Quick answers
- Is CVE-2026-113652 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-113652 being exploited in the wild.
- How severe is CVE-2026-113652?
- Medium severity, with a CVSS score of 5.6, published 20 October 2026.
- Which products and versions are affected?
- ApostropheCMS Apostrophe 1.25.0 to 1.28.0; uploadfs (npm) >= 1.25.0, < 1.28.0, SEMVER:introduced=1.25.0,fixed=1.28.0.
- Is there a fix for CVE-2026-113652?
- Yes. uploadfs (npm): upgrade to 1.28.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-113652 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-113652?
- Check whether you run ApostropheCMS Apostrophe or uploadfs (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
- uploadfs (npm): upgrade to 1.28.0 or later
npm install uploadfs@1.28.0
Technical details
The uploadfs Azure backend embeds a full SAS query string into the BlobServiceClient URL during container creation, and Azure SDK v12 derived clients inherit that query string, causing it to appear in every public attachment URL. This affects versions 1.25.0 through 1.28.0 when uploadfs is configured with the Azure backend and sas: true. An unauthenticated attacker with knowledge of a public attachment URL gains the account-level SAS token and can perform operations permitted by that token.
Affected products
- ApostropheCMS Apostrophe 1.25.0 to 1.28.0
Identifiers
- CVE-2026-113652
- GHSA-hhph-8536-gfq5
Timeline
- 2026-10-20: disclosed