CVE-2026-22034
Remote Code Execution via PHP Upload Validation in Snuffleupagus
Publication date: 2026-01-08
Last updated on: 2026-03-09
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| jvoisin | snuffleupagus | to 0.13.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-636 | When the product encounters an error condition or failure, its design requires it to fall back to a state that is less secure than other options that are available, such as selecting the weakest encryption algorithm or using the most permissive access control restrictions. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-22034 is a critical vulnerability in the Snuffleupagus PHP security module that occurs when the non-default upload validation feature is enabled and configured to use validation scripts relying on the Vulcan Logic Disassembler (VLD) extension, but the VLD extension is not installed or available to the PHP CLI. In this scenario, all files uploaded via multipart POST requests are incorrectly evaluated and executed as PHP code, allowing an attacker to execute arbitrary PHP code remotely without any privileges or user interaction. This happens because PHP does not fail securely when the VLD extension is missing; instead, it falls back to executing the uploaded files. The vulnerability was fixed in Snuffleupagus version 0.13.0 by modifying the validation scripts to run PHP in lint mode, which checks syntax without executing code, preventing this arbitrary code execution. [2, 4]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including allowing unauthenticated remote attackers to execute arbitrary PHP code on your server. This can lead to full compromise of the affected system, including unauthorized access, data theft, data modification, service disruption, and potentially complete control over the web server. Since the vulnerability requires no privileges or user interaction and can be exploited remotely over the network, it poses a critical security risk to any deployment of Snuffleupagus with the vulnerable configuration. [4]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking if your Snuffleupagus deployment is running a version prior to 0.13.0 with the upload_validation feature enabled and configured to use VLD-based validation scripts, while the VLD extension is not installed or available to the PHP CLI SAPI. You can verify the PHP CLI extensions with the command `php -m | grep vld` to see if VLD is loaded. Additionally, inspecting your Snuffleupagus configuration for the upload_validation feature and the use of scripts/upload_validation.php or scripts/upload_validation.py can help identify vulnerable setups. Since the vulnerability involves multipart POST requests being evaluated as PHP code, monitoring for unexpected PHP execution triggered by file uploads or multipart POST requests could indicate exploitation attempts. Specific commands include: 1) `php -m | grep vld` to check for VLD extension presence, 2) reviewing Snuffleupagus configuration files for upload_validation settings, and 3) monitoring web server logs for suspicious multipart POST requests or unexpected PHP execution patterns. [2, 4, 8]
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability immediately, you should upgrade Snuffleupagus to version 0.13.0 or later, where the issue is fixed. If upgrading is not immediately possible, disable the non-default upload_validation feature or ensure that the VLD extension is properly installed and available to the PHP CLI SAPI to prevent uploaded files from being executed as PHP code. The fix involves modifying the upload validation scripts to run PHP in lint mode (`-l` flag), which prevents execution of uploaded PHP files during validation. Therefore, applying the patch from commit 9278dc7 or upgrading to the fixed version will mitigate the risk. Additionally, reviewing and tightening Snuffleupagus configuration to avoid enabling upload_validation without VLD is recommended. [2, 4]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided resources do not contain information regarding the impact of CVE-2026-22034 on compliance with common standards and regulations such as GDPR or HIPAA.