VulnerabilityPublished 20 Jan 2026

CVE-2026-0903: Google Chrome · Insufficient Validation of Untrusted Input

Affects Google ChromeSource CVE Database V5

Not known to be exploited · CVSS 5.4 Medium : upgrade to 144.0.7559.59 when convenient.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score

5.4Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 144.0.7559.59

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 20 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Google Chrome to 144.0.7559.59.

Affected software

Product	Affected	Fixed in
GoogleChrome	Affected >=144.0.7559.59 <144.0.7559.59	Fixed in 144.0.7559.59

AI-suggested

European organizations should immediately update all Windows-based Chrome installations to version 144.0.7559.59 or later to remediate the vulnerability. Beyond patching, organizations should enforce strict download policies, such as restricting downloads of executable or script files from untrusted sources and leveraging browser security settings to block or warn about dangerous file types. Endpoint protection solutions should be configured to scan downloaded files in real-time and quarantine suspicious content. User awareness training should emphasize the risks of downloading files from unknown or untrusted websites. Network-level controls, such as web proxies and URL filtering, can help block access to malicious sites hosting exploit files. Incident response teams should monitor for unusual download activity or execution of unexpected files on endpoints. Additionally, organizations could consider application whitelisting to prevent unauthorized execution of downloaded files. Regular audits of browser versions and patch compliance are critical to ensure ongoing protection against this and similar vulnerabilities.

Description

Inappropriate implementation in Downloads in Google Chrome on Windows prior to 144.0.7559.59 allowed a remote attacker to bypass dangerous file type protections via a malicious file. (Chromium security severity: Medium)

Impact

For European organizations, this vulnerability poses a risk primarily to Windows-based endpoints running vulnerable versions of Chrome. Successful exploitation could lead to the delivery and potential execution of malicious files, which may result in malware infections, data breaches, or further lateral movement within corporate networks. Confidentiality could be compromised if sensitive data is exfiltrated via malware installed through this vector. Integrity and availability could also be affected if destructive payloads are deployed. Sectors such as finance, government, healthcare, and critical infrastructure in Europe are particularly at risk due to their reliance on Chrome and the sensitivity of their data. The vulnerability could be exploited in targeted attacks or broader phishing campaigns leveraging malicious downloads. Although no exploits are currently known, the widespread use of Chrome and Windows in Europe means the attack surface is large. Organizations with strict download policies and endpoint protection may reduce impact, but unpatched systems remain vulnerable. The threat is heightened in countries with high technology adoption and significant digital infrastructure, where attackers may seek to gain footholds for espionage or disruption.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 20 Jan 2026, 04:37 UTC

Technical details

References

Community reviews

Related threats