How severe is CVE-2025-5419?

CVE-2025-5419 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2025-5419?

Affected package information for CVE-2025-5419 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2025-5419?

No fixed version has been published for CVE-2025-5419 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2025-5419 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2025-5419, including . All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2025-5419?

CVE-2025-5419 has an EPSS (Exploit Prediction Scoring System) score of 3.8%, placing it in the 88th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

Is CVE-2025-5419 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2025-5419 (Google Chromium V8 Out-of-Bounds Read and Write Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2025-06-05. CISA required all US federal civilian agencies to remediate this vulnerability by 2025-06-26. The required action was: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2025-5419?

CVE-2025-5419 is classified as Out-of-bounds Read (CWE-125), Out-of-bounds Write (CWE-787). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-5419 published, and has it been updated?

CVE-2025-5419 was published on June 3, 2025 and was last updated on April 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2025-06-05 — agencies required to remediate by 2025-06-26

CVE-2025-5419

HIGH

Published

Jun 3, 2025

Updated

Apr 16, 2026

Affected

0 pkgs

Patched

None yet

Exploits

2 known

EPSS Exploitation Probability

via FIRST.org ↗

3.8%probability of exploitation in next 30 days

Lower Risk88th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

Out of bounds read and write in V8 in Google Chrome prior to 137.0.7151.68 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

mistymntncop/CVE-2025-5419

⭐ 94🍴 18May 2026

bjrjk/CVE-2025-5419

An uninitialized read vulnerability by incorrect Turboshaft Store-Store

⭐ 30🍴 4Feb 2026

Frequently Asked Questions

Out of bounds read and write in V8 in Google Chrome prior to 137.0.7151.68 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

O3 Security · Impact-Aware SCA

Is CVE-2025-5419 in your stack?

O3 detects CVE-2025-5419 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works