CVE-2026-14121

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 62% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: cisa-adp, epss, ghsa
Trending — 4 sources updated this week
9.8EG
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.8Exploit: 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 Chromoting in Google Chrome on Linux prior to 150.0.7871.47 allowed a remote attacker to execute arbitrary code via malicious network traffic. (Chromium security severity: Low)

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

Published

July 1, 2026

Last Modified

July 2, 2026

Advisory Details (2)

Auto-updated Sep 5, 2026
No patch confirmed yet.

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

Frequently asked(5)

What is CVE-2026-14121?
CVE-2026-14121 is a critical vulnerability published on July 1, 2026. Use after free in Chromoting in Google Chrome on Linux prior to 150.0.7871.47 allowed a remote attacker to execute arbitrary code via malicious network traffic. (Chromium security severity: Low)
When was CVE-2026-14121 disclosed?
CVE-2026-14121 was first published in the National Vulnerability Database on July 1, 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-14121 actively exploited?
CVE-2026-14121 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 61.7% of all scored CVEs.
What is the CVSS score of CVE-2026-14121?
CVE-2026-14121 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-14121?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-14121, 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-14121

Explore →

Is Your Infrastructure Affected by CVE-2026-14121?

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