Avi Load Balancer: Improper Limitation of a Pathname to a Restricted Directory
CVE-2026-47871 is a high-severity improper limitation of a pathname to a restricted directory vulnerability in Avi Load Balancer from VMware, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. Affected Avi Load Balancer versions: 32.1.1; 31.1.1 through 31.2.2; 30.1.1 through 30.2.6, and others listed below. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.96% chance of exploitation within 30 days, higher than 62% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Vmware Avi Load Balancer to 30.2.7 or 31.2.2, whichever matches your release line, or a later version.
- Read the advisory on support.broadcom.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| VMware | Avi Load Balancer | 32.1.1; 31.1.1 through 31.2.2; 30.1.1 through 30.2.6; 22.1.1 through 22.1.7 | Not stated |
| Broadcom | Vmware Avi Load Balancer | 22.1.1 through 22.1.7; 30.1.1 up to, but not including, 30.2.7; 31.1.1 up to, but not including, 31.2.2; 31.2.2; 32.1.1 | 30.2.7, 31.2.2 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (vmware.com).
Official description
VMware 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)
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Limitation of a Pathname to a Restricted Directory
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
How developers prevent this class of flaw
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
- Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth.
More Improper Limitation of a Pathname to a Restricted Directory vulnerabilities (CWE-22)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in Avi Load Balancer
- 8.8 High severity
- 8.8 High severity
- 7.8 High severity
- 8.8 High severity
- 8.3 High severity
- 9.8 Critical severity
Recent Improper Limitation of a Pathname to a Restricted Directory vulnerabilities
- 10.0 Critical severity
- 9.9 Critical severity
- 8.1 High severity
- 8.8 High severity
- 7.1 High severity
- 7.5 High severity
Spotted an error? Tell us.