VulnSocial

CVE-2026-11045Patch(apple / chrome)

MEDIUMCVSS 6.5 · MEDIUM

Exploitation ongoing with high activity in latest observed window (1 mentions)

Immediate actions

  • Patch apple chrome systems immediately
  • Assume compromise if assets are exposed

Recommended action window: Immediate (within 24h)

NVD description

Insufficient validation of untrusted input in GPU in Google Chrome prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to obtain potentially sensitive information from process memory via a crafted HTML page. (Chromium security severity: Medium)

apple CVEsBack to dashboard
5.0/ 10 priority

Sources & remediation

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

Priority

MEDIUM

Exploitation

ACTIVE

PoC

NONE

Patch

AVAILABLE

Momentum

NONE

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

  • Active exploitation appears in 1 classified signals
  • Patch or workaround signal is available
  • 1 mentions across 1 observed day

What's happening

  • Active exploitation reported across 1 signal
  • Patch or workaround mentioned in 1 signal
  • 1 total mentions across 1 day

Affected systems

Vendors
applegooglelinuxmicrosoft
Products
chromelinux_kernelmacoswindows

1 version affected across 4 products

Deep dive

Activity timeline1 mentions / 1d
00111Mentions · 2026-06-09: 1Active Exploitation · 2026-06-09: 1Patch / Workaround · 2026-06-09: 106-09
Signal classification1 categories
Patch
1100.0%
Referenced assets1 URL
Full discourse1 post
  • WindowsForum@windowsforum
    Patch

    🪟 Chrome “renderer memory disclosure” isn’t a one-click takeover—it’s just the “now that you’re in” stage. After the first exploit, this bug hands over secrets via a crafted page. Why patch fast? Because chaining works. #Windows #Microsoft #Chrome #CVE https://windowsforum.com/threads/cve-2026-11045-chrome-gpu-bug-patch-to-149-to-stop-renderer-memory-disclosure.424543/?utm_source=x&utm_medium=social&utm_campaign=news_node84 https://t.co/qVHhZKf5dx

    Post summary

    The post highlights a known Chrome renderer memory disclosure (CVE‑2026‑11045) that has been exploited and is being patched promptly to prevent chaining of attacks.

    0000026
    1.2K 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