CVE-2026-1504VulnerabilityPublished 27 Jan 2026

CVE-2026-1504: Google Chrome · Inappropriate implementation

Affects Google ChromeSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium : upgrade to 144.0.7559.110 when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

6.5Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: None
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within 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 27 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 2026-10-26.

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 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.110.

Affected software

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

AI-suggested

European organizations should immediately update all Chrome installations to version 144.0.7559.110 or later to remediate the vulnerability. Beyond patching, organizations should implement strict web content filtering to block access to malicious or untrusted websites that could host crafted HTML pages exploiting this flaw. Employing browser isolation technologies can help contain potential attacks by isolating web content execution. Security teams should monitor network traffic for unusual data exfiltration patterns indicative of exploitation attempts. User awareness training should emphasize caution when visiting unknown or suspicious websites. Organizations should also review and tighten Content Security Policy (CSP) settings to restrict cross-origin data sharing. Regular vulnerability scanning and penetration testing focusing on browser-based threats can help identify residual risks. Finally, maintaining an inventory of browser versions and enforcing update policies ensures timely remediation of similar future vulnerabilities.

Description

Inappropriate implementation in Background Fetch API in Google Chrome prior to 144.0.7559.110 allowed a remote attacker to leak cross-origin data via a crafted HTML page. (Chromium security severity: High)

Impact

For European organizations, this vulnerability poses a substantial risk to data confidentiality. Attackers exploiting this flaw can access cross-origin data, potentially exposing sensitive customer information, intellectual property, or internal communications. This is particularly critical for sectors such as finance, healthcare, and government, where data privacy regulations like GDPR impose strict requirements on data protection. The ease of exploitation without authentication or user interaction increases the threat level, as attackers can deploy malicious web pages or ads to target users broadly. Data leakage incidents could lead to regulatory penalties, reputational damage, and financial losses. Additionally, organizations with remote or hybrid workforces relying heavily on Chrome browsers are more exposed. The vulnerability could also be leveraged as a stepping stone for further attacks, such as phishing or credential theft, by harvesting sensitive data from other origins.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Jan 2026, 21:20 UTC

Technical details

References

Community reviews

Related threats