CVE-2026-47382: NocoDB Server-Side Request Forgery Vulnerability

MODERATE
Advisory Identifier: GHSA-w43h-r5m5-p832
CWE-918
Published
Advisory Summary

CVE-2026-47382 is a MODERATE server-side request forgery vulnerability (CWE-918: Server-Side Request Forgery (SSRF)) affecting NocoDB libraries in the npm ecosystem. The issue involves server-side request forgery via database connection host. Remediation is available by upgrading affected packages to version 2026.05.1.

CVE-2026-47382 at a Glance

CVE Identifier CVE-2026-47382
GHSA Identifier GHSA-w43h-r5m5-p832
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-918: Server-Side Request Forgery (SSRF)
Affected Product NocoDB
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-47382

To remediate this vulnerability, upgrade all affected NocoDB dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

nocodb fixed: 2026.05.1
npm install nocodb@2026.05.1
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls nocodb

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-47382, inspect your project dependencies using npm:

npm ls nocodb

Analyze the terminal output to locate any version of NocoDB in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2026.05.1), your application is affected.

Note: The npm ls nocodb command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-918: Server-Side Request Forgery (SSRF), where the web server receives a url or similar request from an upstream component and retrieves the contents of this url, but it does not sufficiently ensure that the request is being sent to the expected destination. In NocoDB, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary The connection-test endpoint opened a raw TCP socket to the user-supplied database host without resolving and range-checking the destination, so private and link-local addresses (including IPv4-mapped IPv6 forms and `localhost`) reached the driver. ### Details A new `validateDbConnectionHost` helper resolves hostnames through DNS, parses each address with `ipaddr.js`, normalises IPv4-mapped IPv6, and rejects addresses in the private, loopback, link-local, unique-local, reserved, unspecified, broadcast, and carrier-grade-NAT ranges. `0.0.0.0`, `::`, and the literal `localhost` are special-cased. The check runs before the existing SSL block in the connection-test controller and gates the driver invocation. ### Impact Authenticated users with connection-test permission could probe internal services (Redis, the cloud metadata endpoint, internal databases) reachable from the NocoDB process. A DNS rebinding attacker could still race the resolve-vs-connect window. ### Credit This issue was reported by [@helwor-01](https://github.com/helwor-01).

CVE-2026-47382 Affected NocoDB Versions

1 component(s)
Fixed Versions:
2026.05.1
Product / Package Ecosystem Affected Versions Fixed Version
nocodb
npm
< 2026.05.1
2026.05.1

References

Frequently Asked Questions

What is CVE-2026-47382?
CVE-2026-47382 is a security vulnerability in NocoDB involving Server-Side Request Forgery via Database Connection Host under CWE-918: Server-Side Request Forgery (SSRF).
Which NocoDB versions are affected?
Affected versions include releases prior to 2026.05.1 across affected packages: nocodb.
What version fixes CVE-2026-47382?
Upgrading to 2026.05.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is nocodb affected?
Yes, nocodb is affected in releases prior to 2026.05.1. Upgrade your dependency to 2026.05.1 or later.
What CWE is associated with CVE-2026-47382?
CVE-2026-47382 is classified under CWE-918: Server-Side Request Forgery (SSRF) (The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.).
How can I check npm dependencies for CVE-2026-47382?
Run the dependency tree command: 'npm ls nocodb'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-w43h-r5m5-p832",
  "modified" : "2026-07-20T21:18:21Z",
  "published" : "2026-06-05T16:19:01Z",
  "aliases" : [ "CVE-2026-47382" ],
  "summary" : "NocoDB: Server-Side Request Forgery via Database Connection Host",
  "details" : "### Summary\nThe connection-test endpoint opened a raw TCP socket to the user-supplied database\nhost without resolving and range-checking the destination, so private and link-local\naddresses (including IPv4-mapped IPv6 forms and `localhost`) reached the driver.\n\n### Details\nA new `validateDbConnectionHost` helper resolves hostnames through DNS, parses each\naddress with `ipaddr.js`, normalises IPv4-mapped IPv6, and rejects addresses in the\nprivate, loopback, link-local, unique-local, reserved, unspecified, broadcast, and\ncarrier-grade-NAT ranges. `0.0.0.0`, `::`, and the literal `localhost` are special-cased.\nThe check runs before the existing SSL block in the connection-test controller and\ngates the driver invocation.\n\n### Impact\nAuthenticated users with connection-test permission could probe internal services\n(Redis, the cloud metadata endpoint, internal databases) reachable from the NocoDB\nprocess. A DNS rebinding attacker could still race the resolve-vs-connect window.\n\n### Credit\nThis issue was reported by [@helwor-01](https://github.com/helwor-01).",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "nocodb"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2026.05.1"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 2026.05.0"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/nocodb/nocodb/security/advisories/GHSA-w43h-r5m5-p832"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-47382"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/nocodb/nocodb"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/nocodb/nocodb/releases/tag/2026.05.1"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-918" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-05T16:19:01Z",
    "nvd_published_at" : "2026-06-23T21:17:00Z"
  }
}