CVE-2026-7913

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

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, GitHub Security Advisory, NVD CVSS v3
7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

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 (value × EchelonGraph’s weight)
Severity78% × 45%
The EG Score, 7.8 of 10.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
below the 1st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 6, 2026

Last Modified

May 6, 2026

Advisory Details (2)

Auto-updated May 20, 2026
Patch available.
Web page

Chromium

https://issues.chromium.org/issues/497936728
Web page

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 rangeFix by version rangeDependents
chromium100.0.4896.127-1 ... 99.0.4844.84-1~deb11u1 (500 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
chromium113.0.5672.126-1 ... 147.0.7727.55-1~deb13u1 (348 versions)
  • every version up to 148.0.7778.96-1~deb12u1: fixed in 148.0.7778.96-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
chromium138.0.7204.183-1 ... 148.0.7778.96-1~deb12u1 (114 versions)
  • every version up to 148.0.7778.96-1~deb13u1: fixed in 148.0.7778.96-1~deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
chromium138.0.7204.183-1 ... 148.0.7778.96-1~deb13u1 (115 versions)
  • every version up to 148.0.7778.96-1: fixed in 148.0.7778.96-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 26× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 95 of 240 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 145 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  2. 2026-10-12 15:36 UTCEG score recompute
  3. 2026-10-11 19:22 UTCEG score recompute
  4. 2026-10-11 16:38 UTCEG score recompute
  5. 2026-10-11 13:56 UTCEG score recompute
  6. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  7. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  8. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  9. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  10. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  11. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  12. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  13. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  14. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  15. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  16. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  17. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  18. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  19. 2026-09-26 00:28 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  20. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  21. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  22. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  23. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  24. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  25. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.1% · 1st percentile
Show 70 more
  1. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  2. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  3. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  4. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  5. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  6. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  7. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  8. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  9. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  10. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  11. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  12. 2026-08-26 14:47 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  13. 2026-08-24 14:18 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  14. 2026-08-23 19:46 UTCEG score recompute
  15. 2026-08-23 19:46 UTCVendor advisory
  16. 2026-08-23 19:46 UTCGHSA enrichmentGHSA-p432-h2pw-987x · GitHub severity HIGH · GitHub CVSS 7.8
  17. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  18. 2026-08-20 22:56 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  19. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  20. 2026-08-18 13:49 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  21. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  22. 2026-08-17 12:52 UTCEG score recompute
  23. 2026-08-17 12:52 UTCVendor advisory
  24. 2026-08-17 12:52 UTCGHSA enrichmentGHSA-p432-h2pw-987x · GitHub severity HIGH · GitHub CVSS 7.8
  25. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  26. 2026-08-16 04:50 UTCEG score recompute
  27. 2026-08-16 04:50 UTCVendor advisory
  28. 2026-08-16 04:50 UTCGHSA enrichmentGHSA-p432-h2pw-987x · GitHub severity HIGH · GitHub CVSS 7.8
  29. 2026-08-16 02:15 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  30. 2026-08-15 01:31 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  31. 2026-08-14 15:01 UTCVendor advisory
  32. 2026-08-14 15:01 UTCGHSA enrichmentGHSA-p432-h2pw-987x · GitHub severity HIGH · GitHub CVSS 7.8
  33. 2026-08-14 03:23 UTCEG score recompute
  34. 2026-08-14 03:23 UTCVendor advisory
  35. 2026-08-14 03:23 UTCGHSA enrichmentGHSA-p432-h2pw-987x · GitHub severity HIGH · GitHub CVSS 7.8
  36. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  37. 2026-08-13 04:36 UTCGHSA enrichmentGHSA-p432-h2pw-987x · GitHub severity HIGH · GitHub CVSS 7.8
  38. 2026-08-12 16:58 UTCEG score recompute
  39. 2026-08-12 16:58 UTCVendor advisory
  40. 2026-08-12 16:58 UTCGHSA enrichmentGHSA-p432-h2pw-987x · GitHub severity HIGH · GitHub CVSS 7.8
  41. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  42. 2026-08-11 15:59 UTCVendor advisory
  43. 2026-08-11 15:59 UTCGHSA enrichmentGHSA-p432-h2pw-987x · GitHub severity HIGH · GitHub CVSS 7.8
  44. 2026-08-11 01:29 UTCEG score recompute
  45. 2026-08-11 01:29 UTCVendor advisory
  46. 2026-08-11 01:29 UTCGHSA enrichmentGHSA-p432-h2pw-987x · GitHub severity HIGH · GitHub CVSS 7.8
  47. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  48. 2026-08-10 13:39 UTCVendor advisory
  49. 2026-08-10 13:39 UTCGHSA enrichmentGHSA-p432-h2pw-987x · GitHub severity HIGH · GitHub CVSS 7.8
  50. 2026-08-10 01:46 UTCGHSA enrichmentGHSA-p432-h2pw-987x · GitHub severity HIGH · GitHub CVSS 7.8
  51. 2026-08-09 14:10 UTCEG score recompute
  52. 2026-08-09 14:10 UTCVendor advisory
  53. 2026-08-09 14:10 UTCGHSA enrichmentGHSA-p432-h2pw-987x · GitHub severity HIGH · GitHub CVSS 7.8
  54. 2026-08-09 13:47 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  55. 2026-08-09 02:33 UTCEG score recompute
  56. 2026-08-09 02:33 UTCVendor advisory
  57. 2026-08-09 02:33 UTCGHSA enrichmentGHSA-p432-h2pw-987x · GitHub severity HIGH · GitHub CVSS 7.8
  58. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  59. 2026-08-08 10:07 UTCVendor advisory
  60. 2026-08-08 10:07 UTCGHSA enrichmentGHSA-p432-h2pw-987x · GitHub severity HIGH · GitHub CVSS 7.8
  61. 2026-08-07 22:30 UTCVendor advisory
  62. 2026-08-07 22:30 UTCGHSA enrichmentGHSA-p432-h2pw-987x · GitHub severity HIGH · GitHub CVSS 7.8
  63. 2026-08-07 10:53 UTCVendor advisory
  64. 2026-08-07 10:53 UTCGHSA enrichmentGHSA-p432-h2pw-987x · GitHub severity HIGH · GitHub CVSS 7.8
  65. 2026-08-06 21:48 UTCEG score recompute
  66. 2026-08-06 21:48 UTCVendor advisory
  67. 2026-08-06 21:48 UTCGHSA enrichmentGHSA-p432-h2pw-987x · GitHub severity HIGH · GitHub CVSS 7.8
  68. 2026-08-06 13:47 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  69. 2026-08-06 10:10 UTCVendor advisory
  70. 2026-08-06 10:10 UTCGHSA enrichmentGHSA-p432-h2pw-987x · GitHub severity HIGH · GitHub CVSS 7.8

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-7913?
CVE-2026-7913 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-7913 published?
The CVE record for CVE-2026-7913 was published on May 6, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of May 6, 2026; the record at its source may have been updated since.
Is CVE-2026-7913 actively exploited?
CVE-2026-7913 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-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?
A fix for CVE-2026-7913 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-7913 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs