CVE-2024-4059VulnerabilityPublished 1 May 2024Updated 4 Nov 2025

CVE-2024-4059: Google Chrome · Out of bounds read

Affects Google ChromeSource CVE Database V5

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

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

6.5Medium

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

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

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 1 May 2024
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-25.

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

Affected software

Product	Affected	Fixed in
Googlegoogle/chrome`pkg:rpm/google/chrome`Other threats	Affected <124.0.6367.78	Fixed in 124.0.6367.78

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediately update all Google Chrome installations to version 124.0.6367.78 or later to apply the official patch addressing CVE-2024-4059. 2. Implement enterprise-wide browser update policies to ensure timely deployment of security patches. 3. Employ web filtering and content security policies to block access to known malicious or untrusted websites that could host crafted HTML pages exploiting this vulnerability. 4. Educate users about the risks of clicking on suspicious links or visiting untrusted websites to reduce the likelihood of successful exploitation via social engineering. 5. Monitor network traffic and browser logs for unusual or suspicious activity indicative of exploitation attempts, such as unexpected cross-site data requests or anomalous memory access patterns. 6. Consider deploying browser isolation or sandboxing technologies to limit the impact of potential browser-based attacks. 7. Coordinate with IT security teams to audit and verify that all endpoints are running updated browser versions and that legacy or unmanaged devices are identified and remediated.

Description

Out of bounds read in V8 API in Google Chrome prior to 124.0.6367.78 allowed a remote attacker to leak cross-site data via a crafted HTML page. (Chromium security severity: High)

Impact

For European organizations, the primary impact of CVE-2024-4059 is the potential leakage of sensitive cross-site data, which can compromise user privacy and confidentiality of corporate information accessed via web browsers. This could lead to exposure of session tokens, personal data, or other confidential information stored or accessible through browser contexts. While the vulnerability does not allow code execution or system compromise, the data leakage could facilitate further targeted attacks such as phishing, identity theft, or corporate espionage. Organizations in sectors handling sensitive data—such as finance, healthcare, and government—are particularly at risk. The requirement for user interaction means social engineering or phishing campaigns could be used to exploit this vulnerability. Given the widespread use of Google Chrome across Europe, the scope of affected systems is broad, increasing the potential scale of impact. Additionally, regulatory frameworks like GDPR impose strict requirements on data protection, so data leakage incidents could lead to legal and reputational consequences for European entities.

CWE-125Out-of-bounds Read (opens in a new tab)
Base weaknessCWE Top 25 (2025): #8
The product reads data past the end, or before the beginning, of the intended buffer.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design · Language Selection
Use a language that provides appropriate memory abstractions.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Overread Buffers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Nov 2025, 22:15 UTC

WeaknessesCWE-125

Technical details

References

Community reviews

Related threats