CVE-2026-47871
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 directory traversal vulnerability. Flaws in file path validation allow malicious, authenticated network users to perform directory traversal attacks. 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 directory traversal vulnerability caused by insufficient file path validation. Authenticated network users can craft malicious requests with directory traversal sequences (e.g., ../../../) to access files outside the intended web root directory. The vulnerability stems from improper input sanitization in file handling functions.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Identify the installed VMware Avi Load Balancer versionLog into the Avi Controller UI and navigate to Administration > System > Settings, or use the command-line: 'show version' from the Avi shellAffected if The installed version is earlier than 32.1.2, 31.2.2-2p3, or 30.2.7 (or belongs to an earlier major release line)
-
Confirm network accessibility of the Avi Load Balancer management interfaceVerify that the Avi Controller IP/hostname is reachable on ports 443 or 80 from untrusted network segments using tools like nmap or curlAffected if The management interface is exposed to network segments containing untrusted or anonymous users
-
Determine if default or weak authentication is in useCheck the Avi UI under Access Settings > User Authentication to verify if local accounts, LDAP, or SAML are properly configured with strong credentials, and review the number of enabled user accountsAffected if There are multiple enabled user accounts with weak or shared passwords, or anonymous access is permitted
-
Inspect for signs of directory traversal exploitationReview Avi Controller logs under Operations > Logs for abnormal file access patterns, especially requests containing '../' sequences in file paths, or check web server access logs for traversal patternsAffected if Log entries show file path traversal attempts or unusual file read operations outside the expected directories
A user is affected if the Avi Load Balancer version is older than 32.1.2, 31.2.2-2p3, or 30.2.7 AND the management interface is accessible to untrusted authenticated network users.
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 · scopedUpgrade VMware Avi Load Balancer to the fixed versions (32.1.2, 31.2.2-2p3, or 30.2.7 depending on your branch). If immediate patching is not possible, implement strict access controls and network segmentation to limit authenticated user access to the management interface.
32.1.2, 31.2.2-2p3, or 30.2.7 depending on starting version (22.1.x should upgrade to 30.2.7)
- 1. Identify the current VMware Avi Load Balancer version via the admin UI or CLI (show version)
- 2. Based on the current version, determine the target 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 Networks upgrade documentation and release notes for the target version
- 4. Create a full backup of the Avi configuration before proceeding
- 5. Schedule a maintenance window as upgrades may require downtime
- 6. Download the target fixed version upgrade package from the VMware/Avi support portal (support.broadcom.com)
- 7. Upload the upgrade bundle via the Avi admin UI (Templates > Software > Upload) or CLI
- 8. Initiate the upgrade through the UI (Templates > Software > Upgrade) or CLI (upgrade start)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47871 — 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-47871 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