The Exploit Bulletin

Archives
Log in
Subscribe
November 20, 2026

The Exploit Bulletin — Friday, November 20, 2026: 4 issues require action

Friday, November 20, 2026 — 4 issues require action. If you run none of the software below, you are done.

Affects: VMware vCenter / Telco Cloud · F5 NGINX Plus / F5 NGINX Ingress Controller / F5 NGINX Gateway Fabric / F5 NGINX Instance Manager / F5 DoS / NGINX Open Source · Chamilo LMS · BerriAI LiteLLM proxy / Red Hat images bundling litellm only


1. Authentication bypass in the VMware Directory Service grants unauthenticated admin access to vCenter (CVE-2026-123890)

AUTHENTICATION BYPASS · CRITICAL · CVSS 9.8

Broadcom published the fix on 2026-11-19 while Google's Mandiant reports the China-nexus group Armory Castle (formerly UNC5221) has been exploiting this as a zero-day since early September 2026, so any unpatched vCenter reachable by an attacker should be assumed targeted for full administrative takeover.

An alternate-path authentication bypass (CWE-288) in the VMware Directory Service lets any actor with network access to vCenter bypass authentication and gain unauthorized access to the system, giving control over the ESX hosts and virtual machines it manages. Broadcom lists no workaround; fixed builds are available for all supported branches.

Affected: VMware vCenter 9.1.x before 9.1.1.0200; VMware vCenter 9.0.x before 9.0.2.0200; VMware vCenter 8.0 before 8.0 U3m; VMware vCenter / Cloud Foundation 5.x before 5.2.5; VMware Telco Cloud Platform 3.0, 4.x, 5.0.x, 5.1.x, 5.2 (see KB463116); VMware Telco Cloud Infrastructure 3.0 (see KB463116)

How to Test: Check the vCenter build in the vSphere Client or appliance management interface against the fixed builds (9.1.1.0200, 9.0.2.0200, 8.0 U3m, 5.2.5); anything older on a supported branch is vulnerable. Because exploitation predates the patch by more than two months, review vCenter and VMware Directory Service authentication logs for unexpected administrative sessions since early September 2026 and compare hosts against the indicators in Google's Armory Castle write-up.

How to Patch: Upgrade vCenter to 9.1.1.0200, 9.0.2.0200, 8.0 U3m, or 5.2.5 per VMSA-2026-0009; Telco Cloud Platform and Telco Cloud Infrastructure customers should follow KB463116. Broadcom lists no workaround, so if an upgrade must wait, restrict network access to vCenter to trusted management networks only.

Evidence: VulnCheck KEV · Rapid7: Mandiant confirmed in-the-wild exploitation by ARMORY CASTLE · Canadian Centre for Cyber Security AV26-1185 · BleepingComputer: zero-day exploited since September · The Hacker News: Armory Castle exploitation · Google Threat Intelligence write-up with request-level PoC

Full entry with sources →


2. HTTP/2 flow-control window overflow in nginx and NGINX Plus allows unauthenticated heap corruption and code execution (CVE-2026-123007)

REMOTE CODE EXECUTION · CRITICAL · CVSS 9.2

F5 shipped out-of-band fixes on 2026-11-18 and public exploit code plus a Censys reproduction test are already circulating, so any HTTP/2-enabled nginx left unpatched is exposed to unauthenticated worker crashes and, where ASLR is defeated, code execution.

When a stream is terminated nginx refunds unsent payload to the connection window; if the client raised the window after frames were queued, the refund can exceed NGX_HTTP_V2_MAX_WINDOW, breaking buffer size control in ngx_http_v2_send_chain() and corrupting heap memory. An unauthenticated remote client can crash the worker process and, on systems with ASLR disabled or bypassed, execute code as the nginx worker. HTTP/2 must be enabled for the flaw to be reachable.

Affected: NGINX Open Source >= 1.9.5 < 1.31.9 / 1.30.7 with HTTP/2 enabled; F5 NGINX Plus (fixed per F5 K000163926); F5 NGINX Ingress Controller >= 5.0.0 < 5.8.0, >= 2026-lts-r1 < 2026-lts-r11, 3.7.1, 3.7.2, 4.0.0, 4.0.1; F5 NGINX Gateway Fabric >= 1.5.0 <= 1.6.2 and >= 2.0.0 < 2.9.0; F5 NGINX Instance Manager >= 2.19.0 < 2.25.0; F5 DoS >= 4.5.0 <= 4.7.0 and >= 4.8.0 < 4.13.0; ingress-nginx images bundling nginx 1.27.1 (chainguard fork fixed in image tag v2.2.25)

How to Test: Confirm your nginx or NGINX Plus build version and whether HTTP/2 is enabled in your configuration; open source builds older than 1.31.9 (or 1.30.7 on the stable branch) are affected, and Censys published a compact cleartext HTTP/2 test with vulnerable and patched packet captures plus a version-match regex you can run against banners. Review nginx error logs for unexpected worker segmentation faults, which is the typical symptom of the flow-control window overflow being triggered.

How to Patch: Upgrade to nginx 1.31.9 or 1.30.7 (upstream commit b89c4100bf6762a45e4a6463eaf4b70368277c94 adds the h2c->send_queued counter), or to the fixed F5 builds: NGINX Ingress Controller 5.8.0 / 2026-lts-r11, NGINX Gateway Fabric 2.9.0, NGINX Instance Manager 2.25.0, F5 DoS 4.13.0, and the NGINX Plus release referenced in F5 K000163926; distribution users should take the Ubuntu and Red Hat updates. If you cannot upgrade immediately, disable HTTP/2 on affected listeners, since the flaw is only reachable when HTTP/2 is enabled.

Evidence: VulnCheck KEV · VulnCheck XDB exploit · BleepingComputer write-up with request-level PoC · Tenable FAQ on NGINX2Root · Censys lab reproduction and test · The Register coverage

Full entry with sources →


3. Unauthenticated remote code execution in Chamilo LMS before 2.0.1 (CVE-2026-45140)

REMOTE CODE EXECUTION · CRITICAL · CVSS 9.8

VulnCheck's canary sensors recorded exploitation attempts against this flaw on 2026-11-19, so an internet-facing Chamilo instance still below 2.0.1 can be taken over by anyone sending the right request.

Chamilo LMS versions before 2.0.1 let an unauthenticated remote attacker execute arbitrary code on the server; the project's advisory does not disclose the affected component, input or request. The fix is in release 2.0.1.

Affected: Chamilo LMS < 2.0.1

How to Test: Confirm the installed Chamilo LMS version; anything below 2.0.1 is affected. Because the vulnerable endpoint is not disclosed, review web server access logs for unexpected requests to the Chamilo installation from unknown sources, and inspect the web root for recently modified or unfamiliar files and for unexpected processes running as the web server user.

How to Patch: Upgrade to Chamilo LMS 2.0.1 (https://github.com/chamilo/chamilo-lms/releases/tag/v2.0.1); the corrective change is commit 4bdba1b9a8820bd70c0809317775d7f6eaa79844. If the upgrade must wait, restrict access to the instance to trusted networks in the meantime.

Evidence: VulnCheck KEV

Full entry with sources →


4. Host-header parsing flaw in LiteLLM proxy bypasses authentication on management routes (CVE-2026-49468)

AUTHENTICATION BYPASS · CRITICAL · CVSS 9.5

VulnCheck's canary sensors recorded exploitation attempts against this flaw on 2026-11-19 and a public exploit is available, so LiteLLM proxies still below 1.84.0 with management routes reachable are now being probed for unauthenticated admin access.

The LiteLLM proxy's auth layer derived the effective route from request.url.path in litellm/proxy/auth/auth_utils.py::get_request_route(), which Starlette reconstructs from the Host header, so a crafted Host header makes the auth gate evaluate a different route from the one FastAPI actually dispatches. Under specific conditions this gives an unauthenticated attacker access to protected management routes, which Red Hat assesses can lead to full system compromise.

Affected: BerriAI LiteLLM proxy < 1.84.0; Red Hat images bundling litellm (OpenShift AI, Ansible Automation Platform) only when an administrator runs the LiteLLM proxy via litellm --config

How to Test: Check the installed litellm package version; anything below 1.84.0 running the proxy server (litellm --config) is affected, while containers that only run OGX, MLflow with the AI Gateway disabled, Garak, or Lightspeed/Llama Stack APIs by default do not expose the vulnerable path. Review proxy and load-balancer access logs for requests with unusual or non-matching Host headers hitting management routes.

How to Patch: Upgrade LiteLLM to 1.84.0 or later (release v1.84.0, advisory GHSA-4xpc-pv4p-pm3w). Until then, restrict inbound access to the proxy's management routes to trusted internal networks via firewalls or security groups, and configure any load balancer or API gateway in front of the proxy to strictly validate and sanitize the HTTP Host header before forwarding requests.

Evidence: VulnCheck KEV · VulnCheck XDB exploit

Full entry with sources →


Read on the web · Every past edition

The Exploit Bulletin is free and daily. It publishes only what security teams must act on today — nothing else. Forward it freely.

Spot an error, or an exploit we missed? Reply here or email [email protected].

Don't miss what's next. Subscribe to The Exploit Bulletin:
← Newer The Exploit Bulletin — Saturday, November 21, 2026: 2 issues require action Older → The Exploit Bulletin — Thursday, November 19, 2026: 10 issues require action
www.exploitbulletin.com
jbac.co
LinkedIn
Powered by Buttondown, the easiest way to start and grow your newsletter.