Red Hat Build of Podman Desktop: Improper Limitation of a Pathname to a Restricted Directory
CVE-2026-107935 is a critical-severity improper limitation of a pathname to a restricted directory vulnerability in Red Hat Build of Podman Desktop from Red Hat, with a CVSS 3.1 base score of 9.3 out of 10. It can be exploited from the same local network by an unauthenticated attacker, without any action from a user. There is no confirmed exploitation so far. EPSS estimates a 0.24% chance of exploitation within 30 days, which is low compared with other CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Check which version of Red Hat Build of Podman Desktop you run against the affected versions below, and install the vendor's latest release.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Red Hat | Red Hat Build of Podman Desktop | Not specified in the record | Not stated |
| Red Hat | Red Hat Certification Program for Red Hat Enterprise Linux 9 | Not specified in the record | Not stated |
| Red Hat | Red Hat Edge Manager 1 | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 10 | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 8 | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 9 | Not specified in the record | Not stated |
| Red Hat | Red Hat Hardened Images | Not specified in the record | Not stated |
| Red Hat | Red Hat OpenShift Container Platform 4 | Not specified in the record | Not stated |
| Red Hat | Red Hat OpenShift Container Platform 5 | Not specified in the record | Not stated |
| Red Hat | Red Hat OpenShift Dev Spaces | Not specified in the record | Not stated |
| Red Hat | Red Hat OpenStack Platform 18.0 | Not specified in the record | Not stated |
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
- AdjacentThe attacker must be on the same local network segment.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:H. Scored by CNA (redhat.com).
Official description
A path traversal vulnerability was found in gvproxy, the network forwarder provided by the gvisor-tap-vsock package. The unauthenticated /services/forwarder/expose endpoint does not validate the caller-supplied socket path, allowing an attacker to delete arbitrary files on the host system.
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: partial).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Other references
Other vulnerabilities in Red Hat Build of Podman Desktop
- 7.5 High severity
- 7.4 High severity
- 8.8 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
Recent Improper Limitation of a Pathname to a Restricted Directory vulnerabilities
- 8.1 High severity
- 8.8 High severity
- 7.5 High severity
- 7.5 High severity
- 9.1 Critical severity
- 7.3 High severity
Spotted an error? Tell us.