# Critical Patch Response Kit: vCenter and NGINX **Purpose.** This kit helps a small business find out whether it runs VMware vCenter or NGINX, patch in the right order, check for signs of a prior visit, and hold an IT provider to written answers. It was built around two flaws disclosed in mid-November 2026: VMware vCenter CVE-2026-123890 (CVSS 9.8, reportedly exploited since September) and five NGINX flaws led by CVE-2026-123007 (an unauthenticated HTTP/2 bug present since 2015). It is useful printed, on its own, with a pen. Nothing here replaces the vendor's own advisory. Read that too. ## Checklist - [ ] List every VMware vCenter and ESXi host you own or that a provider runs for you. - [ ] List every NGINX web server or reverse proxy, including ones inside appliances, hosting plans and container images. - [ ] Ask your IT provider for their asset list in writing and compare it with yours. - [ ] Record the product version for each item (for NGINX run `nginx -v`; for vCenter check the appliance management page). - [ ] Note whether each system is reachable from the internet (yes, no, or unknown). - [ ] Snapshot or back up each system before patching; confirm you can restore. - [ ] Patch vCenter first, then NGINX. Schedule a maintenance window and tell staff. - [ ] Confirm the running version after the patch, not just the installed package. - [ ] Restrict the vCenter management interface to a VPN or a short list of admin addresses. - [ ] Review vCenter and ESXi logs, accounts, scheduled tasks and outbound connections back to September. - [ ] If anything looks wrong, take the system off the internet and call your provider or an incident responder. - [ ] Check the CISA Known Exploited Vulnerabilities catalog weekly and note due dates for products you run. - [ ] Write down who owns patching for each system and the maximum days allowed for a critical fix. ## Worksheet 1: System inventory Copy one row per system. | System | Owner | Product and version | Internet-exposed (yes/no/unknown) | Patch date | |---|---|---|---|---| | | | | | | | | | | | | | | | | | | | | | | | | ## Worksheet 2: Patch order and maintenance window | Step | Detail | Done | |---|---|---| | 1 | Patch vCenter (exploited before fix) | [ ] | | 2 | Patch NGINX hosts | [ ] | | 3 | Window date and time: __________ | [ ] | | 4 | Staff notified | [ ] | | 5 | Backup or snapshot confirmed restorable | [ ] | | 6 | Rollback plan: how to revert if the site or hosts break | [ ] | | 7 | Post-patch version confirmed | [ ] | ## Worksheet 3: Compromise review (flaws exploited before the fix) For each item, write what you looked at, what you found, and who checked. - Logins to vCenter and ESXi since September, especially from unfamiliar addresses: ______________________ - New or changed accounts and roles: ______________________ - New scheduled tasks, services or startup items: ______________________ - Unexpected outbound connections from management hosts: ______________________ - Management interface exposed to the internet at any time (yes/no/unknown): ______________________ - Reviewed by / date: ______________________ ## Template 1: Email to your managed IT provider ```text Subject: Written answers needed: VMware vCenter and NGINX critical flaws Hello [name], Two critical flaws were disclosed this week: VMware vCenter CVE-2026-123890 (reportedly exploited since September) and a set of NGINX flaws including CVE-2026-123007. Please answer in writing: 1. Do we run vCenter, and which version? Do we run NGINX anywhere, including inside appliances? 2. Have both been patched? On what dates? 3. Was any management interface ever reachable from the internet? 4. Can you show vCenter and ESXi logs back to September, and tell us what you found in them? 5. What is your plan if something suspicious turns up? Please reply by [date, three business days out]. If you cannot answer any item, tell us which and why. Thank you, [name] ``` ## Template 2: One-page patch policy ```text Patch policy for [company], effective [date] Owner: [name] is responsible for patching on each system listed in our inventory. Critical flaws (CVSS 9.0 or higher) and flaws known to be exploited: patched within [number] days of the vendor fix. Other high-severity flaws: patched within [number] days. CISA KEV: we check the Known Exploited Vulnerabilities catalog every [day of week]. If a product we run appears, CISA's due date becomes our deadline. Exceptions: recorded in writing with a reason, a compensating control (for example VPN-only access) and a review date. Providers: our IT provider confirms patch status in writing within [number] business days of any critical advisory. Review: this policy is reviewed every [number] months. ``` ## Hardening checklist: management interfaces - [ ] Management interfaces reachable only through a VPN or a short admin address allowlist. - [ ] No management ports forwarded from the router or exposed by a cloud firewall rule. - [ ] Separate admin accounts from everyday accounts; remove ones nobody recognises. - [ ] Multi-factor authentication on every admin login that supports it. - [ ] Log retention long enough to look back several months. - [ ] A named person receives alerts for failed or unusual admin logins. ## AI prompts to paste ```text I run a small business with these systems: [list]. Which might use VMware vCenter or NGINX, including inside appliances or managed hosting? Give me a checklist to confirm each one without being an engineer, and say when you are unsure. ``` ```text Review these vCenter and ESXi log excerpts, account lists and scheduled tasks: [paste]. Flag anything that looks like prior compromise since September, explain why, and tell me what else you would need if the data is not enough to judge. ``` ## Sources - https://apprised.news/desk/tech/2026-11-20 - https://apprised.news/desk/tech/2026-11-19 - https://www.rapid7.com/blog/post/etr-cve-2026-123890-critical-authentication-bypass-vmware-vcenter - https://www.securityweek.com/newly-patched-vmware-vcenter-flaw-exploited-as-zero-day-by-chinese-apt/ - https://www.bleepingcomputer.com/news/security/vmware-patches-vcenter-zero-day-exploited-in-attacks-since-september/ - https://blog.qualys.com/product-tech/patch-management/2026/11/18/nginx2root-five-nginx-flaws-led-by-cve-2026-123007-how-to-find-mitigate-and-patch-now - https://www.tenable.com/blog/nginx2root-cve-2026-123007-frequently-asked-questions-about-five-critical-nginx - https://thehackernews.com/2026/11/10-year-old-nginx-http2-flaw-lets.html