# CVE-2026-52888: NocoBase: Sensitive Data Exposure via SQL Blacklist Bypass

> An admin user can bypass SQL restrictions to read sensitive database metadata and password hashes in NocoBase.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Jul 2026
- **Updated:** 16 Jul 2026
- **Also known as:** GHSA-v8vm-cqh8-q87q

## What is CVE-2026-52888?

CVE-2026-52888 is a medium-severity vulnerability in nocobase, published on 15 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

NocoBase is an AI-powered no-code/low-code platform for building business applications and enterprise solutions. In 2.0.59 and earlier, NocoBase @nocobase/plugin-collection-sql used the checkSQL() function in packages/plugins/@nocobase/plugin-collection-sql/src/server/utils.ts with an incomplete keyword blacklist that did not restrict PostgreSQL system catalog tables such as pg_shadow, pg_roles, and pg_stat_activity, allowing an admin-role user to read password hashes and database metadata through the SQL Collection feature. This vulnerability is fixed in 2.1.0-alpha.46.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), CWE-184 (Incomplete List of Disallowed Inputs)

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

6 open source packages ship an affected version, including @nocobase/plugin-collection-sql.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@nocobase/plugin-collection-sql` | npm | All versions | 2.0.62 |
| `@nocobase/plugin-collection-sql` | npm | All versions | 2.0.62 |
| `@nocobase/plugin-collection-sql` | npm | From 2.1.0-alpha.1 | 2.1.0-alpha.46 |
| `@nocobase/plugin-collection-sql` | npm | From 2.1.0-alpha.1 | 2.1.0-alpha.46 |
| `@nocobase/plugin-collection-sql` | npm | From 2.1.0-beta.1 | 2.1.0-beta.45 |
| `@nocobase/plugin-collection-sql` | npm | From 2.1.0-beta.1 | 2.1.0-beta.45 |

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

Upgrade @nocobase/plugin-collection-sql to a fixed version for your release line: 2.0.62, 2.1.0-alpha.46 or 2.1.0-beta.45.

## Is CVE-2026-52888 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-52888 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-52888 is a medium-severity vulnerability in nocobase, published on 15 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-52888 exists.

Affected packages and fixed versions:
- @nocobase/plugin-collection-sql (npm): affected all versions; fixed in 2.0.62
- @nocobase/plugin-collection-sql (npm): affected all versions; fixed in 2.0.62
- @nocobase/plugin-collection-sql (npm): affected from 2.1.0-alpha.1; fixed in 2.1.0-alpha.46
- @nocobase/plugin-collection-sql (npm): affected from 2.1.0-alpha.1; fixed in 2.1.0-alpha.46
- @nocobase/plugin-collection-sql (npm): affected from 2.1.0-beta.1; fixed in 2.1.0-beta.45
- @nocobase/plugin-collection-sql (npm): affected from 2.1.0-beta.1; fixed in 2.1.0-beta.45

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-52888/ (Markdown: https://insights.sbomify.com/CVE-2026-52888/index.md)
```

## Sources

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

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