CVE-2026-87652

LOWPre-NVD 3.13.1—
EchelonGraph scoreHIGH confidence

Score 3.1 from GitHub Security Advisory (severity: LOW) published 2026-09-09. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 3.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 4 sources updated this week
3.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.1Exploit: None knownExposed: 0

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

Incorrect authorization in PushAPI in Google Chrome prior to 153.0.8010.36 allowed a remote attacker who had compromised the renderer process to bypass web origin policy via a crafted HTML page. (Chromium security severity: Medium)

CVSS v3
3.1
Vendor severity
MEDIUMper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: Medium)
EG Score
3.1(high)
EG Risk
14(Track)
EG Risk 14/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 computed
Severity31% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
14%
KEV
Not listed

Published

September 9, 2026

Last Modified

September 9, 2026

References (2)

Vendor Advisories for CVE-2026-87652(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

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

  1. 2026-09-24 14:04 UTCEPSS rescore
  2. 2026-09-24 08:26 UTCEG score recompute
  3. 2026-09-24 08:26 UTCVendor advisory
  4. 2026-09-24 08:26 UTCGHSA enrichment
  5. 2026-09-23 17:54 UTCEPSS rescore
  6. 2026-09-22 16:01 UTCEPSS rescore
  7. 2026-09-21 21:09 UTCEPSS rescore
  8. 2026-09-21 10:39 UTCEG score recompute
  9. 2026-09-21 10:39 UTCVendor advisory
  10. 2026-09-21 10:39 UTCGHSA enrichment
  11. 2026-09-20 20:16 UTCEPSS rescore
  12. 2026-09-18 19:28 UTCEPSS rescore
  13. 2026-09-18 12:52 UTCEG score recompute
  14. 2026-09-18 12:52 UTCVendor advisory
  15. 2026-09-18 12:52 UTCGHSA enrichment
  16. 2026-09-17 19:32 UTCEPSS rescore
  17. 2026-09-16 14:09 UTCEPSS rescore
  18. 2026-09-16 05:15 UTCEPSS rescore
  19. 2026-09-15 15:04 UTCEG score recompute
  20. 2026-09-15 15:04 UTCVendor advisory
  21. 2026-09-15 15:04 UTCGHSA enrichment
  22. 2026-09-15 03:12 UTCEPSS rescore
  23. 2026-09-12 17:16 UTCEG score recompute
  24. 2026-09-12 17:16 UTCGHSA enrichment
  25. 2026-09-11 14:53 UTCEPSS rescore
Show 11 more
  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-09 19:29 UTCEG score recompute
  3. 2026-09-09 19:29 UTCGHSA enrichment
  4. 2026-09-09 18:28 UTCGHSA enrichment
  5. 2026-09-09 17:20 UTCEG score recompute▼ 3.40
  6. 2026-09-09 17:20 UTCGHSA enrichment
  7. 2026-09-09 17:19 UTCMITRE cvelistV5CVSS v3 → 3.1 · severity → LOW
  8. 2026-09-09 15:58 UTCGHSA enrichment
  9. 2026-09-09 01:22 UTCNVD update
  10. 2026-09-09 01:01 UTCEG score recompute
  11. 2026-09-09 00:57 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-87652?
CVE-2026-87652 is a low vulnerability published on September 9, 2026. Incorrect authorization in PushAPI in Google Chrome prior to 153.0.8010.36 allowed a remote attacker who had compromised the renderer process to bypass web origin policy via a crafted HTML page. (Chromium security severity: Medium)
When was CVE-2026-87652 disclosed?
CVE-2026-87652 was first published in the National Vulnerability Database on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-87652 actively exploited?
CVE-2026-87652 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 86.1% of all scored CVEs.
What is the CVSS score of CVE-2026-87652?
CVE-2026-87652 has a CVSS v3.1 base score of 3.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-87652?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-87652, 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-87652

Explore →

Is Your Infrastructure Affected by CVE-2026-87652?

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

Book a Demo →Browse All CVEs