CVE-2026-13814

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-01. 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 — 4 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.

Use after free in Views in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who convinced a user to engage in specific UI gestures 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
38(Track)
EG Risk 38/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%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
23%
KEV
Not listed

Published

June 30, 2026

Last Modified

July 2, 2026

Advisory Details (2)

Auto-updated Jul 2, 2026
No patch confirmed yet.

Vendor Advisories for CVE-2026-13814(2)

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 ... 149.0.7827.53-1~deb13u1 (378 versions)150.0.7871.46-1~deb12u1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
chromium138.0.7204.183-1 ... 150.0.7871.46-1~deb12u1 (144 versions)150.0.7871.46-1~deb13u1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
chromium138.0.7204.183-1 ... 150.0.7871.46-1~deb13u1 (145 versions)150.0.7871.46-1

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 86× 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 266 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-13814?
CVE-2026-13814 is a high vulnerability published on June 30, 2026. Use after free in Views in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who convinced a user to engage in specific UI gestures to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
When was CVE-2026-13814 disclosed?
CVE-2026-13814 was first published in the National Vulnerability Database on June 30, 2026, with the most recent update on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-13814 actively exploited?
CVE-2026-13814 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.1% of all scored CVEs.
What is the CVSS score of CVE-2026-13814?
CVE-2026-13814 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-13814?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-13814, 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-13814

Explore →

Is Your Infrastructure Affected by CVE-2026-13814?

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