NocoDB stored XSS in table deletion dialog
- Exploited
- Public exploit code, no confirmed attacks
- Fix
- Fixed in 2026.08.0
- Who is exposed
- Specific setups only
Summary
NocoDB before 2026.08.0 contains a stored cross-site scripting vulnerability that allows authenticated Creator users to inject script by embedding markup in column or table titles. The Delete.vue confirmation dialog renders these titles through an unescaped innerHTML binding, executing script when a victim deletes an external-source table to steal session tokens from localStorage.
Who should check
Teams running NocoDB before 2026.08.0 where users with the base Creator role can create link columns and delete tables on external data sources.
“Affecting nocodb >= 0, < 2026.08.0”
What to do
Check whether your setup matches what the bug needs.
NocoDB versions before 2026.08.0 The deleted table is on an external (non-meta) data source and still has link columns pointing at itUpgrade to a fixed version: 2026.08.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-126274 (NocoDB before 2026.08.0 Stored XSS via Table Deletion Dialog), 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-126274 (entry last updated 2026-11-13):
Affected:
- nocodb nocodb: fixed in 2026.08.0
Fixed versions: 2026.08.0.
Conditions (all must be true for the bug to be hit):
- NocoDB versions before 2026.08.0 (source: https://www.vulncheck.com/advisories/nocodb-before-2026.08.0-stored-xss-via-table-deletion-dialog)
- The deleted table is on an external (non-meta) data source and still has link columns pointing at it (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-638g-xw92-xq9x)
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-126274 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126274 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-638g-xw92-xq9x
- https://www.vulncheck.com/advisories/nocodb-before-2026.08.0-stored-xss-via-table-deletion-dialog
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-126274
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-126274"}.Affected versions
- nocodb nocodbfixed in 2026.08.0
cve.now Index
- Exploitation22/40Public exploit on Exploit-DB or GitHub
- 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 47 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated1 day
- Exploit code on GitHub
googlesky/CVE-2026-126274
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-638g-xw92-xq9x |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-126274 |
| Record | NVD · CVE-2026-126274 |
| Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Exploit | GitHub · googlesky/CVE-2026-126274 · Repository |
| Other links 1 | |
| Link | vulncheck.com · advisories/nocodb-before-2026.08.0-stored-xss-via-table-deletion-dialog |
Questions about CVE-2026-126274
Is CVE-2026-126274 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. Public exploit code exists (a proof of concept on GitHub).
Source: cve.now feed data
What does this mean?
A table name shown in the table deletion dialog is not escaped, so script can run in the browser of a user who confirms the deletion. That script could read the session token from browser storage and act as that user through the authenticated API.
Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-126274?
nocodb: before 2026.08.0.
Source: cve.now feed data
Am I affected, and how do I check?
NocoDB versions before 2026.08.0 are affected, but only for tables on an external (non-meta) data source that still have link columns pointing at them. To check, look at the NocoDB version in the app and whether the table being deleted is on an external data source with link columns.
Source: vulncheck.com, github.com
How do I fix CVE-2026-126274?
Upgrade NocoDB to 2026.08.0 or later, which is the fixed version listed for this vulnerability.
Source: vulncheck.com, 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.