Quick answers
- Is CVE-2026-112953 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-112953 being exploited in the wild.
- How severe is CVE-2026-112953?
- Medium severity, with a CVSS score of 4, published 20 October 2026.
- Which products and versions are affected?
- ApostropheCMS Apostrophe before 3.7.1; @apostrophecms/import-export (npm) < 3.7.1, SEMVER:introduced=0,fixed=3.7.1.
- Is there a fix for CVE-2026-112953?
- Yes. @apostrophecms/import-export (npm): upgrade to 3.7.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-112953 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-112953?
- Check whether you run ApostropheCMS Apostrophe or @apostrophecms/import-export (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
- @apostrophecms/import-export (npm): upgrade to 3.7.1 or later
npm install @apostrophecms/import-export@3.7.1
Technical details
The import-export module prior to version 3.7.1 generates predictable export archive filenames, allowing unauthenticated attackers to enumerate and retrieve exported archives from publicly accessible export storage. Exploitation requires that a user with export permission first create an archive, and the attack is prevented if exports are disabled, upload storage is private, or upload delivery requires authentication. The vulnerability is an information disclosure via predictable resource identifiers.
Affected products
- ApostropheCMS Apostrophe before 3.7.1
Identifiers
- CVE-2026-112953
- GHSA-5gc8-frw3-3vqm
Timeline
- 2026-10-20: disclosed
- 2026-10-14: patched