CVE-2026-5290

CRITICALNVD 9.69.6—
EchelonGraph scoreMEDIUM confidence

Score 9.6 from GitHub Security Advisory (severity: CRITICAL) published 2026-04-01. NVD baseline CVSS 9.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
9.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.6Exploit: 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 Compositing in Google Chrome prior to 146.0.7680.178 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)

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

Published

April 1, 2026

Last Modified

April 1, 2026

Advisory Details (2)

Auto-updated Sep 14, 2026
⚠️ Active exploitation confirmed. No patch confirmed yet.
generic

Chromium

https://issues.chromium.org/issues/496205576
generic🔴 Active Exploitation

Chrome Releases: Stable Channel Update for Desktop

https://chromereleases.googleblog.com/2026/03/stable-channel-update-for-desktop_31.html

Vendor Advisories for CVE-2026-5290(1)

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

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 ... 146.0.7680.80-1~deb13u1 (333 versions)146.0.7680.177-1~deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
chromium138.0.7204.183-1 ... 146.0.7680.80-1~deb13u1 (99 versions)146.0.7680.177-1~deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
chromium138.0.7204.183-1 ... 146.0.7680.80-1~deb13u1 (100 versions)146.0.7680.177-1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 27× 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 253 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-5290?
CVE-2026-5290 is a critical vulnerability published on April 1, 2026. Use after free in Compositing in Google Chrome prior to 146.0.7680.178 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)
When was CVE-2026-5290 disclosed?
CVE-2026-5290 was first published in the National Vulnerability Database on April 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-5290 actively exploited?
CVE-2026-5290 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 76.0% of all scored CVEs.
What is the CVSS score of CVE-2026-5290?
CVE-2026-5290 has a CVSS v3 base score of 9.6 (NVD).
How do I remediate CVE-2026-5290?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-5290, 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-5290

Explore →

Is Your Infrastructure Affected by CVE-2026-5290?

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

Start Free Scan →Browse All CVEs