CVE-2026-2313
Analyzed Analyzed - Analysis Complete
Use-After-Free in Chrome CSS Causes High-Severity Heap Corruption

Publication date: 2026-02-11

Last updated on: 2026-02-13

Assigner: Chrome

Description
Use after free in CSS 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)
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-11
Last Modified
2026-02-13
Generated
2026-05-07
AI Q&A
2026-02-11
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
google chrome to 145.0.7632.45 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-416 The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability is a use-after-free issue in the CSS component of Google Chrome versions prior to 145.0.7632.45. It allows a remote attacker to potentially cause heap corruption by crafting a malicious HTML page that exploits this flaw.


How can this vulnerability impact me? :

Exploitation of this vulnerability can lead to severe impacts including unauthorized code execution, data corruption, or crashing of the browser. Since it involves heap corruption, an attacker could potentially take control of the affected system or cause denial of service.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

I don't know


What immediate steps should I take to mitigate this vulnerability?

I don't know


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart