dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2026-46552

MEDIUM · 5.8 CVSS v3.1 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 →
67/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 8 weeks old

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.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.

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 versions prior to 2026.04.1 incorrectly mapped shared-base sessions (accessed via xc-shared-base-id UUID) to ProjectRoles.VIEWER, granting them baseUserList and userInvite permissions. This allowed attackers with only the shared-base UUID to enumerate base members and invite arbitrary email addresses as real members, who retained authenticated access even after shared link revocation.

MitigationUpgrade to NocoDB version 2026.04.1 or later, which fixes the ACL middleware to properly distinguish shared-base sessions from authenticated viewers.

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
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N

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. Check installed NocoDB version
    Run the command to retrieve the NocoDB version (e.g., check the UI footer, API endpoint /api/v1/version, or docker container tag)
    Affected if The installed version is earlier than 2026.04.1 (e.g., 2026.03.x, 2026.02.x, or any version prior to 2026.04.1)
  2. Verify shared-base feature is in use
    Inspect API requests or application logs for the xc-shared-base-id header or UUID patterns used to access shared bases
    Affected if Shared bases are actively used and accessible via shared-base UUIDs in the environment
  3. Audit recent user invitations
    Review the user invitation logs or database tables (such as nc_users or related invitation records) for invites created from shared-base sessions, noting the timestamp and source IP
    Affected if There are user invitations that were created via shared-base access and which should not have been possible from a VIEWER role
  4. Review base membership for unauthorized members
    Query the base membership or project role tables to identify any users added as members who were not explicitly invited through the normal authenticated workflow
    Affected if Bases contain members whose invitation originated from a shared-base UUID rather than from an authenticated admin or owner session

A user is affected if their NocoDB version is earlier than 2026.04.1 AND shared bases are accessible, allowing enumeration of base members and unauthorized user invitations through the vulnerable shared-base session mapping.

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.04.1 or later, which fixes the ACL middleware to properly distinguish shared-base sessions from authenticated viewers.

Recommended fix High confidence

2026.04.1

  1. 1. Back up your existing NocoDB database and configuration
  2. 2. Stop the NocoDB service
  3. 3. Update NocoDB to version 2026.04.1 or later using your deployment method (e.g., npm install, Docker, or binary)
  4. 4. Verify the installation was successful
  5. 5. Start the NocoDB service
  6. 6. Test that shared links function correctly for viewers but no longer have member enumeration or invitation capabilities
  7. 7. Review any shared links previously generated to ensure they still work as intended for read-only access

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
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46552 — 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-46552 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