dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-47382

MEDIUM · 5.3 CVSS v4.0 Published 2026-06-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
NocoDB is software for building databases as spreadsheets. Prior to 2026.05.1, 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. This vulnerability is fixed in 2026.05.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

NocoDB's connection-test endpoint suffers from a Server-Side Request Forgery (SSRF) vulnerability where it opens raw TCP sockets to user-supplied database hosts without validating whether the destination is a private, link-local, or loopback address. This allows attackers to probe internal services via IPv4, IPv6 (including IPv4-mapped IPv6), and localhost addresses.

MitigationUpgrade to NocoDB version 2026.05.1 or later, which implements proper destination validation to block connections to private and link-local address ranges.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify NocoDB installation and version
    Check the installed NocoDB version by querying the API endpoint /api/v1/meta/version or checking package.json if self-hosted. Compare against the fixed version 2026.05.1.
    Affected if Running a version earlier than 2026.05.1 indicates potential vulnerability.
  2. Verify connection-test endpoint is accessible
    Confirm the /api/v1/dbConnections/test endpoint exists and responds to requests. This endpoint accepts database connection parameters including host/port.
    Affected if The endpoint is reachable without authentication or with valid user credentials.
  3. Check if external database connections are configured
    Review NocoDB configuration for any external database connections (MySQL, PostgreSQL, SQL Server, etc.) that use the connection-test feature. Look for entries in the database connection settings UI or API.
    Affected if External database connections can be tested through the vulnerable endpoint.
  4. Inspect network configuration for exposed access
    Determine if NocoDB is exposed to untrusted networks. Check reverse proxy, firewall rules, or cloud security groups that allow external access to NocoDB ports (default 8080 or 3000).
    Affected if The NocoDB instance is accessible from untrusted networks or the internet.

A user is affected if running NocoDB version earlier than 2026.05.1 with the connection-test endpoint accessible from their network and external database connections enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to NocoDB version 2026.05.1 or later, which implements proper destination validation to block connections to private and link-local address ranges.

Recommended fix High confidence

2026.05.1

  1. Upgrade NocoDB to version 2026.05.1 or later. Follow the standard upgrade procedure for your deployment method (Docker, npm, or manual installation).
  2. After upgrading, verify the connection-test functionality still works correctly for legitimate database connections.
  3. If using automated deployment, update your deployment configuration to reference version 2026.05.1 or the latest stable release.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47382 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-47382 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data