6.5
Medium
CVSS 3.1 base
What to do
If you run nocodb before 2026.10.1, upgrade to 2026.10.1 or later.
Anyone who can reach it over the network, with a low-privilege account and no user interaction, can read sensitive data.Read from the CVSS 3.1 vector
To exploit it
What it gets
This page reproduces the published advisory for this finding. The advisory of record is linked above.
| Package | Ecosystem | Vulnerable | Fixed in |
|---|---|---|---|
nocodb | other | < 2026.10.1 | 2026.10.1 |
The connection-test endpoint merged caller-supplied connection fields over a stored integration’s configuration, so a caller could redirect the connection attempt to a host they control while inheriting the stored database password. A workspace-ownership guard added to the same route for CVE-2026-47381 was also unreachable.
The handler in utils.controller.ts deep-merged the request body over integration.getConfig(), so connection.host, port and user were overridden by the caller while unstated fields, including the stored password, were inherited. Both editions behaved this way, apart from vault-backed configurations in the Enterprise edition. PostgreSQL md5 and MySQL challenge-response handshakes are offline-crackable, so a connectivity check became credential extraction, although NocoDB masks stored connection secrets on read elsewhere.
Separately, the workspace-mismatch check added by the CVE-2026-47381 fix was conditioned on a request property the extract-ids middleware never populates on this route: the ACL is declared at organization scope, and the default-workspace fallback applies only to workspace- and base-scope ACLs. The membership fallback beneath it was skipped outright for organization-level creators. The Enterprise controller overrides this method and enforces workspace membership, and the community edition has no second workspace, so the dead guard was latent. The private-integration check is unaffected by either issue.
A test that names a saved connection now takes only the database and schema from the request and refuses any other client or target field, so stored credentials only go to the stored host. The unreachable workspace check has been removed.
A caller already authorized on an integration could point its stored credentials at a server they control and capture the database password, escalating NocoDB-mediated access into raw credentials for the connected database. The unreachable ownership guard left CVE-2026-47381 unmitigated on this route and would have failed open had the community edition gained multi-workspace support.
This issue was reported by uu K. It was independently reported by @sfwani.
Sanaan Fayaz Wani (GitHub sfwani) reported this vulnerability to the nocodb maintainers under coordinated disclosure and is credited as a reporter in GHSA-jcc2-3vff-7867, published 2026-11-02.
All published findings: advisory index.