[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fo3Gy7bnm7YI2TmcsvCs8X9c6p59hikUL_4cOdW_rF9Y":3},{"lesson":4},{"id":5,"slug":6,"article_id":7,"title":8,"body":9,"prevention":10,"framework_refs":11,"framework_notes":17,"status":23,"created_at":24,"published_at":25,"article":26,"tags":30,"podcasts":43,"controls":50},"b7db7b6c-6904-47fe-9e33-7e38a78101c5","vmware-vcenter-zero-day-exploited-for-months-before-patch-1795180881720","a59a02c0-a605-4f04-949e-1169f80a8b0e","VMware vCenter Zero-Day Exploited for Months Before Patch","A sophisticated China-nexus threat actor exploited a critical VMware vCenter vulnerability (CVSS 9.8) for over two months before a patch was available, using custom tooling to forge authentication tokens and bypass MFA entirely. Because the flaw allowed unauthenticated attackers to gain administrator sessions, any exposed vCenter instance was at risk without compensating controls in place. This incident highlights the danger of assuming perimeter-facing virtualization infrastructure is safe simply because no patch exists yet — the absence of a vendor fix does not mean the absence of attacker knowledge. Organizations must have strategies for operating securely during the zero-day window, including network-level restrictions and enhanced monitoring of privileged session activity.","**Immediate actions:**\n- Restrict vCenter management interfaces to trusted internal IP ranges or VPN-only access to reduce exposure during zero-day windows\n- Deploy integrity monitoring and anomaly detection on authentication logs for vCenter and other hypervisor management planes\n- Apply any vendor-recommended workarounds or mitigations immediately upon public disclosure, even before a formal patch is released\n\n**Long-term improvements:**\n- Implement network segmentation so that virtualization management planes are isolated from general corporate and internet-facing networks\n- Maintain a continuously updated inventory of all internet-exposed management interfaces and assign them elevated vulnerability monitoring priority\n- Establish a formal zero-day response playbook that defines compensating controls, stakeholder escalation, and monitoring uplift for critical unpatched vulnerabilities\n\n**Detection measures:**\n- Enable detailed authentication and session logging on vCenter and alert on unusual admin session creation, especially from unexpected source IPs\n- Deploy behavioral analytics capable of detecting token forgery or anomalous privileged API calls indicative of tools like BONESAW and SAWSNAKE\n- Subscribe to threat intelligence feeds that track nation-state tooling so indicators of compromise can be operationalized before vendor advisories are published",[12,13,14,15,16],"CIS Control 7: Continuous Vulnerability Management","CIS Control 12: Network Infrastructure Management","NIST SP 800-53 SI-2: Flaw Remediation","NIST CSF 2.0 DE.CM-01: Continuous Monitoring","NIS2 Article 21(2)(e)",{"NIS2 Article 21(2)(e)":18,"NIST SP 800-53 SI-2: Flaw Remediation":19,"NIST CSF 2.0 DE.CM-01: Continuous Monitoring":20,"CIS Control 12: Network Infrastructure Management":21,"CIS Control 7: Continuous Vulnerability Management":22},"This point requires security in acquisition, development, and maintenance including vulnerability handling and disclosure, directly covering the obligation to have processes for managing unpatched critical vulnerabilities in infrastructure like vCenter.","SI-2 requires organizations to identify, report, and correct information system flaws and to apply compensating controls when timely remediation is not possible, which is precisely the gap exploited during the unpatched window.","This category requires continuous monitoring of networks and systems for anomalous activity, which could have detected the forged authentication tokens and anomalous administrator sessions created by BONESAW and SAWSNAKE.","This control requires restricting access to network and management infrastructure, which would have limited attacker reach to the vCenter management plane even during the zero-day period.","This control requires organizations to continuously assess and remediate vulnerabilities, including applying compensating controls when patches are unavailable — directly addressing the two-month exploitation window before the vCenter patch was released.","published","2026-11-20T13:21:21.735465+00:00","2026-11-20T13:21:21.679+00:00",{"id":7,"url":27,"slug":28,"title":29},"https:\u002F\u002Fwww.helpnetsecurity.com\u002F2026\u002F11\u002F20\u002Fvmware-vcenter-zero-day-cve-2026-123890-exploited\u002F","vmware-vcenter-zero-day-exploited-for-months-before-patch-cve-2026-123890-bbc89a","VMware vCenter zero-day exploited for months before patch (CVE-2026-123890)",[31,37],{"id":32,"name":33,"slug":34,"description":35,"color":36},"05757c8d-6b93-4194-b35d-7359e7d33b0e","Vulnerability Management","vulnerability-management","Missing scans, no risk prioritization","#fb923c",{"id":38,"name":39,"slug":40,"description":41,"color":42},"af7fce9e-1ce8-4156-93bc-09dcfbfdf29d","Patch Management","patch-management","Unpatched vulnerabilities, delayed updates","#ef4444",[44],{"id":45,"date":46,"edition":47,"title":48,"audio_url":49},"0bb91999-d8d6-422a-ac21-58fc90d5815f","2026-11-20","afternoon","ThreatNoir Afternoon Brief — November 20","https:\u002F\u002Fcdn.threatnoir.com\u002Fpodcasts\u002F2026-11-20\u002Fthreatnoir-afternoon-brief-2026-11-20.mp3",[51,54,57],{"slug":34,"name":52,"problem":53},"Vulnerability scanning and prioritisation","You know which systems are vulnerable, and which ones to fix first.",{"slug":40,"name":55,"problem":56},"Automated patch management","Known holes get closed in days, not months.",{"slug":58,"name":59,"problem":60},"endpoint-detection-response","Endpoint detection and response (EDR and XDR)","Malware and hands-on-keyboard attackers on laptops and servers get spotted and stopped."]