CVE-2026-7357

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-04-29. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
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.

Use after free in GPU in Google Chrome prior to 147.0.7727.138 allowed a remote attacker who had compromised the renderer process to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

CVSS v3
7.5
Vendor severity
HIGHper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: High)
EG Score
7.5(medium)
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
22%
KEV
Not listed

Published

April 28, 2026

Last Modified

July 24, 2026

Advisory Details (2)

Auto-updated Apr 29, 2026
No patch confirmed yet.
generic

Chromium

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

Chrome Releases: Stable Channel Update for Desktop

https://chromereleases.googleblog.com/2026/04/stable-channel-update-for-desktop_28.html

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
chromium100.0.4896.127-1 ... 99.0.4844.84-1~deb11u1 (500 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
chromium113.0.5672.126-1 ... 147.0.7727.55-1~deb13u1 (345 versions)147.0.7727.137-1~deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
chromium138.0.7204.183-1 ... 147.0.7727.55-1~deb13u1 (111 versions)147.0.7727.137-1~deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
chromium138.0.7204.183-1 ... 147.0.7727.55-1~deb13u1 (112 versions)147.0.7727.137-1—

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 5× in last 7d / 31× 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 206 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-7357?
CVE-2026-7357 is a high vulnerability published on April 28, 2026. Use after free in GPU in Google Chrome prior to 147.0.7727.138 allowed a remote attacker who had compromised the renderer process to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
When was CVE-2026-7357 disclosed?
CVE-2026-7357 was first published in the National Vulnerability Database on April 28, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-7357 actively exploited?
CVE-2026-7357 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 77.8% of all scored CVEs.
What is the CVSS score of CVE-2026-7357?
CVE-2026-7357 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-7357?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-7357, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-7357

Explore →

Is Your Infrastructure Affected by CVE-2026-7357?

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

Start Free Scan →Browse All CVEs