CVE-2025-41714
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 · uneditedThe upload endpoint insufficiently validates the 'Upload-Key' request header. By supplying path traversal sequences, an authenticated attacker can cause the server to create upload-related artifacts outside the intended storage location. In certain configurations this enables arbitrary file write and may be leveraged to achieve remote code execution.
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 · high confidenceThe upload endpoint fails to properly validate the 'Upload-Key' request header, allowing authenticated attackers to inject path traversal sequences (e.g., '../'). This enables writing upload artifacts to arbitrary locations on the filesystem outside the intended storage directory, which in permissive configurations can lead to arbitrary file write and potential remote code execution.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Locate upload endpoint using Upload-Key headerReview application source code, API documentation, or network traffic logs to identify endpoints that accept file uploads and reference an 'Upload-Key' request header. Search for terms like 'Upload-Key', 'upload', 'artifact', or 'file upload' in routing definitions.Affected if An upload endpoint exists that reads values from the 'Upload-Key' request header to determine file destination paths.
-
Inspect path validation logic for Upload-KeyExamine the upload handler code that processes the Upload-Key header value. Look for presence of path traversal checks such as path normalization (e.g., path.resolve, os.path.realpath), directory boundary enforcement, or whitelist validation before constructing the final file path.Affected if The code uses the Upload-Key header value directly in file path construction without validating that it stays within the designated upload directory.
-
Verify storage directory configurationLocate the configuration defining the allowed upload storage directory. Check if the application enforces that all uploaded files must remain within this directory, and whether symlinks or relative path sequences could escape this boundary.Affected if The storage directory is not explicitly bounded or the application lacks enforcement to keep files within that directory.
-
Test for path traversal vulnerabilityIf you have authorized access, send a request to the upload endpoint with an Upload-Key header containing path traversal sequences (e.g., '../') and observe whether files are created outside the intended directory. In production, instead review HTTP access logs for suspicious upload requests with '../' in the Upload-Key header.Affected if Files can be written to locations outside the intended upload directory when '../' sequences are included in the Upload-Key header.
Your environment is affected if an upload endpoint uses the Upload-Key header to determine file paths without validating that canonicalized paths remain within the designated storage directory.
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 validation of the Upload-Key header, whitelist allowed characters, and ensure all file paths are canonicalized and validated to remain within the designated upload directory. Restrict file write permissions on the storage location.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-41714 — 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-2025-41714 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