CVE-2026-47867
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedVMware 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)
In the news
Third-party coverageSurfaced from public web coverage — external links open in a new tab.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceVMware Avi Load Balancer contains a remote code execution vulnerability in the Avi Control plane. A malicious user with network access to the control plane can execute arbitrary code remotely on affected installations, bypassing authentication or exploiting insufficient access controls.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm VMware Avi Load Balancer is installedIdentify the product by checking for Avi controller processes or checking the management interface login page. Look for 'Avi' branding or access the /api endpoint which typically returns Avi-specific JSON responses.Affected if The system is running VMware Avi Load Balancer software.
-
Determine installed versionAccess the Avi Control Plane management interface and navigate to the version information page, typically found under Administration > System > System Properties, or use the API endpoint /api/systemconfiguration to retrieve the version details.Affected if The installed version is prior to 32.1.2, 31.2.2-2p3, or 30.2.7.
-
Check network exposure of management interfaceReview firewall rules, security groups, or network ACLs to determine if the Avi Control Plane management interface (ports 443, 80, or 22) is accessible from untrusted networks or the public internet.Affected if The management interface is reachable from untrusted network segments or the internet.
-
Verify access control configurationCheck the Avi controller access policy settings under Access Settings to determine if anonymous or unauthenticated access is permitted to the API or management endpoints.Affected if Anonymous or unauthenticated access is enabled for the control plane API.
A user is affected if they are running a vulnerable version of VMware Avi Load Balancer (pre-32.1.2, 31.2.2-2p3, or 30.2.7) with the management interface exposed to untrusted networks or with unauthenticated access permitted.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedApply vendor-supplied patches: upgrade to 32.1.2, 31.2.2-2p3, or 30.2.7 (or later) depending on the current version branch. Prioritize patching given the high CVSS score and network-exploitable nature.
Upgrade to 32.1.2, 31.2.2-2p3, or 30.2.7 depending on your current branch (see step 2)
- 1. Identify the current VMware Avi Load Balancer version by navigating to the Avi Controller admin UI or using the 'show version' CLI command
- 2. Based on the current installed version, determine the appropriate fixed release: for 32.1.1 upgrade to 32.1.2; for 31.1.1-31.2.2 upgrade to 31.2.2-2p3; for 30.1.1-30.2.6 upgrade to 30.2.7; for 22.1.1-22.1.7 upgrade to 30.2.7
- 3. Review VMware Avi Load Balancer upgrade documentation and ensure backup of configuration is performed
- 4. Schedule a maintenance window as upgrades may require service interruption
- 5. Download the appropriate upgrade image from Broadcom support portal (support.broadcom.com)
- 6. Upload the upgrade bundle via the Avi Controller UI (Operations > Upgrade) or CLI
- 7. Follow the on-screen upgrade wizard or documented CLI upgrade procedure
- 8. After upgrade completes, verify the new version matches the expected fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47867 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-47867 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data