NocoBase: SQL injection in /api/myInAppChannels:list filter to PG-superuser RCE
CVE-2026-52887GHSA-p849-8hwh-84j9
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (@nocobase/plugin-notification-in-app-message 2.0.61), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
npm @nocobase/plugin-notification-in-app-message
- Affected
- <= 2.0.60
- Fixed in
- 2.0.61
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-p849-8hwh-84j9 lists affected ranges: npm @nocobase/plugin-notification-in-app-message >=0 <=2.0.60
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-p849-8hwh-84j9 lists affected ranges: npm @nocobase/plugin-notification-in-app-message >=0 <2.0.61 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 10.0 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
- EPSS
- CVE-2026-52887: 0.89% estimated exploitation activity in the next 30 days; percentile 59.48 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary GET /api/myInAppChannels:list accepts a structured filter query parameter. The handler for the latestMsgReceiveTimestamp field splices the $lt value directly into a Sequelize.literal() template string with no escape, type cast, or parameter binding. The action ACL is loggedIn, so any authenticated account reaches it. The default auth-basic authenticator ships allowSignUp: true, so the account is obtainable anonymously. The injection is reachable with the URL parameter filter[latestMsgReceiveTimestamp][$lt]=<expression. The pg driver in front of Sequelize accepts stacked statements, so the chain extends from boolean and timing oracles to multi-statement payloads. The shipped docker-compose.yml creates the DB role nocobase on a stock postgres:16 image, which assigns the rolsuper attribute by default. COPY ... TO PROGRAM '...' therefore runs shell commands as uid=999(postgres) inside the database container. Result: any anonymous visitor signs up, signs in, and exfiltrates…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-p849-8hwh-84j9
- Revision 2 · amended ·
Amended from osv record GHSA-p849-8hwh-84j9
- Revision 1 · created ·
Published from ghsa record GHSA-p849-8hwh-84j9
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-52887 Advisory: NocoBase: SQL injection in /api/myInAppChannels:list filter to PG-superuser RCE IDs: CVE-2026-52887, GHSA-p849-8hwh-84j9 Record: https://patchnext.com/advisories/cve-2026-52887 (revision 3, source checked 26 Oct 2026, 13:00 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Critical (CVSS 10.0) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: @nocobase/plugin-notification-in-app-message 2.0.61. A vendor fix does not mean a deployment is fixed. ## Affected components - npm @nocobase/plugin-notification-in-app-message: affected <= 2.0.60; fixed in 2.0.61 ## Suggested inspection (read-only) - `npm ls @nocobase/plugin-notification-in-app-message --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on @nocobase/plugin-notification-in-app-message. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-p849-8hwh-84j9 (GitHub-reviewed advisory GHSA-p849-8hwh-84j9 lists affected ranges: npm @nocobase/plugin-notification-in-app-message >=0 <=2.0.60) - Verified: https://osv.dev/vulnerability/GHSA-p849-8hwh-84j9 (OSV record GHSA-p849-8hwh-84j9 lists affected ranges: npm @nocobase/plugin-notification-in-app-message >=0 <2.0.61 (fixed)) Commands are suggestions: review each one before running it.
Loading voting…