CVE-2026-22034
Jvoisin Snuffleupagus ≤ 0.13.0
Raw vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2026-22034 is a critical-severity Failing Open (CWE-636) vulnerability in Jvoisin Snuffleupagus. Its CVSS base score is 9.2 (Critical).
Operationally, ranked at the 49th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to CP-12 (Safe Mode) and SC-24 (Fail in Known State) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-22034 affects Snuffleupagus, a PHP module designed to raise the cost of attacks against websites by eliminating bug classes and providing virtual patching. The vulnerability occurs in deployments prior to version 0.13.0 where the non-default upload validation feature is enabled and configured to use upstream validation scripts based on the Vulcan Logic Disassembler (VLD), but the VLD extension is unavailable to the CLI SAPI. In such configurations, all files from multipart POST requests are incorrectly evaluated as PHP code, enabling unintended code execution. The issue carries a CVSS v3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) and is associated with CWE-636 (Not Failing to Clear Existence Check After Atomic Operation).
Remote attackers can exploit this vulnerability without authentication or user interaction by sending crafted multipart POST requests containing malicious files, which are then executed as PHP code on the server. This leads to arbitrary remote code execution, potentially allowing full compromise of the affected web server, including data exfiltration, modification, or denial of service.
The vulnerability was addressed in Snuffleupagus version 0.13.0, as detailed in the project's security advisory (GHSA-c4ch-xw5p-2mvc) and the fixing commit (9278dc77bab2a219e770a1b31dd6797bc9070e37). Security practitioners should upgrade to version 0.13.0 or later and review configurations to ensure the upload validation feature either uses available VLD extensions or is disabled if not required. Source code changes in sp_upload_validation.c and the affected validation scripts (upload_validation.php and upload_validation.py in v0.12.0) highlight the specific logic flaw resolved in the patch.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-1676
Vulnerability Data
Snuffleupagus is a module that raises the cost of attacks against website by killing bug classes and providing a virtual patching system. On deployments of Snuffleupagus prior to version 0.13.0 with the non-default upload validation feature enabled and configured to…
more
use one of the upstream validation scripts based on Vulcan Logic Disassembler (VLD) while the VLD extension is not available to the CLI SAPI, all files from multipart POST requests are evaluated as PHP code. The issue was fixed in version 0.13.0.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V3.2.1V7.4.1V8.3.3V10.3.4
Mitigating Controls (NIST 800-53 r5) AI
SC-24 directly requires the system to fail to a known state that preserves security properties, structurally stopping fallback to a less-secure mode.
SI-17 mandates explicit fail-safe procedures that activate on indicated failures, preventing the insecure fallback behavior.
CP-12 forces entry into a safe mode on detected conditions, limiting exposure but not covering every failure path.
SA-8 requires application of engineering principles that include fail-secure design, reducing the likelihood the weakness is introduced.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure-development practices explicitly include designing error and failure handling to remain in a secure state.
Least-privilege policy and enforcement directly counters the permissive-access fallback example in the CWE.
Hardened baselines and configuration management reduce the chance that error paths default to insecure settings.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
The control forces an explicit evaluation step before any response, reducing the chance that a failure condition will default to an unsafe open state.