CVE-2026-52888
MEDIUMCVE-2026-52888 is a medium-severity (CVSS 6.8) CWE-184 vulnerability in @nocobase/plugin-collection-sql. O3 Security confirms whether CVE-2026-52888 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
NocoBase: Sensitive Data Exposure via SQL Blacklist Bypass
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
@nocobase/plugin-collection-sqlnpmDescription
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @nocobase/plugin-collection-sql | all versions | 2.0.62 |
| 📦npm | @nocobase/plugin-collection-sql | ≥ 2.1.0-alpha.1&&< 2.1.0-alpha.46 | 2.1.0-alpha.46 |
| 📦npm | @nocobase/plugin-collection-sql | ≥ 2.1.0-beta.1&&< 2.1.0-beta.45 | 2.1.0-beta.45 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @nocobase/plugin-collection-sql. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update @nocobase/plugin-collection-sql to 2.0.62 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-52888 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2026-52888 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2026-52888. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-52888 in your dependencies?
O3 detects CVE-2026-52888 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.