CVE-2026-47382: NocoDB Server-Side Request Forgery in connection-test endpoint

CVE-2026-47382 · Severity: medium · CVSS 4 · Published 2026-06-23

NocoDB, a platform that turns databases into smart spreadsheets, contains a security flaw in its database connection testing feature. An authenticated user could exploit this to probe or interact with internal systems, such as private databases or cloud metadata services, that are normally hidden from the public internet. This could lead to unauthorized internal network mapping or access to sensitive internal infrastructure.

Technologies: nocodb (npm). Vendors: npm.

Quick answers

Is CVE-2026-47382 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-47382 being exploited in the wild.
How severe is CVE-2026-47382?
Medium severity, with a CVSS score of 4, published 23 June 2026.
Which products and versions are affected?
nocodb (npm) <= 2026.05.0, ECOSYSTEM:introduced=0,fixed=2026.05.1.
Is there a fix for CVE-2026-47382?
Yes. nocodb (npm): upgrade to 2026.05.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-47382 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-47382?
Check whether you run nocodb (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • nocodb (npm): upgrade to 2026.05.1 or later
    npm install nocodb@2026.05.1

Technical details

A Server-Side Request Forgery (SSRF) vulnerability exists in NocoDB's connection-test endpoint. The application fails to perform DNS resolution and range-checking on user-supplied database hosts, allowing raw TCP sockets to be opened to private, link-local, and loopback addresses (including IPv4-mapped IPv6). An authenticated attacker with connection-test permissions can use this to scan internal services like Redis or cloud metadata endpoints. While a fix was introduced in version 2026.05.1 using a new validation helper, the advisory notes that DNS rebinding attacks may still be possible during the resolve-vs-connect window.

Affected products

  • NocoDB NocoDB < 2026.05.1

Identifiers

  • CVE-2026-47382
  • GHSA-w43h-r5m5-p832

Timeline

  • 2026-06-04: advisory: GitHub Security Advisory published
  • 2026-06-23: disclosed: CVE published to NVD
  • 2026-05-01: patched: Vulnerability fixed in version 2026.05.1

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.