CVE-2026-13905

MEDIUMPre-NVD 4.24.2—
EchelonGraph scoreHIGH confidence

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

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

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

Race in Chrome for iOS in Google Chrome on iOS prior to 150.0.7871.47 allowed a local attacker to obtain potentially sensitive information from process memory via physical access to the device. (Chromium security severity: Medium)

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

Published

June 30, 2026

Last Modified

July 1, 2026

Advisory Details (2)

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

Chromium

https://issues.chromium.org/issues/504192688
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-13905(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 5× in last 7d / 43× 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-24 14:17 UTCEPSS rescore
  2. 2026-07-23 03:05 UTCEG score recompute
  3. 2026-07-22 14:08 UTCEPSS rescore
  4. 2026-07-20 17:08 UTCEPSS rescore
  5. 2026-07-19 14:30 UTCEPSS rescore
  6. 2026-07-17 02:06 UTCVendor advisory
  7. 2026-07-17 02:06 UTCGHSA enrichment
  8. 2026-07-16 17:02 UTCEPSS rescore
  9. 2026-07-16 03:48 UTCVendor advisory
  10. 2026-07-16 03:48 UTCGHSA enrichment
  11. 2026-07-15 16:57 UTCEPSS rescore
  12. 2026-07-15 05:35 UTCVendor advisory
  13. 2026-07-15 05:35 UTCGHSA enrichment
  14. 2026-07-14 07:11 UTCVendor advisory
  15. 2026-07-14 07:11 UTCGHSA enrichment
  16. 2026-07-13 22:30 UTCEPSS rescore
  17. 2026-07-13 09:00 UTCGHSA enrichment
  18. 2026-07-13 06:12 UTCEPSS rescore
  19. 2026-07-12 10:49 UTCVendor advisory
  20. 2026-07-12 10:49 UTCGHSA enrichment
  21. 2026-07-12 05:46 UTCEPSS rescore
  22. 2026-07-11 12:38 UTCGHSA enrichment
  23. 2026-07-11 08:27 UTCEPSS rescore
  24. 2026-07-10 14:27 UTCGHSA enrichment
  25. 2026-07-09 19:10 UTCEPSS rescore
Show 18 more
  1. 2026-07-09 16:17 UTCGHSA enrichment
  2. 2026-07-08 18:02 UTCGHSA enrichment
  3. 2026-07-07 19:49 UTCGHSA enrichment
  4. 2026-07-07 13:46 UTCEPSS rescore
  5. 2026-07-06 21:37 UTCGHSA enrichment
  6. 2026-07-06 16:27 UTCEPSS rescore
  7. 2026-07-05 23:24 UTCGHSA enrichment
  8. 2026-07-05 02:30 UTCEPSS rescore
  9. 2026-07-05 02:30 UTCEPSS rescore
  10. 2026-07-05 01:12 UTCGHSA enrichment
  11. 2026-07-04 06:31 UTCEPSS rescore
  12. 2026-07-04 02:55 UTCEG score recompute▲ 4.20
  13. 2026-07-04 02:55 UTCGHSA enrichment
  14. 2026-07-01 15:06 UTCEPSS rescore
  15. 2026-07-01 15:06 UTCEPSS rescore
  16. 2026-07-01 03:20 UTCNVD updateCVSS v3 → 4.2 · severity → MEDIUM
  17. 2026-06-30 23:33 UTCEG score recompute
  18. 2026-06-30 23:23 UTCNVD updatefirst tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-13905?
CVE-2026-13905 is a medium vulnerability published on June 30, 2026. Race in Chrome for iOS in Google Chrome on iOS prior to 150.0.7871.47 allowed a local attacker to obtain potentially sensitive information from process memory via physical access to the device. (Chromium security severity: Medium)
When was CVE-2026-13905 disclosed?
CVE-2026-13905 was first published in the National Vulnerability Database on June 30, 2026, with the most recent update on July 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-13905 actively exploited?
CVE-2026-13905 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-13905?
CVE-2026-13905 has a CVSS v3.1 base score of 4.2 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-13905?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-13905, 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-13905

Explore →

Is Your Infrastructure Affected by CVE-2026-13905?

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

Start Free Scan →Browse All CVEs