LiveActive security incident?Get immediate response
CVE Record

CVE-2025-5419: Out of bounds read and write in V8 in Google Chrome prior to 137.0.7151.68 allowed a remote attacker to pot...

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)

HighCVSS 8.8Known exploitedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This is a high-severity Chrome V8 memory-safety flaw. A user who visits a malicious page could expose the browser to heap corruption with potential compromise impact. CISA lists it as known exploited, so this is not theoretical and should be prioritized across managed Chrome fleets.

Executive priority

Treat as urgent browser patching. Known exploitation plus high impact makes delayed update exposure a practical business risk, especially for users handling sensitive systems or data.

Technical view

CVE-2025-5419 is an out-of-bounds read and write in Chrome V8 before 137.0.7151.68. The CVSS 3.1 score is 8.8 with network attack vector, low complexity, no privileges required, user interaction required, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is likely wherever Google Chrome desktop versions before 137.0.7151.68 remain in use. The provided bundle does not establish affected server software, mobile scope, or other Chromium-based products beyond the cited vendor sources.

Exploitation context

CISA KEV status supports known exploitation in the wild. The provided sources do not describe campaigns, targets, exploit maturity, or technical exploit details. The realistic scenario is a user reaching crafted HTML content in an unpatched browser.

Researcher notes

The source bundle confirms memory corruption in V8 and KEV status, but does not provide exploit internals or detailed affected-platform boundaries. Validation should focus on version evidence, update telemetry, and vendor advisories rather than proof-of-concept reproduction.

Mitigation direction

  • Update Chrome to 137.0.7151.68 or later.
  • Confirm browser restarts completed after update deployment.
  • Check Google and Microsoft guidance for affected channel details.
  • Prioritize managed endpoints with internet-facing browsing activity.
  • Accelerate patching for privileged users and high-risk business units.

Validation and detection

  • Inventory Chrome versions across managed endpoints.
  • Flag Chrome versions earlier than 137.0.7151.68.
  • Verify CISA KEV tracking includes CVE-2025-5419.
  • Confirm update compliance after browser restart.
  • Review EDR telemetry for browser exploitation alerts.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-125: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-787: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-5419 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
Yes
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2025-5419Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleChrome137.0.7151.68Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-125 · source CWE mapping

Out-of-bounds Read

Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

CWE-787 · source CWE mapping

Out-of-bounds Write

Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.