Sensitive information leak via HTTP/2 authorization omission
Published Aug 25, 2026 · Updated Aug 25, 2026
Missing authorization in HTTP/2 in Google Chrome before 152.0.7977.65 allows remote attackers to leak sensitive information via network traffic. Google identifies the affected locus only as HTTP/2 and has not published the omitted authorization check or the protected data exposed by it. The attack is unauthenticated and network-based, but high attack complexity limits reachability; successful exploitation discloses data without integrity or availability impact.
Summary
What happened
Missing authorization in HTTP/2 in Google Chrome before 152.0.7977.65 allows remote attackers to leak sensitive information via network traffic. Google identifies the affected locus only as HTTP/2 and has not published the omitted authorization check or the protected data exposed by it. The attack is unauthenticated and network-based, but high attack complexity limits reachability; successful exploitation discloses data without integrity or availability impact.
The record
- CVE
- CVE-2026-79208
- Published
- Aug 25, 2026
- Updated
- Aug 25, 2026
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-862
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 25, 2026CVE publishedPublication date reported by the CVE source.
- Aug 25, 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?
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