/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Broadcom fixes three VMware zero-days exploited in the wild found by Microsoft; attackers with admin or root access can chain the flaws to escape a VM's sandbox

Broadcom warned customers today about three VMware zero-days, tagged as exploited in attacks and reported by the Microsoft Threat Intelligence Center.

BleepingComputer Sergiu Gatlan

Discussion

  • @campuscodi.risky.biz Catalin Cimpanu on bluesky
    Broadcom released security patches to patch an actively exploited zero-day in its VMware ESXi products.  —  Broadcom credited Microsoft's MSTIC security team with spotting and reporting the attacks.  —  CVE-2025-22224: support.broadcom.com/web/ecx/ supp...
  • @cyb3rops Florian Roth on x
    There could be multiple reasons why VMware didn't publish details: 1. They might believe the exploitation isn't widespread enough to justify detailed disclosure. 2. They might worry that publishing specifics (log entries, vulnerable components, or temporary files) could enable
  • @vmwaresrc @vmwaresrc on x
    Today we released a new Critical Severity VMware Security Advisory. Check out https://support.broadcom.com/ .... #VMware #VMwareByBroadcom
  • @cyb3rops Florian Roth on x
    VMware reports active exploitation of new ESXi zero-days - but only gives us a patch matrix 🙄 - How is it so hard to understand that if a zero-day is actively exploited, we need indicators and forensic guidance to hunt? - Otherwise, we're just blindly patching already [image]