SECURITYHIGHCVE-2026-47868

CVE-2026-47868: VMware Avi Load Balancer Local Privilege Escalation

A local privilege escalation vulnerability in VMware Avi Load Balancer allows malicious local users to execute code as root. Versions 22.x through 32.1.1...

Dylan H.

Security Team

July 19, 2026
2 min read
CVE-2026-47868: VMware Avi Load Balancer Local Privilege Escalation

Affected Products

  • VMware Avi Load Balancer 22.1.x, 30.1.x - 30.2.6, 31.1.x - 31.2.2, 32.1.1

Overview

VMware has disclosed CVE-2026-47868, a local privilege escalation vulnerability in its Avi Load Balancer product. A malicious user with local system access may exploit flaws in the software to escalate their privileges and execute arbitrary code as root.

The vulnerability carries a CVSS v3.1 base score of 7.8 (High) and was published to the NVD on July 18, 2026.

Affected Versions

Version BranchAffected RangeFixed Version
32.x32.1.132.1.2
31.x31.1.1 – 31.2.231.2.2-2p3
30.x30.1.1 – 30.2.630.2.7
22.x22.1.1 and later (branch)See VMware advisory

Technical Details

The vulnerability exists in the local privilege escalation surface of VMware Avi Load Balancer. Specifically, improper access controls or unsafe operations allow a locally authenticated user to gain elevated privileges up to root on the affected system.

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Impact: High Confidentiality, High Integrity, High Availability

Remediation

VMware has released patches to address this vulnerability:

  • 32.x: Upgrade to 32.1.2 or later
  • 31.x: Upgrade to 31.2.2-2p3 or later
  • 30.x: Upgrade to 30.2.7 or later

Administrators should apply the appropriate fix for their version branch as soon as possible.

Mitigation

If immediate patching is not possible:

  • Restrict local access to Avi Load Balancer management nodes to trusted administrators only
  • Audit local user accounts and remove any unnecessary accounts
  • Monitor for unusual privilege escalation activity in system logs
  • Apply principle of least privilege across all service accounts

References