# CVE-2026-46552: NocoDB: Shared-base link access can invite arbitrary users as persistent base members

> Attackers with a shared-base link can invite arbitrary users as persistent members, bypassing access controls to gain authenticated data access.

- **Severity:** Medium 5.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jun 2026
- **Updated:** 24 Jun 2026
- **Also known as:** GHSA-chqv-vrj7-qffp

## What is CVE-2026-46552?

CVE-2026-46552 is a medium-severity missing authorization vulnerability in nocodb, published on 23 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

NocoDB is software for building databases as spreadsheets. Prior to 2026.04.1, shared-base sessions were granted the same base-member capabilities as authenticated viewers. Using only the shared-base UUID (xc-shared-base-id), an attacker could enumerate base members and invite an arbitrary email into the base as a real member. The invited user could then redeem the invite via the normal signup flow and retain authenticated access even after the owner revoked the shared link. Shared-base sessions were mapped to ProjectRoles.VIEWER in packages/nocodb/src/strategies/base-view.strategy/base-view.strategy.ts, and packages/nocodb/src/utils/acl.ts granted baseUserList and userInvite to that role. The shared frontend (packages/nc-gui/composables/useApi/interceptors.ts) deliberately removed auth headers in favour of the shared-base header, but the ACL middleware did not distinguish shared sessions from genuine viewers. This vulnerability is fixed in 2026.04.1.

Weakness: CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2026-46552?

2 open source packages ship an affected version, including nocodb.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `nocodb` | npm | All versions to 0.301.3 | None |
| `nocodb` | npm | All versions to 0.301.3 | None |

## How do I fix CVE-2026-46552?

No fix has been published for CVE-2026-46552 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-46552 being exploited?

There is no known exploitation of CVE-2026-46552 in the wild and no public exploit code.

Public exploit code:

- NocoDB Shared-Base Links Could Invite Real Base Members and Survive Share Revocation (github_poc): https://github.com/0xmrma/CVE-2026-46552

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-46552 and fix it if it is affected.

What it is: CVE-2026-46552 is a medium-severity missing authorization vulnerability in nocodb, published on 23 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-46552 in the wild and no public exploit code.

Affected packages and fixed versions:
- nocodb (npm): affected all versions up to 0.301.3; no fix listed
- nocodb (npm): affected all versions up to 0.301.3; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-46552/ (Markdown: https://insights.sbomify.com/CVE-2026-46552/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-46552
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-46552
- OSV: https://osv.dev/vulnerability/CVE-2026-46552

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-46552/
Summaries are generated and may contain mistakes; the official description above is the record.