Advisory

GHSA-6mhr-74x2-98v9

Also known as: CVE-2026-53929

Summary

NocoDB: Stored Cross-Site Scripting via Secure Attachment

Details

Summary
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.

Details
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. The fix corrects the key case and
additionally forces Content-Disposition: attachment and
Content-Type: application/octet-stream for any MIME type not on the preview
allowlist.

Impact
Stored Cross-Site Scripting in the NocoDB origin from inline-rendered uploads. Script
executing in the victim's browser can read the auth JWT from localStorage.
Exploitation requires authenticated upload permission and the secure-attachment mode
to be enabled.

Credit
This issue was reported by @bugbunny-research.
It was independently reported by @DavidCarliez.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-06-17 14:07 UTC
Modified
2026-07-20 21:30 UTC

Affected packages and fixes

nocodb

npm · All systems

Affected

  • introduced 0, last affected 0.301.3 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences