CVE-2025-10585: Type confusion in V8 in Google Chrome prior to 140.0.7339.185 allowed a remote attacker to potentially expl...
Type confusion in V8 in Google Chrome prior to 140.0.7339.185 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
Security readout for executives and security teams
Plain-English summary
CVE-2025-10585 is a high-impact Chrome V8 flaw that could let a malicious web page corrupt browser memory. Because CISA lists it in KEV, treat it as exploited in the wild. Business risk is highest where browsers lag behind managed updates or users can browse untrusted sites.
Executive priority
Treat as an urgent browser patching item because exploitation is confirmed by KEV and impact could include confidentiality, integrity, and availability compromise on user endpoints.
Technical view
The issue is CWE-843 type confusion in V8 in Google Chrome before 140.0.7339.185. The CVSS 3.1 score is 8.8 with network attack vector, low complexity, no privileges, and required user interaction. The described outcome is potential heap corruption via crafted HTML.
Likely exposure
Endpoints running Google Chrome prior to 140.0.7339.185 are the clearly supported exposure. The Siemens advisory may indicate downstream product relevance, but product-specific impact is not included in the provided bundle.
Exploitation context
CISA KEV status supports known exploitation. The provided sources do not include exploit mechanics, campaign details, or proof-of-concept availability. Exploitation requires user interaction, such as reaching crafted HTML content.
Researcher notes
The public bundle supports impact, affected Chrome version boundary, CVSS, CWE, and KEV status. It does not provide technical root-cause details from the Chromium issue, exploit indicators, or complete downstream product impact.
Mitigation direction
Update Google Chrome to 140.0.7339.185 or later.
Prioritize browser updates on internet-facing user workstations.
Check CISA KEV due dates and internal remediation SLAs.
Review Siemens advisory for any affected Siemens-managed environments.
Consult vendor guidance for downstream Chromium-based products.
Validation and detection
Inventory Chrome versions across managed endpoints.
Confirm installed Chrome is 140.0.7339.185 or later.
Identify users or systems exempted from browser auto-update policies.
Review EDR or browser telemetry for suspicious renderer crashes.
Check asset exposure against Siemens advisory if relevant.
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-843: 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.
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.
Exploitation: activeAutomatable: noTechnical Impact: total
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-843 · source CWE mapping
Access of Resource Using Incompatible Type ('Type Confusion')
Access of Resource Using Incompatible Type ('Type Confusion') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.