CVE-2024-2400

CVE-2024-2400 is a high-severity vulnerability in Google Chrome with a CVSS 3.x base score of 8.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-416.

Key facts

Description

Use after free in Performance Manager in Google Chrome prior to 122.0.6261.128 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

Frequently asked questions

What is CVE-2024-2400?
Use after free in Performance Manager in Google Chrome prior to 122.0.6261.128 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
How severe is CVE-2024-2400?
CVE-2024-2400 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2024-2400 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (49th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2024-2400?
CVE-2024-2400 primarily affects Google Chrome. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2024-2400?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2024-2400 have an EU (EUVD) identifier?
Yes. CVE-2024-2400 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-27352.
When was CVE-2024-2400 published?
CVE-2024-2400 was published on 2024-03-13 and last updated on 2026-06-17.

References

Affected products (3)

More vulnerabilities in Google Chrome

All CVEs affecting Google Chrome →

Other CWE-416 (Use After Free) vulnerabilities

Browse all CWE-416 (Use After Free) vulnerabilities →