# CVE-2026-52887: NocoBase: SQL injection in /api/myInAppChannels:list filter to PG-superuser RCE

> Authenticated users can exploit SQL injection in the notification plugin to execute arbitrary PostgreSQL commands and achieve remote code execution.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Jul 2026
- **Updated:** 20 Jul 2026
- **Also known as:** GHSA-p849-8hwh-84j9

## What is CVE-2026-52887?

CVE-2026-52887 is a critical SQL injection vulnerability in nocobase, published on 15 Jul 2026. An attacker can exploit it over the internet without logging in, 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. Prior to 2.0.61, NocoBase @nocobase/plugin-notification-in-app-message exposed GET /api/myInAppChannels:list, where the filter[latestMsgReceiveTimestamp][$lt] value was inserted into a Sequelize.literal() template string without escaping or parameter binding, allowing a signed-up authenticated user to run stacked PostgreSQL statements and potentially execute commands with COPY ... TO PROGRAM. This vulnerability is fixed in 2.0.61.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

2 open source packages ship an affected version, including @nocobase/plugin-notification-in-app-message.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@nocobase/plugin-notification-in-app-message` | npm | All versions | 2.0.61 |
| `@nocobase/plugin-notification-in-app-message` | npm | All versions | 2.0.61 |

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

Upgrade @nocobase/plugin-notification-in-app-message to 2.0.61 or later.

## Is CVE-2026-52887 being exploited?

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

Public exploit code:

- CVE-2026-52887 — NocoBase SQL injection -> PostgreSQL-superuser RCE (myInAppChannels:list filter, CVSS 10.0). Author PoC + source analysis + docker lab. (github_poc): https://github.com/BiiTts/CVE-2026-52887-NocoBase-SQLi-RCE
- NocoBase security research and exploitation notes for CVE-2026-52887, structured for documentation and reproduction scripts. (github_poc): https://github.com/pentrestion/nocobase-cve-2026-52887

## Fix prompt for AI coding agents

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

What it is: CVE-2026-52887 is a critical SQL injection vulnerability in nocobase, published on 15 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-52887 exists.

Affected packages and fixed versions:
- @nocobase/plugin-notification-in-app-message (npm): affected all versions; fixed in 2.0.61
- @nocobase/plugin-notification-in-app-message (npm): affected all versions; fixed in 2.0.61

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

## Sources

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

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