CVE-2026-47867: VMware Avi Load Balancer Remote Code Execution Vulnerability
Telemetry drift only. No threshold crossed and no authority ruling changed.
CVE record, CISA KEV and EPSS as of 2026-10-18.
CVEs like this one computed, by meaning
What to do now held facts and links
- Upgrade to the fixed version for your release line, or later: vmware avi load balancer 30.2.7; vmware avi load balancer 31.2.2 upper bounds of the CVE record's affected ranges
- Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
- Check your version against the ranges this record publishes.
What it is stated by the CNA
VMware Avi Load Balancer contains a remote code execution vulnerability. A malicious user with network access may be able to access the Avi Control plane and execute code remotely. Affected versions: 32.1.1 (fixed in 32.1.2) 31.1.1 through 31.2.2 (fixed in 31.2.2-2p3) 30.1.1 through 30.2.6 (fixed in 30.2.7) 22.1.1 through 22.1.7 (fixed in 30.2.7)
- weakness
- CWE-94 Improper Control of Generation of Code ('Code Injection')
- affected
- VMware Avi Load Balancer
- published ranges
- broadcom vmware avi load balancer >= 22.1.1 <= 22.1.7; broadcom vmware avi load balancer >= 30.1.1 < 30.2.7; broadcom vmware avi load balancer >= 31.1.1 < 31.2.2; broadcom vmware avi load balancer 31.2.2; and 3 more on the CVE page
- first unaffected version, by branch
- vmware avi load balancer 30.2.7; vmware avi load balancer 31.2.2
- severity
- 8.7 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N
- assigned by
- vmware
- published
- 2026-07-18
check us support.broadcom.com
Exploit code held, dated
- exploit code
- None held in the PoC-in-GitHub feed. A public repository changes this brief.
What moved held, dated
| date | EPSS | event |
|---|---|---|
| 18 Jul 2026 | 0.00682 | |
| 24 Jul 2026 | 0.00441 | |
| 21 Aug 2026 | 0.00496 | |
| 28 Sep 2026 | 0.00739 |
4 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.
Outside the record researched, cited
This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.
What would change this brief held, dated
- CISA KEV
- Not listed in the catalogue we hold. A listing changes this brief.
- exploit probability
- 0.01 on 2026-09-28 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
- fix
- Held: vmware avi load balancer 30.2.7; vmware avi load balancer 31.2.2. A newer fix from the CNA or OSV changes this brief.
How to check this
Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:
SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2026-47867', '2026-10-29T23:59:59.999999Z', now());