What is CVE-2026-5858?
Heap buffer overflow in WebML in Google Chrome prior to 147.0.7727.55 allowed a remote attacker to execute arbitrary code via a crafted HTML page.
The record classifies CVE-2026-5858 under weakness class CWE-122. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs a user to take an action first, and has high impact on confidentiality, integrity, availability. 4 affected-product entries are recorded, across 4 vendors, listed below. The identifier was first published 203 days ago.
Severity and exploitation probability
- CVSS v3.1 base score
- 8.8 — HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H - EPSS (FIRST)
- 0.5% probability of exploitation in the next 30 days, higher than 45.6% of all scored CVEs
- CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 8.2/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- Published
- 2026-04-08, last modified 2026-04-13
Is CVE-2026-5858 being exploited?
Weaponised exploit code for CVE-2026-5858 is publicly available. 1 public proof-of-concept repository is tracked for this identifier. It currently carries a trending score of 24 in the Threadlinqs vulnerability feed.
- trickest/cve (trickest)
Affected products and versions
How to fix CVE-2026-5858
The record marks a vendor fix as available for CVE-2026-5858. Vendor advisory: https://chromereleases.googleblog.com/2026/04/stable-channel-update-for-desktop.html. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.
Threat activity tracking CVE-2026-5858
1 tracked threat in the Threadlinqs corpus references CVE-2026-5858, either in the campaign’s CVE list or as an indicator on the campaign record.
Sources
Enriched from CVE.org, FIRST EPSS, GitHub Security Advisories, public proof-of-concept repositories. Last verified by Threadlinqs on .