NocoDB has Blind SSRF via Unvalidated HEAD Request in uploadViaURL Functionality

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.9 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N

EPSS

• CVE-2026-24767: 0.22% estimated exploitation activity in the next 30 days; percentile 12.58 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary A blind Server-Side Request Forgery (SSRF) vulnerability exists in the uploadViaURL functionality due to an unprotected HEAD request. While the subsequent file retrieval logic correctly enforces SSRF protections, the initial metadata request executes without validation. This allows limited outbound requests to arbitrary URLs before SSRF controls are applied. --- Vulnerability Details The uploadViaURL() function issues an axios.head() request to retrieve metadata (content type, content length, and final URL after redirects). This request is performed without SSRF filtering. Although the actual file download is protected by request filtering, the initial HEAD request occurs prior to these checks and can be triggered with an attacker-controlled URL. Vulnerable Code --- Impact The impact of this issue is limited due to the following constraints: Only HEAD requests are affected (no response body is returned) No direct exfiltration of response data occurs The subsequent…

Published by the source

28 Jan 2026, 21:41 UTC

Last modified by the source

3 Feb 2026, 03:06 UTC

Source last checked

26 Oct 2026, 12:41 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-xr7v-j379-34v9

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-xr7v-j379-34v9

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-24767

Advisory: NocoDB has Blind SSRF via Unvalidated HEAD Request in uploadViaURL Functionality
IDs: CVE-2026-24767, GHSA-xr7v-j379-34v9
Record: https://patchnext.com/advisories/cve-2026-24767 (revision 2, source checked 26 Oct 2026, 12:41 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: nocodb 0.301.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm nocodb: affected < 0.301.0; fixed in 0.301.0

## Suggested inspection (read-only)
- `npm ls nocodb --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on nocodb.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-xr7v-j379-34v9 (OSV record GHSA-xr7v-j379-34v9 lists affected ranges: npm nocodb >=0 <0.301.0 (fixed))
- Verified: https://github.com/advisories/GHSA-xr7v-j379-34v9 (GitHub-reviewed advisory GHSA-xr7v-j379-34v9 lists affected ranges: npm nocodb >=0 <0.301.0)

Commands are suggestions: review each one before running it.