CVE-2026-79139

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-25. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 6 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

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

Improper input validation in Media in Google Chrome on on Windows prior to 152.0.7977.65 allowed a remote attacker who had compromised the renderer process to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Medium)

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

Published

August 25, 2026

Last Modified

August 27, 2026

Advisory Details (2)

Auto-updated Aug 26, 2026
No patch confirmed yet.
generic

Chromium

https://issues.chromium.org/issues/532917452
generic

Chrome Releases: Stable Channel Update for Desktop

https://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_0256176589.html

Vendor Advisories for CVE-2026-79139(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 28× in last 7d / 28× 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-08-30 03:14 UTCEG score recompute
  2. 2026-08-30 03:14 UTCVendor advisory
  3. 2026-08-30 03:14 UTCGHSA enrichment
  4. 2026-08-30 01:22 UTCEPSS rescore
  5. 2026-08-29 14:54 UTCVendor advisory
  6. 2026-08-29 14:54 UTCGHSA enrichment
  7. 2026-08-29 02:34 UTCEG score recompute
  8. 2026-08-29 02:34 UTCVendor advisory
  9. 2026-08-29 02:34 UTCGHSA enrichment
  10. 2026-08-28 21:42 UTCEPSS rescore
  11. 2026-08-28 14:12 UTCGHSA enrichment
  12. 2026-08-28 01:52 UTCEG score recompute
  13. 2026-08-28 01:52 UTCGHSA enrichment
  14. 2026-08-27 14:25 UTCEPSS rescore
  15. 2026-08-27 13:33 UTCGHSA enrichment
  16. 2026-08-27 04:27 UTCGHSA enrichment
  17. 2026-08-27 04:04 UTCEG score recompute
  18. 2026-08-27 04:04 UTCGHSA enrichment
  19. 2026-08-26 16:39 UTCGHSA enrichment
  20. 2026-08-26 15:43 UTCEG score recompute
  21. 2026-08-26 15:43 UTCGHSA enrichment
  22. 2026-08-26 14:47 UTCEPSS rescore
  23. 2026-08-26 12:58 UTCEG score recompute▲ 1.00
  24. 2026-08-26 12:58 UTCGHSA enrichment
  25. 2026-08-26 12:57 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
Show 3 more
  1. 2026-08-25 21:26 UTCNVD update
  2. 2026-08-25 20:28 UTCEG score recompute
  3. 2026-08-25 20:25 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-79139?
CVE-2026-79139 is a high vulnerability published on August 25, 2026. Improper input validation in Media in Google Chrome on on Windows prior to 152.0.7977.65 allowed a remote attacker who had compromised the renderer process to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Medium)
When was CVE-2026-79139 disclosed?
CVE-2026-79139 was first published in the National Vulnerability Database on August 25, 2026, with the most recent update on August 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-79139 actively exploited?
CVE-2026-79139 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 71.8% of all scored CVEs.
What is the CVSS score of CVE-2026-79139?
CVE-2026-79139 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-79139?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-79139, 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-79139

Explore →

Is Your Infrastructure Affected by CVE-2026-79139?

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

Start Free Scan →Browse All CVEs