Skip to main content
Mallory
HighVulnerability

CVE-2026-33687: Authenticated unrestricted file upload type restriction bypass in Sharp

Published Mar 26, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.8High · v3.1
EPSS0.54%46th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Code16
IdentifiersCVE-2026-33687CWE-434 · Unrestricted Upload of File with…

CVE-2026-33687 affects Sharp, a content management framework for Laravel, in versions prior to 9.20.0. The vulnerability is in the file upload endpoint implemented in ApiFormUploadController. Sharp accepted a client-controlled validation_rule parameter and passed it directly to Laravel's validator without adequate server-side enforcement. An authenticated attacker could intercept an upload request and replace the intended validation constraints with validation_rule[]=file, thereby bypassing all configured MIME type and file extension restrictions for uploaded content. The flaw is effectively an unrestricted file upload condition caused by trusting client-supplied validation rules.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an authenticated user to upload files of arbitrary type, including files that would normally be blocked by MIME type or extension validation. This can enable storage of dangerous or unauthorized content and may lead to further compromise depending on deployment configuration. The advisory notes that under default configurations uploaded PHP files are not directly executable, but if Sharp uploads are stored on a publicly accessible disk, the issue could enable direct access to attacker-supplied files and potentially code execution or broader compromise. The provided CVSS vector indicates high impact to confidentiality, integrity, and availability.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, ensure the storage disk used for Sharp uploads is strictly private and not publicly exposed. Avoid configurations that store uploads on a public disk, especially where uploaded server-executable content could be directly requested. As an additional defensive measure, enforce server-side allowlists for permitted file types and ensure uploaded content cannot be executed by the web server.

Remediation

Patch, then assume compromise.

Upgrade Sharp to version 9.20.0 or later. The fix removes client-controlled upload validation rules and enforces upload restrictions strictly on the server side. Any deployment running a version prior to 9.20.0 should be updated as the primary remediation.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Code16Sharpapplication
FAQ

Frequently asked questions

Is CVE-2026-33687 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-33687 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-33687?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-33687.
Is there a patch for CVE-2026-33687?
Upgrade Sharp to version 9.20.0 or later. The fix removes client-controlled upload validation rules and enforces upload restrictions strictly on the server side.
What products are affected by CVE-2026-33687?
Code16 Sharp.
How severe is CVE-2026-33687?
CVE-2026-33687 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 0.54% (46th percentile) as of Sep 25, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity5Community discussion across Reddit, Mastodon, and other social sources.