Quick answers
- Is CVE-2026-113653 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-113653 being exploited in the wild.
- How severe is CVE-2026-113653?
- Medium severity, with a CVSS score of 4, published 20 October 2026.
- Which products and versions are affected?
- ApostropheCMS Apostrophe before 4.33.0; apostrophe (npm) < 4.33.0, SEMVER:introduced=0,fixed=4.33.0.
- Is there a fix for CVE-2026-113653?
- 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-113653 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-113653?
- Check whether you run ApostropheCMS Apostrophe 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 viewRole access control check is not applied to anonymous site visitors when user objects are serialized in publicly rendered relationships or expressly enabled public APIs. While relationships do not automatically publish full user objects and password hashes remain protected, conditional disclosure of user fields is possible through inadequately limited templates. This is an authorization bypass affecting the API layer.
Affected products
- ApostropheCMS Apostrophe before 4.33.0
Identifiers
- CVE-2026-113653
- GHSA-xf6w-q65w-4f2w
Timeline
- 2026-10-20: disclosed