CVE-2026-33687: code16 sharp · Unrestricted File Upload
Affects code16 sharpSource CVE Database V5
Not known to be exploited · CVSS 8.8 High : upgrade to 9.20.0 soon.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 9.20.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 26 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade sharp and code16/sharp to 9.20.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| code16sharp | Affected
| Fixed in
|
GitHubcode16/sharppkg:github/code16/sharpOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Sharp to version 9.20.0 or later, where the vulnerability is fixed by removing client-controlled validation rules and enforcing strict server-side upload validation. As a workaround, ensure that the storage disk used for uploads is configured as strictly private to prevent direct execution of uploaded files. Avoid using public disk configurations for file storage. Patch status is not explicitly stated as 'patchAvailable' but the vendor fixed the issue in version 9.20.0, so upgrading to this version or later is the official fix.
Description
Sharp, a Laravel content management framework package, has a vulnerability in versions prior to 9.20.0 that allows authenticated users to bypass file type restrictions on uploads. The issue arises because the file upload endpoint accepts a client-controlled validation_rule parameter, which is passed directly to the Laravel validator without proper server-side checks. This enables attackers to bypass MIME type and file extension restrictions by manipulating the validation_rule parameter. The vulnerability is addressed in version 9.20.0 by removing client control over validation rules and enforcing strict server-side upload rules. A workaround is to ensure the storage disk for uploads is private, as default configurations prevent direct execution of uploaded PHP files unless a public disk is used.