Quick answers
- Is CVE-2026-112952 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-112952 being exploited in the wild.
- How severe is CVE-2026-112952?
- Medium severity, with a CVSS score of 4.3, published 20 October 2026.
- Which products and versions are affected?
- ApostropheCMS before 4.34.0; apostrophe (npm) < 4.34.0, SEMVER:introduced=0,fixed=4.34.0.
- Is there a fix for CVE-2026-112952?
- Yes. apostrophe (npm): upgrade to 4.34.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-112952 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-112952?
- Check whether you run ApostropheCMS or apostrophe (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- apostrophe (npm): upgrade to 4.34.0 or later
npm install apostrophe@4.34.0
Technical details
The POST /api/v1/@apostrophecms/doc/slugTaken endpoint returns a boolean indicating slug availability without applying any permission or type filters, allowing enumeration across all document visibility levels. Any authenticated user, including those with basic editor privileges, can query this endpoint to discover the slug namespace of restricted content. The vulnerability is fixed in version 4.34.0 through permission-aware filtering of the API response.
Affected products
- ApostropheCMS ApostropheCMS before 4.34.0
Identifiers
- CVE-2026-112952
- GHSA-f66c-mpj2-3r8h
Timeline
- 2026-10-20: disclosed