VulnerabilityPublished 6 Nov 2025

CVE-2025-11219: Google Chrome · Use After Free

Affects Google ChromeSource CVE Database V5

Not known to be exploited · CVSS 3.1 Low : upgrade to 141.0.7390.54 when convenient.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

3.1Low

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

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

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

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
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: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
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: 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 6 Nov 2025
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 141.0.7390.54.

Affected software

Product	Affected	Fixed in
Google Chrome	Affected =141.0.7390.54 <141.0.7390.54	Fixed in 141.0.7390.54

AI-suggested

European organizations should implement the following specific mitigations: 1) Ensure all Chrome browsers are updated to version 141.0.7390.54 or later promptly, using centralized patch management tools where possible. 2) Enforce policies that restrict or monitor the execution of untrusted or unknown web content, including the use of browser security extensions or content filtering solutions. 3) Educate users about the risks of visiting suspicious websites and the importance of avoiding clicking on unknown links, especially in emails or messaging platforms. 4) Employ network-level protections such as web proxies or secure web gateways that can detect and block access to malicious sites hosting crafted HTML pages. 5) Monitor browser telemetry and logs for unusual behavior that might indicate exploitation attempts. 6) Integrate vulnerability scanning and browser version inventory into regular security audits to ensure compliance. These steps go beyond generic advice by focusing on operational controls and user awareness tailored to this specific vulnerability.

Description

Use after free in V8 in Google Chrome prior to 141.0.7390.54 allowed a remote attacker to potentially perform out of bounds memory access via a crafted HTML page. (Chromium security severity: Low)

Impact

For European organizations, the primary impact of CVE-2025-11219 is limited to potential confidentiality breaches through out-of-bounds memory reads in affected Chrome browsers. Since the vulnerability does not allow code execution or denial of service, the risk to system integrity and availability is minimal. However, in environments where sensitive information is accessed via Chrome, such as financial institutions, healthcare providers, or government agencies, even limited data leakage could have compliance and privacy implications under regulations like GDPR. The requirement for user interaction reduces the likelihood of widespread automated exploitation, but targeted phishing or watering hole attacks could leverage this vulnerability to gather sensitive data. Organizations with large numbers of users on outdated Chrome versions may face increased exposure. The absence of known exploits in the wild suggests a low immediate threat, but the vulnerability should not be ignored as part of a layered defense strategy.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Nov 2025, 02:28 UTC

Technical details

References

Community reviews

Related threats