NocoDB stored XSS in attachment MIME type handling
Affects NocoDB versions before 2026.09.0, where the records API stored attachment cell MIME types without validation. Fixed in 2026.09.0.
- Exploited
- No known exploitation
- Fix
- Fixed in 2026.09.0
- Who is exposed
- Specific setups only
Summary
Written by a model
NocoDB before 2026.09.0 contains a stored cross-site scripting vulnerability that allows authenticated Editor users to execute scripts by storing crafted attachment MIME types like text/html;image/png. Attackers can write the value through the records API so the /dltemp signed URL serves HTML inline, stealing session tokens from localStorage to impersonate victims.
Who should check
Teams running NocoDB before 2026.09.0 where Editor users can write attachment cells through the records API, and the instance serves attachments to users.
“Affected versions < 2026.09.0”
What to do
Check whether your setup matches what the bug needs.
NocoDB versions before 2026.09.0 Attachment cell mimetype stored via the records API without validationUpgrade to a fixed version: 2026.09.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-126269 (NocoDB before 2026.09.0 Stored XSS via Attachment MIME Type), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-126269 (entry last updated 2026-11-17):
Affected:
- nocodb nocodb: fixed in 2026.09.0
Fixed versions: 2026.09.0.
Conditions (all must be true for the bug to be hit):
- NocoDB versions before 2026.09.0 (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-3f7w-wqf7-786q)
- Attachment cell mimetype stored via the records API without validation (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-3f7w-wqf7-786q)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, a user action.
CISA KEV: CVE-2026-126269 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126269 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/nocodb/nocodb/security/advisories/GHSA-3f7w-wqf7-786q
- https://www.vulncheck.com/advisories/nocodb-before-2026.09.0-stored-xss-via-attachment-mime-type
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-126269
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126269"}.Affected versions
- nocodb nocodbfixed in 2026.09.0
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 9.3, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 25 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now4 days
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Public exploit activity
- GitHub PoC repos: 1
- EPSS: 0.33%
- Posted on X by cve.now Nov 13
Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.
Evidence 5
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · nocodb/nocodb · Advisory GHSA-3f7w-wqf7-786q |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-126269 |
| Record | NVD · CVE-2026-126269 |
| Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Exploit | GitHub · googlesky/CVE-2026-126269 · Repository |
| Other links 1 | |
| Link | vulncheck.com · advisories/nocodb-before-2026.09.0-stored-xss-via-attachment-mime-type |
Questions about CVE-2026-126269
Is CVE-2026-126269 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
The records API stored an attachment cell's MIME type without validation, so a malicious attachment can run script in the NocoDB origin in the browser of any user who opens it. That script can read the session token from localStorage and impersonate the victim through the authenticated API.
Source: github.com
Which versions are affected by CVE-2026-126269?
nocodb: before 2026.09.0.
Source: cve.now feed data
Am I affected, and how do I check?
NocoDB versions before 2026.09.0 are in the affected range. To check a deployment, look at the NocoDB version it runs and compare it with 2026.09.0.
Source: github.com
How do I fix CVE-2026-126269?
Upgrade NocoDB to 2026.09.0, the fixed version listed for this vulnerability. The vendor's patched versions list names no other patch identifiers.
Source: github.com
Related
- CVE-2026-130730NocoDB before 2026.10.1 OAuth Access Token Accepted as First-Party Session
- CVE-2026-130716NocoDB before 2026.08.0 Stored XSS via URL Formula in Grid View
- CVE-2026-130712NocoDB before 2026.08.1 Cross-Base Database Access via Source ID Collision
- CVE-2026-130729NocoDB before 2026.08.0 Row Filter Bypass via Shared View Relation Endpoints
- CVE-2026-130727NocoDB before 2026.08.0 Shared View Row Filter Bypass via Primary Key Lookup
- CVE-2026-130723NocoDB before 2026.08.0 Shared View Attachment Disclosure via Record ID Enumeration
No corrections so far. Something wrong on this page? Report an error.