What is the severity of CVE-2025-4051?

CVE-2025-4051 is classified as a high severity vulnerability affecting Chromium-based browsers.

How do I fix CVE-2025-4051?

To fix CVE-2025-4051, update your Chrome browser to version 136.0.7103.59 or higher, or update Microsoft Edge to the latest version.

Which versions are affected by CVE-2025-4051?

CVE-2025-4051 affects Google Chrome versions prior to 136.0.7103.59 and Microsoft Edge versions prior to 136.0.3240.50.

Who is responsible for addressing CVE-2025-4051?

CVE-2025-4051 was addressed by Google for Chrome and has also been mitigated in Microsoft Edge since it is based on Chromium.

Is CVE-2025-4051 being exploited in the wild?

At this time, there is no public indication that CVE-2025-4051 is being actively exploited in the wild.

Vulnerability/
CVE-2025-4051

medium

16/3/2025

1/5/2025

CVE-2025-4051: Insufficient data validation in DevTools

First published: Sun Mar 16 2025(Updated: )

<p>This CVE was assigned by Chrome. Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see <a href="https://chromereleases.googleblog.com/202%C2%A05">Google Chrome Releases</a> for more information.</p>

Credit: Daniel Fröjdendahl

Affected Software	Affected Version	How to fix
Google Chrome	<136.0.7103.59	136.0.7103.59
Microsoft Edge Beta	<136.0.3240.50
Microsoft Edge		fix available externally

Never miss a vulnerability like this again

Reference Links

Parent vulnerabilities

(Appears in the following advisories)

5659444046422897663

Peer vulnerabilities

(Found alongside the following vulnerabilities)

Frequently Asked Questions

What is the severity of CVE-2025-4051?
CVE-2025-4051 is classified as a high severity vulnerability affecting Chromium-based browsers.
How do I fix CVE-2025-4051?
To fix CVE-2025-4051, update your Chrome browser to version 136.0.7103.59 or higher, or update Microsoft Edge to the latest version.
Which versions are affected by CVE-2025-4051?
CVE-2025-4051 affects Google Chrome versions prior to 136.0.7103.59 and Microsoft Edge versions prior to 136.0.3240.50.
Who is responsible for addressing CVE-2025-4051?
CVE-2025-4051 was addressed by Google for Chrome and has also been mitigated in Microsoft Edge since it is based on Chromium.
Is CVE-2025-4051 being exploited in the wild?
At this time, there is no public indication that CVE-2025-4051 is being actively exploited in the wild.

agent/title
agent/severity
agent/first-publish-date
agent/type
agent/author
collector/chrome-releases
agent/software-canonical-lookup
agent/references
agent/source
agent/last-modified-date
agent/softwarecombine
agent/tags
agent/description
collector/msrc-cve
source/Microsoft
collector/msrc
agent/event
vendor/google
canonical/google chrome
vendor/microsoft
canonical/microsoft edge beta
canonical/microsoft edge

Company

Resources

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.

Frequently Asked Questions

What is the severity of CVE-2025-4051?
CVE-2025-4051 is classified as a high severity vulnerability affecting Chromium-based browsers.
How do I fix CVE-2025-4051?
To fix CVE-2025-4051, update your Chrome browser to version 136.0.7103.59 or higher, or update Microsoft Edge to the latest version.
Which versions are affected by CVE-2025-4051?
CVE-2025-4051 affects Google Chrome versions prior to 136.0.7103.59 and Microsoft Edge versions prior to 136.0.3240.50.
Who is responsible for addressing CVE-2025-4051?
CVE-2025-4051 was addressed by Google for Chrome and has also been mitigated in Microsoft Edge since it is based on Chromium.
Is CVE-2025-4051 being exploited in the wild?
At this time, there is no public indication that CVE-2025-4051 is being actively exploited in the wild.