CVE-2026-22102
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA POST request sent to a specific webserver endpoint can be used to write to arbitrary file locations. The endpoint accepts the filename parameter in the Content-Disposition header without verification. This can be used to cause a denial of service by overwriting system files, or remote-code-execution by overwriting shell-scripts which execution can be triggered through other means.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceAn unauthenticated POST endpoint accepts a filename parameter from the Content-Disposition header without validation, allowing path traversal and arbitrary file writes. Attackers can overwrite system files for DoS or replace shell scripts for RCE.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify exposed file upload endpointsReview your web application's exposed POST endpoints, particularly those accepting multipart/form-data or file uploads. Check for endpoints that process Content-Disposition headers without authentication requirements.Affected if An unauthenticated POST endpoint exists that accepts file uploads and processes Content-Disposition headers.
-
Inspect Content-Disposition header parsing logicExamine the codebase or configuration for the file upload handler. Locate where the filename parameter from the Content-Disposition header is extracted and used.Affected if The code extracts and uses the filename parameter from Content-Disposition without validation or sanitization.
-
Check for input validation on filename parameterSearch the file upload handler for validation routines that sanitize or validate the filename parameter. Look for allowlists, path normalization, or directory restriction logic.Affected if No validation, sanitization, or allowlisting is performed on the filename parameter before using it in file operations.
-
Verify write operations are restrictedInspect where uploaded files are written to disk. Check if write operations are confined to a specific uploads directory with no ability to traverse outside that directory.Affected if File write operations can occur outside a designated uploads directory, allowing path traversal.
-
Confirm authentication on endpointReview endpoint access controls, authentication middleware, or authorization checks applied to the file upload POST endpoint.Affected if The file upload endpoint permits unauthenticated access.
You are affected if your environment exposes an unauthenticated POST endpoint that processes the filename parameter from Content-Disposition headers without validation, allowing path traversal and arbitrary file writes.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict input validation on the filename parameter using allowlist validation, restrict write operations to a designated uploads directory, and add proper authentication/authorization checks to the endpoint.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22102 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-22102 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data