CVE-2026-7913
HIGHCVSS 7.8/10EPSS 0.11%
Last modified
CVE-2026-7913 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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). EPSS estimates a 0.11% chance of exploitation in the next 30 days.
Description
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)
Metrics
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Chrome | < 148.0.7778.96 |
References
- https://issues.chromium.org/issues/497936728Issue Tracking, Permissions Required
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-7913?
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)
How severe is CVE-2026-7913?
CVE-2026-7913 has a CVSS score of 7.8/10 (HIGH severity). The EPSS model estimates a 0.11% probability of exploitation in the next 30 days.
How do I fix CVE-2026-7913?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-7907Use after free in DOM in Google Chrome prior to 148.0.7778.9…8.8
- CVE-2026-7908Use after free in Fullscreen in Google Chrome prior to 148.0…9.6
- CVE-2026-7909Inappropriate implementation in ServiceWorker in Google Chro…3.1
- CVE-2026-7910Use after free in Views in Google Chrome prior to 148.0.7778…9.6
- CVE-2026-7911Use after free in Aura in Google Chrome on Windows prior to …8.3
- CVE-2026-7912Integer overflow in GPU in Google Chrome on Android prior to…4.2
- CVE-2026-7914Type Confusion in Accessibility in Google Chrome on Windows …8.3
- CVE-2026-7915Insufficient data validation in DevTools in Google Chrome on…4.3
- CVE-2026-7916Insufficient data validation in InterestGroups in Google Chr…8.3
- CVE-2026-7917Use after free in Fullscreen in Google Chrome on Windows pri…8.3
- CVE-2026-7918Use after free in GPU in Google Chrome prior to 148.0.7778.9…8.3
- CVE-2026-7919Use after free in Aura in Google Chrome prior to 148.0.7778.…8.3
Are you affected by CVE-2026-7913?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST