{"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-33687 in the wild and no public exploit code.","fix":"Upgrade code16/sharp to 9.20.0 or later.","what":"CVE-2026-33687 is a high-severity 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-33687 and fix it if it is affected.\n\nWhat it is: CVE-2026-33687 is a high-severity 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-33687 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-33687/ (Markdown: https://insights.sbomify.com/CVE-2026-33687/index.md)","id":"CVE-2026-33687","markdown":"https://insights.sbomify.com/CVE-2026-33687/index.md","name":"CVE-2026-33687","record":{"aliases":["GHSA-fr76-5637-w3g9"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"Laravel CMS package","requires_auth":"low_privilege","summary":"Authenticated users can bypass file type restrictions in Sharp by manipulating client-side validation rules, potentially leading to remote code execution if public storage is configured.","user_interaction":"not_required","vuln_class":"file_upload"},"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-434","name":"Unrestricted Upload of File with Dangerous Type"}],"description":"Sharp is a content management framework built for Laravel as a package. Versions prior to 9.20.0 contain a vulnerability in the file upload endpoint that allows authenticated users to bypass all file type restrictions. The upload endpoint within the `ApiFormUploadController` accepts a client-controlled `validation_rule` parameter. This parameter is directly passed into the Laravel validator without sufficient server-side enforcement. By intercepting the request and sending `validation_rule[]=file`, an attacker can completely bypass all MIME type and file extension restrictions. This issue has been addressed in version 9.20.0 by removing the client-controlled validation rules and strictly defining upload rules server-side. As a workaround, ensure that the storage disk used for Sharp uploads is strictly private. Under default configurations, an attacker cannot directly execute uploaded PHP files unless a public disk configuration is explicitly used.","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 has Unrestricted File Upload via Client-Controlled Validation Rules","id":"CVE-2026-33687","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"file_upload","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"AVideo has Pre-Captcha User Enumeration and Account Status Disclosure in Password Recovery Endpoint","id":"CVE-2026-33688"},"packages":[{"ecosystem":"Packagist","fixed":["9.20.0"],"introduced":["0"],"last_affected":[],"package":"code16/sharp","purl":null,"source":"GHSA-fr76-5637-w3g9"},{"ecosystem":"Packagist","fixed":["9.20.0"],"introduced":["0"],"last_affected":[],"package":"code16/sharp","purl":"pkg:composer/code16/sharp","source":"GHSA-fr76-5637-w3g9"}],"prev":{"headline":"Sharp is Vulnerable to Path Traversal via Unsanitized Extension in FileUtil","id":"CVE-2026-33686"},"products":["sharp"],"published":"2026-03-26","related":[{"cvss_score":8.8,"headline":"Sharp is Vulnerable to Path Traversal via Unsanitized Extension in FileUtil","id":"CVE-2026-33686","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":"Authenticated users can bypass file type restrictions in Sharp by manipulating client-side validation rules, potentially leading to remote code execution if public storage is configured.","url":"https://insights.sbomify.com/CVE-2026-33687/"}