CVE-2026-13903

HIGHPre-NVD 8.88.8
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 0

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

Insufficient policy enforcement in Bluetooth in Google Chrome prior to 150.0.7871.47 allowed a remote attacker to perform privilege escalation via a crafted HTML page. (Chromium security severity: Medium)

CVSS v3
8.8
EG Score
8.8(high)
EPSS
27.0%
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-13903(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 12× in last 7d / 83× 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-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:24 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 14:30 UTCEPSS rescore
  5. 2026-07-19 02:28 UTCEPSS rescore
  6. 2026-07-18 10:04 UTCEPSS rescore
  7. 2026-07-17 01:25 UTCVendor advisory
  8. 2026-07-17 01:25 UTCGHSA enrichment
  9. 2026-07-16 17:02 UTCEPSS rescore
  10. 2026-07-16 14:27 UTCGHSA enrichment
  11. 2026-07-16 03:30 UTCVendor advisory
  12. 2026-07-16 03:30 UTCGHSA enrichment
  13. 2026-07-15 16:57 UTCEPSS rescore
  14. 2026-07-15 16:33 UTCVendor advisory
  15. 2026-07-15 16:33 UTCGHSA enrichment
  16. 2026-07-15 05:35 UTCVendor advisory
  17. 2026-07-15 05:35 UTCGHSA enrichment
  18. 2026-07-15 02:00 UTCEPSS rescore
  19. 2026-07-14 18:30 UTCVendor advisory
  20. 2026-07-14 18:30 UTCGHSA enrichment
  21. 2026-07-14 07:33 UTCVendor advisory
  22. 2026-07-14 07:33 UTCGHSA enrichment
  23. 2026-07-13 22:30 UTCEPSS rescore
  24. 2026-07-13 20:34 UTCGHSA enrichment
  25. 2026-07-13 09:37 UTCGHSA enrichment
Show 58 more
  1. 2026-07-13 06:12 UTCEPSS rescore
  2. 2026-07-12 22:40 UTCVendor advisory
  3. 2026-07-12 22:40 UTCGHSA enrichment
  4. 2026-07-12 11:43 UTCVendor advisory
  5. 2026-07-12 11:43 UTCGHSA enrichment
  6. 2026-07-12 05:46 UTCEPSS rescore
  7. 2026-07-12 00:45 UTCVendor advisory
  8. 2026-07-12 00:45 UTCGHSA enrichment
  9. 2026-07-11 13:48 UTCVendor advisory
  10. 2026-07-11 13:48 UTCGHSA enrichment
  11. 2026-07-11 08:27 UTCEPSS rescore
  12. 2026-07-11 02:51 UTCVendor advisory
  13. 2026-07-11 02:51 UTCGHSA enrichment
  14. 2026-07-10 15:54 UTCVendor advisory
  15. 2026-07-10 15:54 UTCGHSA enrichment
  16. 2026-07-10 04:57 UTCVendor advisory
  17. 2026-07-10 04:56 UTCGHSA enrichment
  18. 2026-07-09 19:10 UTCEPSS rescore
  19. 2026-07-09 17:55 UTCVendor advisory
  20. 2026-07-09 17:55 UTCGHSA enrichment
  21. 2026-07-09 06:57 UTCVendor advisory
  22. 2026-07-09 06:57 UTCGHSA enrichment
  23. 2026-07-08 20:00 UTCVendor advisory
  24. 2026-07-08 20:00 UTCGHSA enrichment
  25. 2026-07-08 15:15 UTCEPSS rescore
  26. 2026-07-08 15:15 UTCEPSS rescore
  27. 2026-07-08 09:00 UTCVendor advisory
  28. 2026-07-08 09:00 UTCGHSA enrichment
  29. 2026-07-07 22:03 UTCVendor advisory
  30. 2026-07-07 22:03 UTCGHSA enrichment
  31. 2026-07-07 13:46 UTCEPSS rescore
  32. 2026-07-07 11:06 UTCVendor advisory
  33. 2026-07-07 11:05 UTCGHSA enrichment
  34. 2026-07-07 00:08 UTCVendor advisory
  35. 2026-07-07 00:08 UTCGHSA enrichment
  36. 2026-07-06 13:11 UTCVendor advisory
  37. 2026-07-06 13:11 UTCGHSA enrichment
  38. 2026-07-06 02:23 UTCEPSS rescore
  39. 2026-07-06 02:09 UTCVendor advisory
  40. 2026-07-06 02:09 UTCGHSA enrichment
  41. 2026-07-05 15:11 UTCVendor advisory
  42. 2026-07-05 15:11 UTCGHSA enrichment
  43. 2026-07-05 04:14 UTCVendor advisory
  44. 2026-07-05 04:14 UTCGHSA enrichment
  45. 2026-07-05 02:30 UTCEPSS rescore
  46. 2026-07-05 02:30 UTCEPSS rescore
  47. 2026-07-04 17:16 UTCVendor advisory
  48. 2026-07-04 17:16 UTCGHSA enrichment
  49. 2026-07-04 06:31 UTCEPSS rescore
  50. 2026-07-04 06:18 UTCVendor advisory
  51. 2026-07-04 06:18 UTCGHSA enrichment
  52. 2026-07-03 19:20 UTCEG score recompute 8.80
  53. 2026-07-03 19:20 UTCGHSA enrichment
  54. 2026-07-01 17:06 UTCNVD updateCVSS v3 → 8.8 · severity → HIGH
  55. 2026-07-01 15:06 UTCEPSS rescore
  56. 2026-07-01 15:06 UTCEPSS rescore
  57. 2026-06-30 23:33 UTCEG score recompute
  58. 2026-06-30 23:23 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-13903?
CVE-2026-13903 is a high vulnerability published on June 30, 2026. Insufficient policy enforcement in Bluetooth in Google Chrome prior to 150.0.7871.47 allowed a remote attacker to perform privilege escalation via a crafted HTML page. (Chromium security severity: Medium)
When was CVE-2026-13903 disclosed?
CVE-2026-13903 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-13903 actively exploited?
CVE-2026-13903 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 27.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-13903?
CVE-2026-13903 has a CVSS v3.1 base score of 8.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-13903?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-13903, 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-13903

Explore →

Is Your Infrastructure Affected by CVE-2026-13903?

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