Privilege Escalation in VMware Avi Load Balancer (CVE-2026-47870)
Summary
Vulnerability in VMware Avi Load Balancer (CVE-2026-47870). Confidential information can be exposed externally. Mitigation: upgrade to 32.1.2 or later.
Original description
The description as published by the source.
VMware Avi Load Balancer contains a privilege escalation vulnerability. A malicious authenticated user with network access may be able to execute remote code.
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)
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-47870 has been found in VMware Avi Load Balancer.
Confidential information can be exposed externally. CVSS score: 7.1/10.
What to do: upgrade VMware Avi Load Balancer to 32.1.2 or later.
If unsure, ask your IT team or search "VMware Avi Load Balancer CVE-2026-47870" on the vendor's site.
CVE-2026-47870 (VMware Avi Load Balancer) — CWE-269 / CVSS v3 7.1
Attack vector: remote (network-reachable) / no user interaction
Patched: 32.1.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-269) exists in VMware Avi Load Balancer.
Check the vendor advisory for the affected versions of VMware Avi Load Balancer.
Severity: High (CVSS 7.1/10). Confidential information can be exposed externally.
Update to 32.1.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで VMware Avi Load Balancer を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade VMware Avi Load Balancer to 32.1.2ステージング環境で 32.1.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- patch security@vmware.com
- web nvd.nist.gov
- web github.com