VulnerabilityPublished 27 May 2025Updated 3 Nov 2025

CVE-2025-5283: Google Chrome · Use After Free

Affects Google ChromeSource CVE Database V5

Not known to be exploited · CVSS 5.4 Medium : upgrade to 137.0.7151.55 when convenient.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

5.4Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: Low
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on 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 27 May 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 the Debian debian/chrome package to 137.0.7151.55.

Affected software

Product	Affected	Fixed in
Debiandebian/chrome`pkg:deb/debian/chrome`Other threats	Affected <137.0.7151.55	Fixed in 137.0.7151.55

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

AI-suggested

Immediately update Google Chrome to version 137.0.7151.55 or later where the vulnerability is patched.
Employ enterprise browser management tools to enforce automatic updates and prevent use of outdated versions.
Use browser security features such as site isolation, sandboxing, and strict content security policies to limit the impact of malicious web content.
Educate users about the risks of visiting untrusted or suspicious websites to reduce the likelihood of triggering the vulnerability.
Deploy network-level protections such as web filtering and intrusion prevention systems to block access to known malicious domains.
Monitor browser crash logs and unusual behavior that may indicate exploitation attempts.
For high-risk environments, consider restricting or isolating browser usage to minimize exposure.
Maintain up-to-date endpoint detection and response (EDR) solutions to detect exploitation attempts or post-exploitation activity.

Description

Use after free in libvpx in Google Chrome prior to 137.0.7151.55 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 confidentiality and integrity of data accessed or processed via Google Chrome. Since Chrome is widely used across enterprises, government agencies, and critical infrastructure in Europe, exploitation could lead to unauthorized information disclosure or manipulation of browser data. Sectors with high exposure to web-based threats, such as finance, healthcare, and public administration, are particularly at risk. The requirement for user interaction (visiting a malicious webpage) means phishing or drive-by download attacks could be vectors. While no known exploits exist currently, the presence of a use-after-free flaw in a widely used browser component means that attackers could develop exploits, increasing risk over time. The vulnerability does not affect availability directly but could be leveraged as part of multi-stage attacks. Organizations relying on Chrome for sensitive operations should consider this a medium priority but act promptly to mitigate risk.

CWE-416Use After Free (opens in a new tab)
Variant weaknessLikelihood of exploit: HighCWE Top 25 (2025): #7
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.
Architecture and Design · Language Selection
Choose a language that provides automatic memory management.
Implementation · Attack Surface Reduction
When freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy.
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)
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, 01:42 UTC

WeaknessesCWE-416

Technical details

References

Community reviews

Related threats