UI spoofing via improper CSS implementation
Published Jun 30, 2026 · Updated Jun 30, 2026
Inappropriate CSS implementation in Google Chrome before 150.0.7871.47 allows remote attackers to spoof browser UI via crafted HTML. Google identifies the CSS component but has not disclosed the specific code path or incorrect handling of the crafted page. Exploitation requires a user to load attacker-controlled HTML, enabling misleading interface content without reported data disclosure or service interruption.
Summary
What happened
Inappropriate CSS implementation in Google Chrome before 150.0.7871.47 allows remote attackers to spoof browser UI via crafted HTML. Google identifies the CSS component but has not disclosed the specific code path or incorrect handling of the crafted page. Exploitation requires a user to load attacker-controlled HTML, enabling misleading interface content without reported data disclosure or service interruption.
The record
- CVE
- CVE-2026-13837
- Published
- Jun 30, 2026
- Updated
- Jun 30, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-451, T1204
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 30, 2026CVE publishedPublication date reported by the CVE source.
- Jun 30, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=150.0.7871.47 <150.0.7871.47
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo