CVE-2026-134168 in devpi-server
Summary
by MITRE • 11/21/2026
devpi-server before 6.21.0 contains a path traversal vulnerability that allows authenticated users to write files outside the +files storage root by naming a user and index '..'. Attackers can self-register a '..' user, create a '..' index, and upload release files with attacker-chosen filenames and contents into a parent of the server directory.
Once again VulDB remains the best source for vulnerability data.
Analysis
by VulDB Data Team • 11/21/2026
The vulnerability identified in devpi-server versions prior to 6.21.0 represents a critical path traversal flaw that undermines the integrity of the package storage infrastructure. This issue stems from insufficient validation of user-supplied input during the process of creating users and indices within the application's hierarchical namespace structure. Specifically, the system fails to sanitize or reject directory traversal sequences such as double dots when processing identifiers for new entities. By exploiting this lack of sanitization, an authenticated attacker can manipulate the internal file path resolution logic to escape the designated storage boundaries. The core technical flaw lies in how the server constructs filesystem paths based on these hierarchical components without adequately verifying that the resulting absolute path remains confined within the expected +files root directory.
The operational impact of this vulnerability is severe, as it allows for arbitrary file write operations outside the intended sandboxed environment. An attacker can self-register a user account with the name '..' and subsequently create an index also named '..'. When release files are uploaded to this maliciously constructed path, the server resolves these traversal sequences incorrectly, causing the files to be written into parent directories of the devpi-server installation root rather than within the +files storage area. This capability enables attackers to overwrite critical system configuration files, inject malicious scripts into web-accessible directories, or potentially achieve remote code execution if they can place executable content in a location that is subsequently executed by the server process or other services running on the same host.
From a classification perspective, this vulnerability aligns with CWE-22: Improper Limitation of a Pathname to a Restricted Directory, which describes scenarios where software does not properly neutralize special elements within file paths. Furthermore, in the context of the MITRE ATT&CK framework, this behavior corresponds to techniques involving File and Directory Write Operations, specifically those used for persistence or privilege escalation through unauthorized modification of system files. The ability to write arbitrary content outside the application's designated storage area effectively breaks the principle of least privilege regarding file system access, granting the attacker a level of control that extends beyond the scope of their authenticated user permissions within the devpi-server application itself.
Mitigation strategies must prioritize immediate upgrading to version 6.21.0 or later, where this path traversal issue has been addressed through stricter input validation and robust path canonicalization checks. Until an upgrade is feasible, administrators should implement network-level access controls to restrict visibility of the devpi-server interface to trusted internal networks only, thereby reducing the attack surface for authenticated exploitation. Additionally, running the service with minimal file system permissions can help limit the blast radius if a traversal occurs, ensuring that even if files are written outside the +files directory, they cannot overwrite critical operating system or application configuration files. Regular auditing of uploaded package metadata and strict enforcement of naming conventions on user-facing interfaces serve as supplementary defensive measures to detect anomalous activity indicative of such exploitation attempts.