CVE-2025-14765: High Use after free in WebGPU.

Published Sep 30, 2025
·
Updated

Chromium: CVE-2025-14765 Out of bounds read and write in V8

Other sources

This CVE was assigned by Chrome. Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information.

Microsoft

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

MITRE

Credit

Anonymous

Affected Software

6 affected componentsFixes available
All of the following
Google Chrome<143.0.7499.146
Any of the following
Apple macOS
Linux Linux kernel
Microsoft Windows
Microsoft Edge (Chromium-based)
Microsoft Edge<143.0.3650.96

Event History

Sep 30, 2025
CVE Published
12:00 AM
Data Sourced
12:00 AM
Weakness
Dec 16, 2025
CVE Published
via MITRE·10:54 PM
Data Sourced
via MITRE·10:54 PM
DescriptionWeakness
Data Sourced
via NVD·11:15 PM
DescriptionSeverityWeaknessAffected Software
Dec 18, 2025
Data Sourced
via Microsoft·08:43 PM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·08:43 PM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-14765?

CVE-2025-14765 has a high severity level due to its potential for heap corruption exploitation.

2

How do I fix CVE-2025-14765?

To fix CVE-2025-14765, upgrade Google Chrome to version 143.0.7499.147 or later.

3

What is the impact of CVE-2025-14765?

CVE-2025-14765 can allow remote attackers to exploit vulnerability via a crafted HTML page.

4

Which version of Google Chrome is affected by CVE-2025-14765?

Google Chrome versions prior to 143.0.7499.147 are affected by CVE-2025-14765.

5

Is there a workaround for CVE-2025-14765 until I can update?

There are no official workarounds for CVE-2025-14765; updating Chrome is the recommended solution.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203