CVE-2026-14130

MEDIUMNVD 4.34.3—
EchelonGraph scoreHIGH confidence

Score 4.3 from GitHub Security Advisory published 2026-07-01. NVD baseline CVSS 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
4.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.3Exploit: NoneExposed: 0

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

Incorrect security UI in Omnibox in Google Chrome prior to 150.0.7871.47 allowed a remote attacker to perform UI spoofing via a crafted HTML page. (Chromium security severity: Low)

CVSS v3
4.3
EG Score
4.3(high)
EG Risk
24(Track)
EG Risk 24/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
Severity43% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
10.4%
KEV
Not listed

Published

July 1, 2026

Last Modified

July 2, 2026

Advisory Details (2)

Auto-updated Jul 4, 2026
No patch confirmed yet.
generic

Chromium

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

Chrome Releases: Stable Channel Update for Desktop

https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html

Vendor Advisories for CVE-2026-14130(2)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 54× 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-07-23 03:05 UTCEG score recompute
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-21 15:24 UTCEPSS rescore
  4. 2026-07-20 17:08 UTCEPSS rescore
  5. 2026-07-19 14:30 UTCEPSS rescore
  6. 2026-07-19 02:28 UTCEPSS rescore
  7. 2026-07-18 10:04 UTCEPSS rescore
  8. 2026-07-16 17:02 UTCEPSS rescore
  9. 2026-07-16 10:58 UTCVendor advisory
  10. 2026-07-16 10:58 UTCGHSA enrichment
  11. 2026-07-15 16:57 UTCEPSS rescore
  12. 2026-07-15 10:17 UTCVendor advisory
  13. 2026-07-15 10:17 UTCGHSA enrichment
  14. 2026-07-15 02:00 UTCEPSS rescore
  15. 2026-07-14 09:36 UTCVendor advisory
  16. 2026-07-14 09:36 UTCGHSA enrichment
  17. 2026-07-13 22:30 UTCEPSS rescore
  18. 2026-07-13 08:53 UTCGHSA enrichment
  19. 2026-07-13 06:12 UTCEPSS rescore
  20. 2026-07-12 08:13 UTCVendor advisory
  21. 2026-07-12 08:13 UTCGHSA enrichment
  22. 2026-07-12 05:46 UTCEPSS rescore
  23. 2026-07-11 08:27 UTCEPSS rescore
  24. 2026-07-11 07:32 UTCVendor advisory
  25. 2026-07-11 07:32 UTCGHSA enrichment
Show 29 more
  1. 2026-07-10 06:52 UTCVendor advisory
  2. 2026-07-10 06:52 UTCGHSA enrichment
  3. 2026-07-09 19:10 UTCEPSS rescore
  4. 2026-07-09 06:10 UTCVendor advisory
  5. 2026-07-09 06:10 UTCGHSA enrichment
  6. 2026-07-08 15:15 UTCEPSS rescore
  7. 2026-07-08 15:15 UTCEPSS rescore
  8. 2026-07-08 05:29 UTCVendor advisory
  9. 2026-07-08 05:29 UTCGHSA enrichment
  10. 2026-07-07 13:46 UTCEPSS rescore
  11. 2026-07-07 04:49 UTCVendor advisory
  12. 2026-07-07 04:49 UTCGHSA enrichment
  13. 2026-07-06 16:27 UTCEPSS rescore
  14. 2026-07-06 04:09 UTCVendor advisory
  15. 2026-07-06 04:09 UTCGHSA enrichment
  16. 2026-07-06 02:23 UTCEPSS rescore
  17. 2026-07-05 03:28 UTCVendor advisory
  18. 2026-07-05 03:28 UTCGHSA enrichment
  19. 2026-07-05 02:30 UTCEPSS rescore
  20. 2026-07-05 02:30 UTCEPSS rescore
  21. 2026-07-04 06:31 UTCEPSS rescore
  22. 2026-07-04 02:48 UTCEG score recompute▲ 4.30
  23. 2026-07-04 02:48 UTCVendor advisory
  24. 2026-07-04 02:47 UTCGHSA enrichment
  25. 2026-07-01 17:06 UTCNVD updateCVSS v3 → 4.3 · severity → MEDIUM
  26. 2026-07-01 15:06 UTCEPSS rescore
  27. 2026-07-01 15:06 UTCEPSS rescore
  28. 2026-07-01 01:23 UTCEG score recompute
  29. 2026-07-01 01:23 UTCGHSA enrichment

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-14130?
CVE-2026-14130 is a medium vulnerability published on July 1, 2026. Incorrect security UI in Omnibox in Google Chrome prior to 150.0.7871.47 allowed a remote attacker to perform UI spoofing via a crafted HTML page. (Chromium security severity: Low)
When was CVE-2026-14130 disclosed?
CVE-2026-14130 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-14130 actively exploited?
CVE-2026-14130 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 10.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-14130?
CVE-2026-14130 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-14130?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-14130, 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-14130

Explore →

Is Your Infrastructure Affected by CVE-2026-14130?

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

Start Free Scan →Browse All CVEs