{"answers":{"affected":"2 open source packages ship an affected version, including code16/sharp. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-33686 in the wild and no public exploit code.","fix":"Upgrade code16/sharp to 9.20.0 or later.","what":"CVE-2026-33686 is a high-severity path traversal vulnerability in code16 sharp, published on 26 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-33686 and fix it if it is affected.\n\nWhat it is: CVE-2026-33686 is a high-severity path traversal vulnerability in code16 sharp, published on 26 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-33686 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- code16/sharp (Packagist): affected all versions; fixed in 9.20.0\n- code16/sharp (Packagist): affected all versions; fixed in 9.20.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-33686/ (Markdown: https://insights.sbomify.com/CVE-2026-33686/index.md)","id":"CVE-2026-33686","markdown":"https://insights.sbomify.com/CVE-2026-33686/index.md","name":"CVE-2026-33686","record":{"aliases":["GHSA-9ffq-6457-8958"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Laravel CMS package","requires_auth":"low_privilege","summary":"Attackers can exploit unsanitized file extensions in Sharp to perform path traversal, potentially reading or modifying files outside the intended storage directory.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"sharp","vendor":"code16"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"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(PATHINFO_EXTENSION)` instead of `strrpos()`, alongside applying strict regex replacements to both the base name and the extension.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Sharp is Vulnerable to Path Traversal via Unsanitized Extension in FileUtil","id":"CVE-2026-33686","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"Sharp has Unrestricted File Upload via Client-Controlled Validation Rules","id":"CVE-2026-33687"},"packages":[{"ecosystem":"Packagist","fixed":["9.20.0"],"introduced":["0"],"last_affected":[],"package":"code16/sharp","purl":null,"source":"GHSA-9ffq-6457-8958"},{"ecosystem":"Packagist","fixed":["9.20.0"],"introduced":["0"],"last_affected":[],"package":"code16/sharp","purl":"pkg:composer/code16/sharp","source":"GHSA-9ffq-6457-8958"}],"prev":{"headline":"AVideo Allows Unauthenticated Access to AD_Server reports.json.php that Exposes Ad Campaign Analytics and User Data","id":"CVE-2026-33685"},"products":["sharp"],"published":"2026-03-26","related":[{"cvss_score":8.8,"headline":"Sharp has Unrestricted File Upload via Client-Controlled Validation Rules","id":"CVE-2026-33687","kev_date_added":null,"published":"2026-03-26"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-03-27","vendors":["code16"]},"summary":"Attackers can exploit unsanitized file extensions in Sharp to perform path traversal, potentially reading or modifying files outside the intended storage directory.","url":"https://insights.sbomify.com/CVE-2026-33686/"}