Dangerous-file protection bypass via insufficient validation
Published Jan 20, 2026 · Updated Jan 20, 2026
Input validation failure in Google Chrome Downloads before 144.0.7559.59 on Windows allows remote attackers to bypass dangerous-file protections. The Downloads component inadequately validates a malicious file before applying dangerous-file handling; Google has not disclosed the specific validation error. Exploitation requires user interaction with attacker-supplied content and permits the file to evade the browser's intended protection.
Summary
What happened
Input validation failure in Google Chrome Downloads before 144.0.7559.59 on Windows allows remote attackers to bypass dangerous-file protections. The Downloads component inadequately validates a malicious file before applying dangerous-file handling; Google has not disclosed the specific validation error. Exploitation requires user interaction with attacker-supplied content and permits the file to evade the browser's intended protection.
The record
- CVE
- CVE-2026-0903
- Published
- Jan 20, 2026
- Updated
- Jan 20, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-20, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 20, 2026CVE publishedPublication date reported by the CVE source.
- Jan 20, 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=144.0.7559.59 <144.0.7559.59
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