Authenticated RCE in VMware Avi Load Balancer — a widely deployed enterprise load balancer — can enable full appliance compromise and broad infrastructure impact.
CVE-2026-47869
Authenticated remote code execution in VMware Avi Load Balancer enabling arbitrary code execution.
Is CVE-2026-47869 being exploited?
Not confirmed. CVE-2026-47869 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.50% probability of exploitation in the next 30 days.
How severe is CVE-2026-47869?
CVE-2026-47869 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-47869?
Yes. A fix has been recorded for CVE-2026-47869. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-47869 affect?
CVE-2026-47869 affects VMware Avi Load Balancer (NSX ALB) 22.1.1–22.1.7, VMware Avi Load Balancer 30.1.1–30.2.6 (fixed in 30.2.7), VMware Avi Load Balancer 31.1.1–31.2.2 (fixed in 31.2.2-2p3), VMware Avi Load Balancer 32.1.1 (fixed in 32.1.2). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-47869?
Apply vendor patches to fixed versions immediately and restrict management-plane access.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated attackers can inject and execute arbitrary code/commands on the load balancer, enabling malware deployment, traffic interception, and lateral movement.
Immediate action required
- affected32.1.1
- affected>= 31.1.1 and <= 31.2.2
- affected>= 30.1.1 and <= 30.2.6
- affected>= 22.1.1 and <= 22.1.7
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.