Advisory

GHSA-w43h-r5m5-p832

Also known as: CVE-2026-47382

Summary

NocoDB: Server-Side Request Forgery via Database Connection Host

Details

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.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-06-05 16:19 UTC
Modified
2026-07-20 21:30 UTC

Affected packages and fixes

nocodb

npm · All systems

Affected

  • introduced 0, fixed 2026.05.1 (ecosystem)

Fixed versions

2026.05.1

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences