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
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 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
Vendor severity
HIGHper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: High)
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/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
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
chromium100.0.4896.127-1 ... 99.0.4844.84-1~deb11u1 (500 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
chromium113.0.5672.126-1 ... 147.0.7727.55-1~deb13u1 (348 versions)148.0.7778.96-1~deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
chromium138.0.7204.183-1 ... 148.0.7778.96-1~deb12u1 (114 versions)148.0.7778.96-1~deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
chromium138.0.7204.183-1 ... 148.0.7778.96-1~deb13u1 (115 versions)148.0.7778.96-1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 81× 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 205 total refreshes for this CVE.

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

See which npm, PyPI, Go, and Maven packages are affected by 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