CVE-2025-6558 · Published 15 Jul 2025
Google Chromium
On CISA's KEV list 7 days after disclosure; 3 public exploits.
Google Chromium contains an improper input validation vulnerability in ANGLE and GPU. This vulnerability could allow a remote attacker to potentially perform a sandbox escape via a crafted HTML page. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.
CISA required action (federal due date 12 Aug 2025): Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Signals
- KEV, exploited in the wild
- yes, added 22 Jul 2025, due 12 Aug 2025
- EPSS, 30-day forecast
- 11%, 96th percentile (as of 18 Nov 2026)
- CVSS, NVD
- not stated
- Internet exposure
- not stated
KEV is an observation, EPSS a forecast; KEV outranks it. No score published by NVD.
Timeline 15 Jul 2025 to today
- Disclosed
- KEV+7 d
- First PoCsame day
7 days from disclosure to the KEV listing
Indicators none tied yet
No threat feed has tied an indicator to this CVE yet. Checked every six hours.
On the wire 0 dispatches
No dispatch on our wire has named this CVE yet.
Public exploit code 3 known · links only
GitHub PoCs 3Metasploit 0Exploit-DB 0
GitHub PoCs, by trust then stars3
- DevBuiHieu/CVE-2025-6558-Proof-Of-ConceptTrust ok 1007 stars
created 24 Jul 2025
- gmh5225/CVE-2025-6558-exp1 stars
Trust ok 85 · 1 flag
- no source (no_source)
created 22 Jul 2025
- dexteon/cve-2025-6558-pocTrust ok 1000 stars
Research notes for cve-2025-6558-poc
created 12 Nov 2026
Fake proof-of-concept repositories have been used to deliver malware to the researchers who run them. The trust verdict is our engine's heuristic over the repository (account age, what it ships, how its stars arrived); it is a reason to read the code first, not a finding about its author.
References
Watch this one?
KEV additions reach Telegram and the KEV-only RSS as they land.