ApostropheCMS is an open-source Node.js content management system. In 4.32.0 and earlier, PATCH /api/v1/article/:id accepts the inherited path toString.call and passes it through the utility module to apos.util.set() and apos.util.get(), allowing an authenticated editor to overwrite the shared Object.prototype.toString function's call property and cause a persistent process-wide denial of service until restart.
CVE-2026-71553
This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 77% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.1
- EG Score
- 7.1(medium)
- EG Risk
- 32(Track)EG Risk 32/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity71% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 23%
- KEV
- Not listed
Published
August 17, 2026
Last Modified
August 17, 2026
Advisory Details (2)
Auto-updated Aug 17, 20262nd-order prototype pollution via PATCH leading to single-request persistent DoS · Advisory · apostrophecms/apostrophe · GitHub
https://github.com/apostrophecms/apostrophe/security/advisories/GHSA-vmg4-6gfg-83qxcommit 5a3746aaed49 (apostrophecms/apostrophe)
Fix landed in apostrophecms/apostrophe commit 5a3746aaed49 — awaiting tagged release
https://github.com/apostrophecms/apostrophe/commit/5a3746aaed49761e171c2cbfe793267c959829fdWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 19× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-25 19:31 UTCEG score recompute
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 19:36 UTCEG score recompute
- 2026-08-23 07:48 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 07:56 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 08:01 UTCEG score recompute
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-19 20:11 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 20:19 UTCEG score recompute
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 08:18 UTCEG score recompute
- 2026-08-17 20:20 UTCEG score recompute
- 2026-08-17 20:11 UTCEG score recompute
- 2026-08-17 20:09 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-71553?
When was CVE-2026-71553 disclosed?
Is CVE-2026-71553 actively exploited?
What is the CVSS score of CVE-2026-71553?
How do I remediate CVE-2026-71553?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-71553
Is Your Infrastructure Affected by CVE-2026-71553?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.