Origin-policy bypass via Variations input validation
Published Aug 25, 2026 · Updated Aug 27, 2026
Improper input validation in Google Chrome Variations before 152.0.7977.65 allows remote attackers to bypass web origin policy. The public record does not identify the malformed field or the validation operation that Variations performs incorrectly on untrusted network input. Exploitation requires Chrome to process crafted network traffic, and the disclosed consequence is limited to a web-origin-policy bypass.
Summary
What happened
Improper input validation in Google Chrome Variations before 152.0.7977.65 allows remote attackers to bypass web origin policy. The public record does not identify the malformed field or the validation operation that Variations performs incorrectly on untrusted network input. Exploitation requires Chrome to process crafted network traffic, and the disclosed consequence is limited to a web-origin-policy bypass.
The record
- CVE
- CVE-2026-79192
- Published
- Aug 25, 2026
- Updated
- Aug 27, 2026
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-20
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 25, 2026CVE publishedPublication date reported by the CVE source.
- Aug 27, 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=152.0.7977.65 <152.0.7977.65
What conditions does exploitation require?
What is affected?
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