CVE-2026-13868

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory published 2026-07-01. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.5Exploit: NoneExposed: 0

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

Inappropriate implementation in Network in Google Chrome on Android prior to 150.0.7871.47 allowed a remote attacker who had compromised the renderer process to bypass site isolation via a crafted HTML page. (Chromium security severity: Medium)

CVSS v3
6.5
EG Score
6.5(high)
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
Severity65% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
12.3%
KEV
Not listed

Published

June 30, 2026

Last Modified

July 6, 2026

Advisory Details (2)

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

Chromium

https://issues.chromium.org/issues/497453475
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-13868(2)

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

Weakness Classification(1)

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

Data Freshness Timeline

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-13868?
CVE-2026-13868 is a medium vulnerability published on June 30, 2026. Inappropriate implementation in Network in Google Chrome on Android prior to 150.0.7871.47 allowed a remote attacker who had compromised the renderer process to bypass site isolation via a crafted HTML page. (Chromium security severity: Medium)
When was CVE-2026-13868 disclosed?
CVE-2026-13868 was first published in the National Vulnerability Database on June 30, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-13868 actively exploited?
CVE-2026-13868 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 12.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-13868?
CVE-2026-13868 has a CVSS v3.1 base score of 6.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-13868?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-13868, 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-13868

Explore →

Is Your Infrastructure Affected by CVE-2026-13868?

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

Start Free Scan →Browse All CVEs