VulnerabilityPublished 14 Nov 2025

CVE-2025-9479: Google Chrome · Out-of-bounds Read

Affects Google ChromeSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium : upgrade to 133.0.6943.141 when convenient.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score

4.3Medium

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 133.0.6943.141

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

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

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: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 14 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 133.0.6943.141.

Affected software

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

AI-suggested

European organizations should prioritize updating all Google Chrome installations to version 133.0.6943.141 or later to remediate CVE-2025-9479. Beyond patching, organizations should implement browser security best practices such as enabling sandboxing features, restricting JavaScript execution on untrusted sites via Content Security Policy (CSP), and using browser isolation technologies where feasible. Security awareness training should emphasize the risks of clicking unknown links or visiting suspicious websites to reduce the likelihood of user interaction-based exploitation. Network-level protections like web filtering and intrusion prevention systems can help block access to known malicious domains hosting crafted HTML pages. Monitoring browser crash logs and unusual behavior can provide early detection of attempted exploitation. For high-risk environments, consider deploying endpoint detection and response (EDR) solutions that can detect anomalous heap corruption or memory-related attacks. Regular vulnerability scanning and asset inventory to identify outdated Chrome versions will support timely patch management. Finally, coordinate with IT teams to ensure rapid deployment of browser updates across all user devices, including remote and mobile endpoints.

Description

Out of bounds read in V8 in Google Chrome prior to 133.0.6943.141 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Medium)

Impact

For European organizations, this vulnerability poses a moderate risk primarily to availability and operational stability. Organizations relying heavily on Google Chrome for web access, especially those with employees frequently browsing external or untrusted sites, could experience browser crashes or disruptions if targeted by malicious actors exploiting this flaw. Although no direct confidentiality or integrity impact is indicated, heap corruption can sometimes be a stepping stone for more advanced exploits, potentially leading to privilege escalation or code execution in a worst-case scenario. Critical sectors such as finance, government, and healthcare in Europe, which depend on stable and secure browsing environments, may face operational interruptions or targeted phishing campaigns embedding malicious HTML content. The lack of known exploits reduces immediate risk, but the widespread use of Chrome in Europe means the attack surface is large. Additionally, the requirement for user interaction means social engineering or drive-by download attacks could be vectors. The medium severity suggests that while urgent patching is recommended, the threat is not currently critical but should be addressed promptly to avoid escalation.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 21 Nov 2025, 04:54 UTC

Technical details

References

Community reviews

Related threats