CVE-2026-53929
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 · uneditedNocoDB is software for building databases as spreadsheets. Prior to 2026.05.1, with NC_SECURE_ATTACHMENTS=true, an authenticated uploader could deliver .html or .svg attachments that the browser rendered inline from the NocoDB origin instead of forcing a download. The signed attachment handler stored response-header overrides under PascalCase keys (ResponseContentDisposition, ResponseContentType) while the controller that served the file read them under lowercase-hyphen names (response-content-disposition). The mismatch dropped the Content-Disposition: attachment header, leaving Express to auto-render .html, .svg, and similar inline. This vulnerability is fixed in 2026.05.1.
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 confidenceIn NocoDB prior to 2026.05.1 with NC_SECURE_ATTACHMENTS enabled, a header key mismatch caused the Content-Disposition: attachment header to be dropped when serving uploaded files. The signed attachment handler stored overrides under PascalCase keys (ResponseContentDisposition) while the controller read under lowercase-hyphen names (response-content-disposition), causing Express to auto-render .html and .svg files inline from the NocoDB origin instead of forcing downloads.
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
- Authentication
- X
- User interaction
- P
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/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 installed NocoDB versionCheck the NocoDB version running in your environment via the /api/v1/meta/version endpoint, admin UI footer, or package.json file in the installation directoryAffected if the version is prior to 2026.05.1 (e.g., 2026.04.x, 2026.03.x, or earlier)
-
Verify NC_SECURE_ATTACHMENTS is enabledInspect your environment variables or configuration files for NC_SECURE_ATTACHMENTS set to true or 1Affected if NC_SECURE_ATTACHMENTS is enabled (set to true, yes, or 1) in your environment
You are affected if your NocoDB version is prior to 2026.05.1 AND NC_SECURE_ATTACHMENTS is enabled, which causes .html/.svg attachments to be served inline instead of as downloads due to the header key mismatch.
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.
dbcve · scopedUpgrade NocoDB to version 2026.05.1 or later to fix the header key mismatch that causes browsers to render malicious .html/.svg attachments inline instead of downloading them.
2026.05.1
- 1. Back up your current NocoDB installation and database before upgrading.
- 2. Upgrade NocoDB to version 2026.05.1 or later (e.g., pull the latest Docker image or update via your package manager).
- 3. Ensure NC_SECURE_ATTACHMENTS=true is still set in your environment configuration.
- 4. Verify the fix by uploading a test .html or .svg file and confirming it is served with Content-Disposition: attachment rather than rendered inline.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-53929 — 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-53929 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