Quick answers
- Is CVE-2026-71553 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-71553 being exploited in the wild.
- How severe is CVE-2026-71553?
- High severity, with a CVSS score of 4, published 17 August 2026.
- Which products and versions are affected?
- apostrophe (npm) <= 4.32.0, SEMVER:introduced=0,last_affected=4.32.0.
- Is there a fix for CVE-2026-71553?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-71553 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-71553?
- Check whether you run 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.
Technical details
The vulnerability is a second-order prototype pollution flaw in the PATCH API endpoint (e.g., PATCH /api/v1/article/<id>) that fails to sanitize user input before merging it into JavaScript objects. An authenticated attacker with editor privileges can inject a crafted JSON payload such as {"toString.call":"x"} to overwrite critical prototype chain properties, including global methods like toString(). This causes all subsequent operations that rely on these methods to fail catastrophically, resulting in a persistent denial of service that affects the entire application and persists across requests until the server is restarted. The attack requires valid editor-level authentication but no user interaction or complex exploitation steps.
Affected products
- ApostropheCMS apostrophe <= 4.32.0
Identifiers
- CVE-2026-71553
- GHSA-vmg4-6gfg-83qx
Timeline
- 2026-09-02: disclosed: Published to GitHub Advisory Database
- 2026-08-17: advisory: Published to NVD
- 2026-08-12: other: Vulnerability reported
References
- https://api.github.com/users/breakingsystems
- https://github.com/breakingsystems
- https://api.github.com/users/breakingsystems/gists%7B/gist_id%7D
- https://api.github.com/users/breakingsystems/repos
- https://avatars.githubusercontent.com/u/72152138?v=4
- https://api.github.com/users/breakingsystems/events%7B/privacy%7D