nocodb
Affected
- introduced
0, fixed2026.05.1(ecosystem)
Fixed versions
2026.05.1
Fix
- Fixed version
2026.05.1npm install [email protected]
Advisory
Also known as: CVE-2026-47381
NocoDB: Cross-Workspace Integration Use in Connection Test
Summary
A user in one workspace could exercise another workspace's integration through thetestConnection endpoint by supplying its ID, because the integration was fetched in
a bypass scope and the caller's permission check matched any base in any workspace.
Details
The connection-test endpoint fetched the integration in RootScopes.BYPASS scope and
checked only that the integration was non-private and that the caller held an
owner/creator role on any base in any workspace. The permission lookup is now scoped
to the integration's workspace by joining on fk_workspace_id, and the controller
rejects requests where the integration's workspace differs from the request's workspace.
Impact
Cross-tenant access to integration configuration through the connection-test endpoint,
including the ability to drive the resolved database with the other workspace's
credentials. Authentication with creator-or-owner role on any base in any workspace
was sufficient.
Credit
This issue was reported by @DongyangLyu.
Medium Basis: The source's own band: MODERATE
0, fixed 2026.05.1 (ecosystem)2026.05.1
2026.05.1npm install [email protected]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
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0