CVE-2026-8579

Insufficient validation of untrusted input in Skia in Google Chrome prior to 148.0.7778.168 allowed a remote attacker who had compromised the renderer process to perform an out of bounds memory write via a crafted print file. (Chromium security severity: Medium)

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

CVE-2026-8579 is rated Low Risk (17.5/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.05%). Low composite risk—no urgent action required; patch on your normal maintenance cycle and revisit priority if CVSS or EPSS increases.

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-8579

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-15 — 0.05% —

Full EPSS history (1 record total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
3.1 3.1 LOW
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N 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:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 1.6 1.4 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2026-8579

GitHub Security Advisory for CVE-2026-8579

GHSA-9h3r-77j2-mgh9 · Severity: low — Insufficient validation of untrusted input in Skia in Google Chrome prior to 148.0.7778.168...

OS Trackers for CVE-2026-8579

vendor priority summary link
debian end-of-life CVE-2026-8579 end-of-life priority: Debian including 2 source packages (chromium, libskia), 7 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 6, open 1. https://security-tracker.debian.org/tracker/CVE-2026-8579
redhat medium — https://access.redhat.com/security/cve/CVE-2026-8579
ubuntu medium CVE-2026-8579 medium priority: Ubuntu including 2 source packages (chromium-browser, libskia), 10 status rows across 5 suites (jammy, noble, questing, resolute, upstream): not-affected 4, DNE 3, released 2, needs-triage 1. https://ubuntu.com/security/CVE-2026-8579

Affected software / configurations for CVE-2026-8579

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

References for CVE-2026-8579

cvelogic Threat Intelligence