CVE
NocoDB stored XSS via OAuth redirect URI
Affects NocoDB before 2026.08.0, where any authenticated account, including an organization-level Viewer, could register OAuth clients. No vendor rating is given. Fixed in 2026.08.0.
- Exploited
- No known exploitation
- Fix
- Fixed in 2026.08.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. OAuth client registration is available to any authenticated account, including an organization-level Viewer.
Summary
NocoDB before 2026.08.0 contains a stored cross-site scripting vulnerability that allows any authenticated user to register OAuth clients with javascript: redirect URIs. Attackers can send a consent link to a signed-in victim so either consent button runs script in the NocoDB origin, stealing the session token for account takeover.
Who should check
Teams running NocoDB before 2026.08.0 where any signed-in user can register OAuth clients, including self-hosted and shared instances.
“OAuth client registration accepted a redirect URI with any URL scheme”
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.5/10CVSS 8.5
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
OAuth client registration is available to any authenticated account, including an organization-level Viewer.Upgrade 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-130728 (NocoDB before 2026.08.0 Stored XSS via OAuth Redirect URI), 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-130728 (entry last updated 2026-11-18):
Affected:
- nocodb nocodb: fixed in 2026.08.0
Fixed versions: 2026.08.0.
Conditions (all must be true for the bug to be hit):
- OAuth client registration is available to any authenticated account, including an organization-level Viewer. (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-2rwf-5cmp-5xwq)
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-130728 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130728 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-2rwf-5cmp-5xwq
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-130728
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-130728"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- nocodb nocodb
fixed in 2026.08.0
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · nocodb/nocodb · Advisory GHSA-2rwf-5cmp-5xwq |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130728 |
| Record | NVD · CVE-2026-130728 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130728
Is CVE-2026-130728 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?
Stored cross-site scripting through the OAuth redirect URI lets a script run in the victim's NocoDB tab. The script can read the session token from localStorage and call authenticated APIs as the victim, including as an administrator, which can lead to account takeover.Source: github.com
Which versions are affected by CVE-2026-130728?
nocodb: before 2026.08.0.Source: cve.now feed data
Am I affected, and how do I check?
Versions before 2026.08.0 are in the affected range. The exposed setup involves OAuth client registration, which was available to any authenticated account, including an organization-level Viewer. Check the installed NocoDB version against 2026.08.0 and review who holds accounts that can register OAuth clients.Source: github.com
How do I fix CVE-2026-130728?
Upgrade NocoDB to 2026.08.0 or later, the first fixed version listed for this vulnerability.Source: github.com