CVE-2026-8018

Insufficient policy enforcement in DevTools in Google Chrome prior to 148.0.7778.96 allowed a remote attacker to potentially perform a sandbox escape via malicious network traffic. (Chromium security severity: Low)

Published: 2026-05-06 Last update: 2026-05-08 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-8018 is rated Low Risk (37.7/100): CVSS High severity, with low exploitation likelihood (EPSS 0.05%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-8018

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-22 0.15% 0.05% -0.10%
2 2026-05-12 0.07% 0.15% +0.08%
3 2026-05-07 — 0.07% —

Full EPSS history (3 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-8018

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.1 3.1 HIGH
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.2 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2026-8018

GitHub Security Advisory for CVE-2026-8018

GHSA-j96j-v243-5h5m · Severity: high — Insufficient policy enforcement in DevTools in Google Chrome prior to 148.0.7778.96 allowed a...

OS Trackers for CVE-2026-8018

vendor priority summary link
debian end-of-life CVE-2026-8018 end-of-life priority: Debian including 1 source packages (chromium), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 1. https://security-tracker.debian.org/tracker/CVE-2026-8018
ubuntu medium CVE-2026-8018 medium priority: Ubuntu including 1 source packages (chromium-browser), 5 status rows across 5 suites (jammy, noble, questing, resolute, upstream): not-affected 4, released 1. https://ubuntu.com/security/CVE-2026-8018

Affected software / configurations for CVE-2026-8018

Vendor Product Version Raw CPE
google chrome < 148.0.7778.96 cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*

References for CVE-2026-8018

cvelogic Threat Intelligence