Quick answers
- Is CVE-2026-113658 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-113658 being exploited in the wild.
- How severe is CVE-2026-113658?
- High severity, with a CVSS score of 7.5, 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-113658?
- 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-113658 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-113658?
- 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
A public, unauthenticated Rich Text CSV conversion route accepts multipart uploads and writes them to the system temporary directory before validating the file extension. When validation fails, the staged file is not cleaned up, allowing repeated large rejected uploads to exhaust temporary-disk capacity. The vulnerability requires only a valid CSRF cookie available to public users, with no authentication needed.
Affected products
- ApostropheCMS Apostrophe before 4.33.0
Identifiers
- CVE-2026-113658
- GHSA-qhcq-9pm2-c9w9
Timeline
- 2026-10-20: disclosed
- 2026-09-30: patched