---
title: Wall off vCenter's management ports with a network firewall, not just the appliance's own VAMI firewall | ctxsec
url: https://ctxsec.com/items/tip-wall-off-vcenter-management-ports-2012-389-5480-not-just-vami-firewall
description: "CVE-2026-123890 only needs network access to vCenter, and ARMORY CASTLE reached it from an ordinary internal Linux appliance. Mandiant notes the built-in VCSA firewall managed in VAMI cannot allow a host to one port without trusting it for all ports, can be switched off by anyone who reaches VAMI on TCP 5480, and does not log denied connections. Patch first, then put vCenter behind a network firewall that only lets admin workstations and named backup or monitoring servers reach the specific ports they need, and alert on anything else touching TCP 2012, 389/636 and 5480."
status: "guidance drawn from the GTIG/Mandiant ARMORY CASTLE report and Broadcom VMSA-2026-0009"
published: 2026-11-19
---

> CVE-2026-123890 only needs network access to vCenter, and ARMORY CASTLE reached it from an ordinary internal Linux appliance. Mandiant notes the built-in VCSA firewall managed in VAMI cannot allow a host to one port without trusting it for all ports, can be switched off by anyone who reaches VAMI on TCP 5480, and does not log denied connections. Patch first, then put vCenter behind a network firewall that only lets admin workstations and named backup or monitoring servers reach the specific ports they need, and alert on anything else touching TCP 2012, 389/636 and 5480.

[← Tips & Guides](/tips) · [markdown](/items/tip-wall-off-vcenter-management-ports-2012-389-5480-not-just-vami-firewall.md)

guidance drawn from the GTIG/Mandiant ARMORY CASTLE report and Broadcom VMSA-2026-0009

2026-11-19 3:37 PM ET

### Wall off vCenter's management ports with a network firewall, not just the appliance's own VAMI firewall

- Patch to the VMSA-2026-0009 fixed versions; Broadcom lists no workaround.
- Allow-list by source and port at a firewall in front of vCenter, using privileged access workstations for admin access.
- Log and alert on connections to TCP 2012 and 5480 from anything but admin workstations, and on SSH being enabled on vCenter.
- Keep EDR or at least process and auth logging on the Linux appliances that sit next to vCenter; in this case the attacker staged tools on appliances that had none.

Sources: [Google Threat Intelligence Group / Mandiant: ARMORY CASTLE Exploits vSphere (Nov 19, 2026)](https://cloud.google.com/blog/topics/threat-intelligence/armory-castle-exploits-vsphere) · [Broadcom VMSA-2026-0009: VMware vCenter, Tools, and SDDC Manager updates address multiple vulnerabilities (Nov 19, 2026)](https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39495)
