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.
Published Mar 25, 2026 · Updated Mar 27, 2026
Affected packages
code16/sharp
- Ecosystem
- Composer (PHP)
- Affected
- < 9.20.0
- Fixed in
- 9.20.0
- Check
composer show code16/sharp
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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(PATHINFO_EXTENSION) 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.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-84974
code16/sharp: Arbitrary class instantiation through the embed_key API parameter
medium5.4Nov 12, 2026CVE-2026-84987
code16/sharp: Server-side request forgery through an unanchored autocomplete endpoint check
medium5.4Nov 12, 2026CVE-2026-61823
code16 Sharp vulnerable to stored XSS via iframe srcdoc Attribute
high7.3Sep 25, 2026CVE-2026-61825
code16/sharp has a stored XSS via data-html-content Sanitizer Bypass
high8.7Sep 25, 2026CVE-2026-53634
Sharp Missing Authorization Check in Quick Creation Command Endpoints
medium4.3Jul 8, 2026CVE-2026-44692
Authenticated Sharp users can download unrelated Laravel Storage objects through the generic download endpoint
high7.7May 15, 2026
