Cross-origin script injection via undisclosed CSS flaw
Published Jul 30, 2026 · Updated Jul 30, 2026
Cross-site scripting in CSS in Google Chrome before 151.0.7922.72 allows remote attackers to inject scripts or HTML via a crafted page. Google identifies the CSS component but keeps the linked bug details restricted, so the specific erroneous CSS operation is undisclosed. A user must open the crafted page; successful exploitation runs attacker-controlled content across an origin boundary, affecting confidentiality and integrity without reported availability impact.
Summary
What happened
Cross-site scripting in CSS in Google Chrome before 151.0.7922.72 allows remote attackers to inject scripts or HTML via a crafted page. Google identifies the CSS component but keeps the linked bug details restricted, so the specific erroneous CSS operation is undisclosed. A user must open the crafted page; successful exploitation runs attacker-controlled content across an origin boundary, affecting confidentiality and integrity without reported availability impact.
The record
- CVE
- CVE-2026-17845
- Published
- Jul 30, 2026
- Updated
- Jul 30, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-79, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 30, 2026CVE publishedPublication date reported by the CVE source.
- Jul 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=151.0.7922.72 <151.0.7922.72
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