Quick answers
- Is CVE-2026-113668 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-113668 being exploited in the wild.
- How severe is CVE-2026-113668?
- Medium severity, with a CVSS score of 5.3, published 20 October 2026.
- Which products and versions are affected?
- ApostropheCMS 4.32.2 and earlier; apostrophe (npm) < 4.33.0, SEMVER:introduced=0,fixed=4.33.0.
- Is there a fix for CVE-2026-113668?
- Yes. apostrophe (npm): upgrade to 4.33.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-113668 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-113668?
- 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.33.0 or later
npm install apostrophe@4.33.0
Technical details
The GET /api/v1/<piece-type>/:_id/locales and GET /api/v1/@apostrophecms/page/:_id/locales endpoints in the piece-type and page modules lack the publicApiCheckAsync authorization gate applied to sibling read routes. An unauthenticated attacker with knowledge of a document ID can query these endpoints to determine document existence and enumerate published locales, bypassing the public-API access policy intended to protect read operations.
Affected products
- ApostropheCMS ApostropheCMS 4.32.2 and earlier
Identifiers
- CVE-2026-113668
- GHSA-gqh3-7856-rjjg
Timeline
- 2026-10-20: disclosed