CVE-2026-7913

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-06. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.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 DevTools in Google Chrome on Android prior to 148.0.7778.96 allowed a local attacker to perform privilege escalation via a malicious file. (Chromium security severity: High)

CVSS v3
7.8
EG Score
7.8(medium)
EPSS
1.6%
KEV
Not listed

Published

May 6, 2026

Last Modified

May 6, 2026

Advisory Details (2)

Auto-updated May 20, 2026
No patch confirmed yet.
generic

Chromium

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

Chrome Releases: Stable Channel Update for Desktop

https://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop.html

Vendor Advisories for CVE-2026-7913(1)

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 10× in last 7d / 48× 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 138 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-7913?
CVE-2026-7913 is a high vulnerability published on May 6, 2026. Insufficient policy enforcement in DevTools in Google Chrome on Android prior to 148.0.7778.96 allowed a local attacker to perform privilege escalation via a malicious file. (Chromium security severity: High)
When was CVE-2026-7913 disclosed?
CVE-2026-7913 was first published in the National Vulnerability Database on May 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-7913 actively exploited?
CVE-2026-7913 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-7913?
CVE-2026-7913 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-7913?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-7913, 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-7913

Explore →

Is Your Infrastructure Affected by CVE-2026-7913?

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

Start Free Scan →Browse All CVEs