CVE
NocoDB missing authorization leaks job status in polling endpoint
NocoDB before 2026.09.0 has a job status polling endpoint with missing authorization, so a caller who knows a job's id can read its status and completion payload. Fixed in 2026.09.0.
- Exploited
- No known exploitation
- Fix
- Fixed in 2026.09.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2026.09.0.
Summary
NocoDB before 2026.09.0 contains a missing authorization vulnerability in the job status polling endpoint of jobs.controller.ts that lacks an @Acl decorator. Unauthenticated attackers with a job id can read buffered status messages and completion payloads, exposing signed export download URLs or new base identifiers.
Who should check
Anyone running NocoDB before 2026.09.0, including self-hosted NocoDB instances whose job API is reachable over the network
“Affected versions”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.2/10CVSS 8.2
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 30 if advisories confirm default setups are exposed
What to do
Upgrade 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-130710 (NocoDB before 2026.09.0 Missing Authorization on Job Status Polling Endpoint), 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-130710 (entry last updated 2026-11-18):
Affected:
- nocodb nocodb: fixed in 2026.09.0
Fixed versions: 2026.09.0.
Conditions (all must be true for the bug to be hit):
- The attacker must know the job's id, which the base's job list returns to every base member, including Viewers (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-26fp-q2gc-grh6)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-130710 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130710 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-26fp-q2gc-grh6
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-130710
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-130710"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- nocodb nocodb
fixed in 2026.09.0
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · nocodb/nocodb · Advisory GHSA-26fp-q2gc-grh6 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130710 |
| Record | NVD · CVE-2026-130710 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130710
Is CVE-2026-130710 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 job status polling endpoint does not check authorization, so a caller who holds a job's id can read that job's status updates and completion payload while the job runs. The payload can expose a signed export download URL or a new base identifier.Source: github.com
Which versions are affected by CVE-2026-130710?
nocodb: before 2026.09.0.Source: cve.now feed data
Am I affected, and how do I check?
Versions of NocoDB before 2026.09.0 are in the affected range. The attacker needs the job's id, which the base's job list returns to every base member, including Viewers, so the job list is the setup to look at. Check the installed NocoDB version against 2026.09.0.Source: github.com
How do I fix CVE-2026-130710?
Upgrade NocoDB to 2026.09.0 or later, which is the fixed version listed for this vulnerability.Source: github.com