CVE-2026-11569
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 flaw was found in Quay. The filedrop endpoint accepts any mime type without validation, allowing an authenticated user with repository write access to upload a malicious SVG file containing JavaScript. The file is stored and served inline through the CDN, enabling stored cross-site scripting when a victim visits the archive URL.
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 confidenceQuay's filedrop endpoint lacks mime type validation, allowing authenticated users with repository write access to upload malicious SVG files containing JavaScript. These files are stored and served inline through the CDN, enabling stored XSS when users visit the archive URL.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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.
-
Verify Quay instance is running and accessibleAccess the Quay web interface and confirm you can authenticate with valid credentialsAffected if Quay is running and you can log in as an authenticated user with repository write access
-
Confirm repository write access existsCheck user permissions on at least one repository to verify the account has write or admin accessAffected if User account has write or admin permissions on one or more repositories
-
Identify if the filedrop endpoint is enabledCheck if the filedrop feature is available in repository settings or by attempting to access the upload interface for a repositoryAffected if The filedrop/upload functionality is present and accessible to authenticated users with write access
-
Test SVG upload capability to the filedrop endpointAttempt to upload a test SVG file through the filedrop interface or API endpoint to see if it is accepted without mime type validationAffected if SVG files can be uploaded through the filedrop endpoint without rejection based on mime type validation
-
Check how uploaded SVG files are servedAccess the uploaded SVG file through its URL and examine the Content-Disposition header to determine if it is served inline or as an attachmentAffected if SVG files are served with inline Content-Disposition or without proper Content-Type restrictions, allowing script execution in browsers
You are affected if your Quay instance allows authenticated users with write access to upload SVG files through the filedrop endpoint and serves those files inline, enabling stored XSS
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 allowlist-based mime type validation on the filedrop endpoint, specifically blocking SVG uploads or sanitizing SVG content, and ensure proper Content-Type headers are set when serving files to prevent script execution.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11569 — 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-11569 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