VulnSocial

CVE-2025-9132General(apple / chrome)

LOWCVSS 8.8 · HIGH

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD description

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

apple CVEsBack to dashboard
1.0/ 10 priority

Sources & remediation

Vendor / third-party advisories
Other references
Weakness type (CWE)
CWE-787

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

NONE

Momentum

STABLE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • chrome
  • linux_kernel
  • macos
  • windows

Threat summary

  • 2 mentions across 2 observed days
  • Momentum state: stable

What's happening

  • Technical details provided in 1 signal
  • General: 2 classified signals
  • Peaked 1d ago at 1 mentions (2026-03-16); latest day: 1
  • 2 total mentions across 2 days

Affected systems

Vendors
applegooglelinuxmicrosoft
Products
chromelinux_kernelmacoswindows

1 version affected across 4 products

Deep dive

Activity timeline2 mentions / 2d
00111Mentions · 2026-03-16: 1Mentions · 2026-06-06: 1Technical Details · 2026-06-06: 103-1606-06
Signal classification1 categories
General
2100.0%
Full discourse2 posts
  • _SiCk@encrypted_past
    General

    More to the point. CVE-2025-9132 - OOB write CVE-2025-12036 - inappropriate implementation CVE-2025-13224 - type confusion (CVSS 8.8) CVE-2025-10585 - type confusion CVE-2025-13223 - type confusion (CVSS 8.8) CVE-2026-3910 - (CVSS 8.8, CISA KEV) Fuck v8.

    Post summary

    The post enumerates several CVE identifiers with brief vulnerability descriptions and CVSS scores, offering no additional context on exploits, mitigations, or active attacks.

    0222142.6K
    2.7K followersView on X
  • suleif@proteinpowder00
    General

    My progress on CVE-2025-9132: - Somewhat understood the root cause - Found precisely where the code execution ends up after the faulty jump - Stuck on how to manipulate where this jump will end up going, currently from some tinkering I can send it a few bytes before where it went

    Post summary

    The text details a developer’s personal progress on understanding CVE‑2025‑9132 but provides no evidence of a PoC, exploit, active exploitation, patch, or technical specifics.

    20050624
    38 followersView on X
CPE platform detail4 entries

4 of 4 entries

PartVendorProductVersionTarget SWTarget HW
OSapplemacos---
Appgooglechrome---
OSlinuxlinux_kernel---
OSmicrosoftwindows---

Explore more

Back to dashboardapple CVEsgoogle CVEslinux CVEschrome vulnerabilities