VulnerabilityPublished 11 Feb 2026Updated 26 Feb 2026

CVE-2026-2314: Google Chrome · Heap Buffer Overflow

Affects Google ChromeSource CVE Database V5

Not known to be exploited · CVSS 8.8 High : upgrade to 145.0.7632.45 soon.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

8.8High

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

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

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

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

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: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Feb 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 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 145.0.7632.45.

Affected software

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

AI-suggested

To mitigate CVE-2026-2314, organizations should immediately update all instances of Google Chrome to version 145.0.7632.45 or later, where the vulnerability is patched. Beyond patching, implement strict web content filtering to block access to untrusted or suspicious websites that could host malicious HTML content. Employ browser sandboxing and exploit mitigation technologies such as Control Flow Guard (CFG) and Address Space Layout Randomization (ASLR) to reduce the impact of potential exploitation. Educate users about the risks of clicking unknown links or visiting untrusted sites to reduce the likelihood of triggering the vulnerability. Monitor network and endpoint logs for unusual browser behavior or crashes that could indicate exploitation attempts. Consider deploying endpoint detection and response (EDR) solutions capable of detecting anomalous process behavior related to browser exploits. For high-security environments, restrict browser extensions and plugins to minimize attack surface. Finally, maintain an up-to-date inventory of browser versions across the organization to ensure timely patch deployment.

Description

Heap buffer overflow in Codecs in Google Chrome prior to 145.0.7632.45 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

Impact

The impact of CVE-2026-2314 is substantial for organizations worldwide. Successful exploitation can lead to arbitrary code execution within the browser context, enabling attackers to bypass security controls, steal sensitive data, install malware, or pivot to internal networks. The vulnerability compromises confidentiality by potentially exposing user data, integrity by allowing unauthorized code execution, and availability by causing browser crashes or denial of service. Given Chrome's dominant market share in enterprise and consumer environments, a large number of systems are exposed. Attackers could leverage this vulnerability in targeted attacks or widespread campaigns, especially against high-value targets such as government agencies, financial institutions, and critical infrastructure operators. The requirement for user interaction limits automated exploitation but does not eliminate risk, as phishing and drive-by download attacks remain effective vectors. The absence of known exploits in the wild currently reduces immediate risk but does not preclude future weaponization.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Feb 2026, 08:47 UTC

Technical details

References

Community reviews

Related threats