CVE-2026-33686: Sharp is Vulnerable to Path Traversal via Unsanitized Extension in FileUtil
Summary A path traversal vulnerability exists in the FileUtil class of the code16/sharp package. The application fails to sanitize file extensions properly, allowing path separators to be passed into the storage layer.
Detail In src/Utils/FileUtil.php, the FileUtil::explodeExtension() function extracts a file's extension by splitting the filename at the last dot. However, the extracted extension is never sanitized. While the application uses a normalizeName() function, this function only cleans the base filename, meaning any path separators (such as /) injected into the extension will survive and be passed into the storeAs() function.
Impact Exploiting this flaw allows an authenticated attacker to manipulate file paths: - Files can be written outside of the intended tmp directory via path traversal. For more details on the package, visit: https://github.com/code16/sharp - Existing critical files (such as .env or configuration files) could potentially be overwritten. Review the CWE definition here: https://cwe.mitre.org/data/definitions/22.html (Note: This vulnerability was successfully chained with CWE-434 in a local Proof of Concept to confirm the traversal.)
Patches This issue has been patched by properly sanitizing the extension using pathinfo(PATHINFOEXTENSION) instead of strrpos(), alongside applying strict regex replacements to both the base name and the extension. The fix is available in pull request #715
Credits Reported by zaurgsynv.
Other sources
Sharp is a content management framework built for Laravel as a package. Versions prior to 9.20.0 have a path traversal vulnerability in the FileUtil class. The application fails to sanitize file extensions properly, allowing path separators to be passed into the storage layer. In src/Utils/FileUtil.php, the FileUtil::explodeExtension() function extracts a file's extension by splitting the filename at the last dot. This issue has been patched in version 9.20.0 by properly sanitizing the extension using pathinfo(PATHINFOEXTENSION) instead of strrpos(), alongside applying strict regex replacements to both the base name and the extension.
— MITRE
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2026-33686?
CVE-2026-33686 is classified as a high-severity path traversal vulnerability.
How do I fix CVE-2026-33686?
To fix CVE-2026-33686, upgrade to the latest version of the code16/sharp package, specifically version 9.20.0 or later.
What systems are affected by CVE-2026-33686?
CVE-2026-33686 affects applications that utilize the code16/sharp package prior to version 9.20.0.
What is the primary issue with CVE-2026-33686?
The primary issue with CVE-2026-33686 is improper sanitization of file extensions that allows for path traversal attacks.
Can CVE-2026-33686 lead to data exposure?
Yes, CVE-2026-33686 can potentially lead to unauthorized access to sensitive files and data exposure.