CVE-2026-53609

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 85% 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
9.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

ApostropheCMS is an open-source Node.js content management system. In versions up to and including 4.30.0, apos.util.set() traverses dot-notation paths without sanitizing __proto__, allowing an authenticated editor to write arbitrary values to Object.prototype via the $pullAll patch operator. A confirmed gadget in publicApiCheck() causes this to bypass authorization on all piece-type REST API endpoints for every subsequent unauthenticated request, for the lifetime of the Node.js process. As of time of publication, no known patched versions are available.

CVSS v3
9.1
EG Score
9.1(medium)
EPSS
14.6%
KEV
Not listed

Published

June 12, 2026

Last Modified

June 15, 2026

Advisory Details (1)

Auto-updated Jun 12, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Server-Side Prototype Pollution in apos.util.set via patch operators leads to process-wide authorization bypass · Advisory · apostrophecms/apostrophe · GitHub

https://github.com/apostrophecms/apostrophe/security/advisories/GHSA-6h5j-32cf-4253

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 44× in last 7d / 201× 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.

Showing the most recent 100 of 201 total refreshes for this CVE.

  1. 2026-07-12 07:59 UTCEG score recompute
  2. 2026-07-12 05:46 UTCEPSS rescore
  3. 2026-07-12 03:52 UTCEG score recompute
  4. 2026-07-11 23:38 UTCEG score recompute
  5. 2026-07-11 19:33 UTCEG score recompute
  6. 2026-07-11 15:28 UTCEG score recompute
  7. 2026-07-11 11:21 UTCEG score recompute
  8. 2026-07-11 08:27 UTCEPSS rescore
  9. 2026-07-11 08:27 UTCEPSS rescore
  10. 2026-07-11 07:16 UTCEG score recompute
  11. 2026-07-11 02:52 UTCEG score recompute
  12. 2026-07-10 21:32 UTCEG score recompute
  13. 2026-07-10 17:27 UTCEG score recompute
  14. 2026-07-10 13:04 UTCEG score recompute
  15. 2026-07-10 03:19 UTCEG score recompute
  16. 2026-07-09 21:35 UTCEG score recompute
  17. 2026-07-09 19:10 UTCEPSS rescore
  18. 2026-07-09 19:10 UTCEPSS rescore
  19. 2026-07-09 13:25 UTCEG score recompute
  20. 2026-07-09 09:10 UTCEG score recompute
  21. 2026-07-09 05:03 UTCEG score recompute
  22. 2026-07-09 00:57 UTCEG score recompute
  23. 2026-07-08 20:33 UTCEG score recompute
  24. 2026-07-08 15:16 UTCEG score recompute
  25. 2026-07-08 15:16 UTCEPSS rescore
Show 75 more
  1. 2026-07-08 15:16 UTCEPSS rescore
  2. 2026-07-08 10:45 UTCEG score recompute
  3. 2026-07-08 06:38 UTCEG score recompute
  4. 2026-07-08 01:27 UTCEG score recompute
  5. 2026-07-07 21:21 UTCEG score recompute
  6. 2026-07-07 13:53 UTCEG score recompute
  7. 2026-07-07 13:46 UTCEPSS rescore
  8. 2026-07-07 13:46 UTCEPSS rescore
  9. 2026-07-07 05:06 UTCEG score recompute
  10. 2026-07-07 00:55 UTCEG score recompute
  11. 2026-07-06 16:27 UTCEPSS rescore
  12. 2026-07-06 16:27 UTCEPSS rescore
  13. 2026-07-06 06:55 UTCEG score recompute
  14. 2026-07-06 02:23 UTCEPSS rescore
  15. 2026-07-06 02:23 UTCEPSS rescore
  16. 2026-07-06 01:56 UTCEG score recompute
  17. 2026-07-05 21:51 UTCEG score recompute
  18. 2026-07-05 17:46 UTCEG score recompute
  19. 2026-07-05 13:40 UTCEG score recompute
  20. 2026-07-05 09:35 UTCEG score recompute
  21. 2026-07-05 03:17 UTCEG score recompute
  22. 2026-07-05 02:31 UTCEPSS rescore
  23. 2026-07-05 02:30 UTCEPSS rescore
  24. 2026-07-04 23:09 UTCEG score recompute
  25. 2026-07-04 19:05 UTCEG score recompute
  26. 2026-07-04 14:27 UTCEG score recompute
  27. 2026-07-04 10:23 UTCEG score recompute
  28. 2026-07-04 06:31 UTCEPSS rescore
  29. 2026-07-04 06:31 UTCEPSS rescore
  30. 2026-07-03 22:46 UTCEG score recompute
  31. 2026-07-03 18:35 UTCEG score recompute
  32. 2026-07-03 14:31 UTCEG score recompute
  33. 2026-07-03 08:31 UTCEG score recompute
  34. 2026-07-03 04:12 UTCEG score recompute
  35. 2026-07-02 23:41 UTCEG score recompute
  36. 2026-07-02 19:36 UTCEG score recompute
  37. 2026-07-02 15:30 UTCEG score recompute
  38. 2026-07-02 11:21 UTCEG score recompute
  39. 2026-07-02 06:56 UTCEG score recompute
  40. 2026-07-02 02:50 UTCEG score recompute
  41. 2026-07-01 22:45 UTCEG score recompute
  42. 2026-07-01 18:14 UTCEG score recompute
  43. 2026-07-01 15:07 UTCEPSS rescore
  44. 2026-07-01 14:09 UTCEG score recompute
  45. 2026-07-01 10:05 UTCEG score recompute
  46. 2026-07-01 05:59 UTCEG score recompute
  47. 2026-07-01 01:43 UTCEG score recompute
  48. 2026-06-30 23:22 UTCEPSS rescore
  49. 2026-06-30 21:38 UTCEG score recompute
  50. 2026-06-30 17:33 UTCEG score recompute
  51. 2026-06-30 13:17 UTCEG score recompute
  52. 2026-06-30 07:05 UTCEG score recompute
  53. 2026-06-30 02:51 UTCEG score recompute
  54. 2026-06-29 22:46 UTCEG score recompute
  55. 2026-06-29 18:40 UTCEG score recompute
  56. 2026-06-29 14:20 UTCEG score recompute
  57. 2026-06-29 14:06 UTCEPSS rescore
  58. 2026-06-29 14:06 UTCEPSS rescore
  59. 2026-06-29 10:15 UTCEG score recompute
  60. 2026-06-29 06:10 UTCEG score recompute
  61. 2026-06-29 01:21 UTCEG score recompute
  62. 2026-06-28 21:16 UTCEG score recompute
  63. 2026-06-28 17:11 UTCEG score recompute
  64. 2026-06-28 14:07 UTCEPSS rescore
  65. 2026-06-28 13:05 UTCEG score recompute
  66. 2026-06-28 08:59 UTCEG score recompute
  67. 2026-06-28 04:56 UTCEPSS rescore
  68. 2026-06-28 04:56 UTCEPSS rescore
  69. 2026-06-28 04:55 UTCEG score recompute
  70. 2026-06-28 00:51 UTCEG score recompute
  71. 2026-06-27 20:47 UTCEG score recompute
  72. 2026-06-27 16:41 UTCEG score recompute
  73. 2026-06-27 12:36 UTCEG score recompute
  74. 2026-06-27 08:31 UTCEG score recompute
  75. 2026-06-27 04:26 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-53609?
CVE-2026-53609 is a critical vulnerability published on June 12, 2026. ApostropheCMS is an open-source Node.js content management system. In versions up to and including 4.30.0, apos.util.set() traverses dot-notation paths without sanitizing proto, allowing an authenticated editor to write arbitrary values to Object.prototype via the $pullAll patch operator. A…
When was CVE-2026-53609 disclosed?
CVE-2026-53609 was first published in the National Vulnerability Database on June 12, 2026, with the most recent update on June 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53609 actively exploited?
CVE-2026-53609 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 14.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53609?
CVE-2026-53609 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-53609?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53609, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-53609

Explore →

Is Your Infrastructure Affected by CVE-2026-53609?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs