CVE
NocoDB SSRF in integration remote fetch operation
Affects NocoDB before 2026.08.0 for authenticated users holding the Editor role on a single base. 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. NocoDB versions before 2026.08.0 Attacker holds the base Editor role on a base
Summary
NocoDB before 2026.08.0 contains a server-side request forgery vulnerability that allows authenticated base Editors to make backend HTTP requests by supplying arbitrary URLs to the integration remote fetch operation. Attackers can control the method, headers, and body to reach internal APIs, loopback services, and cloud metadata endpoints, reading responses and echoed decrypted integration secrets.
Who should check
Teams running NocoDB before 2026.08.0 where users hold the base Editor role, including anyone who can create their own base, and teams with integrations storing secrets
Not fixed by: Upgrading only to 2026.08.0 still lets integration secrets reach external hosts.
“Any authenticated user holding the Editor role on a single base”
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.4/10CVSS 8.4
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
NocoDB versions before 2026.08.0 Attacker holds the base Editor role on a baseUpgrade 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-130724 (NocoDB before 2026.08.0 SSRF via Integration Remote Fetch Operation), 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-130724 (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):
- NocoDB versions before 2026.08.0 (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-hjgf-2f3h-4962)
- Attacker holds the base Editor role on a base (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-hjgf-2f3h-4962)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-130724 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130724 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-hjgf-2f3h-4962
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-130724
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-130724"}.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-hjgf-2f3h-4962 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130724 |
| Record | NVD · CVE-2026-130724 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130724
Is CVE-2026-130724 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 NocoDB backend can be made to act as an HTTP client against internal services reachable only from the deployment network. The requester can read the responses and make state-changing requests, and can receive echoed decrypted integration secrets.Source: github.com
Which versions are affected by CVE-2026-130724?
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. The requester needs the base Editor role on a base. To check, compare the installed NocoDB version against 2026.08.0.Source: github.com
How do I fix CVE-2026-130724?
Upgrade NocoDB to 2026.08.0 or later, which refuses internal targets and no longer echoes the expanded configuration.Source: github.com