devpi-web unauthenticated path traversal in documentation route
Affects devpi-web before 5.2.0 on servers where any self-registered user can upload a doczip to their own index. Fixed in 5.2.0.
- Exploited
- No known exploitation
- Fix
- Fixed in 5.2.0
- Who is exposed
- Default setups
Summary
Path traversal in devpi-web lets an unauthenticated attacker send a crafted request to the +doc documentation route over the network and read files on the server. The description says this includes the keyfs sqlite database, which holds password hashes.
Written by a model
Original description
devpi-web before 5.2.0 contains an unauthenticated path traversal vulnerability in the +doc documentation route because docs_file_exists and docs_file_path in doczip.py never confine relpath to the documentation directory. Attackers can request a relpath with a leading // or percent-encoded .. segments to read server files, including the keyfs sqlite database holding password hashes.
Who should check
Teams running devpi-web before 5.2.0 as part of a devpi index server, including default installs that allow self-registered users and doc uploads
“Affecting devpi-web >= 0, < 5.2.0”
What to do
Check every install: default setups are affected.
Upgrade to a fixed version: 5.2.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-134167 (devpi-web before 5.2.0 Unauthenticated Path Traversal via +doc Route), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-134167 (entry last updated 2026-11-20):
Affected:
- PyPI package devpi-web: fixed in 5.2.0
Fixed versions: 5.2.0.
Conditions (all must be true for the bug to be hit):
- A project/version with an uploaded doczip must exist on the server, which any self-registered user can create on their own index (source: https://github.com/devpi/devpi/security/advisories/GHSA-w72q-5vww-p2rh)
- devpi-web versions before 5.2.0 (source: https://www.vulncheck.com/advisories/devpi-web-before-5.2.0-unauthenticated-path-traversal-via-doc-route)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-134167 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134167 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (PyPI): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/devpi/devpi/security/advisories/GHSA-w72q-5vww-p2rh
- https://github.com/devpi/devpi/commit/680fca1607840905dab6c54059b65ba326f46850
- https://github.com/devpi/devpi/blob/a67a065777d372acca968ab7b5cf362dc2ceb911/web/devpi_web/doczip.py#L78-L87
- https://pypi.org/project/devpi-web/5.2.0/
- https://www.vulncheck.com/advisories/devpi-web-before-5.2.0-unauthenticated-path-traversal-via-doc-route
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-134167
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134167"}.Affected versions
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure22/25Default setups, reachable over the network without a login
- Reach10/20Affects PyPI packages
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 81 if added to CISA KEV
- Would score about 76 if CISA's SSVC rates exploitation active
Timeline
- CVE published
- First seen by cve.now
Evidence 7
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · devpi/devpi · Advisory GHSA-w72q-5vww-p2rh |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134167 |
| Record | NVD · CVE-2026-134167 |
| Other links 4 | |
| Patch | GitHub · devpi/devpi · Commit 680fca16 |
| Repository | GitHub · devpi/devpi · web/devpi_web/doczip.py · L78-L87 |
| Link | pypi.org · project/devpi-web/5.2.0 |
| Link | vulncheck.com · advisories/devpi-web-before-5.2.0-unauthenticated-path-traversal-via-doc-route |
Questions about CVE-2026-134167
Is CVE-2026-134167 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
A flaw in the +doc route lets an unauthenticated visitor read files outside the intended documentation area by using path traversal. Anything the server process can read is exposed, including the keyfs sqlite database that holds password hashes and token ids.
Source: github.com, vulncheck.com
Which versions are affected by CVE-2026-134167?
devpi-web (PyPI): before 5.2.0.
Source: cve.now feed data
Am I affected, and how do I check?
devpi-web versions before 5.2.0 are affected, but only where a project/version with an uploaded doczip exists on the server, which any self-registered user can create on their own index. To check, look at the installed devpi-web version and whether any index has uploaded documentation.
Source: github.com, vulncheck.com
How do I fix CVE-2026-134167?
Upgrade devpi-web to 5.2.0 or later, which is the listed fixed version. No vendor patch identifiers are given.
Source: github.com, vulncheck.com
Related
- CVE-2026-54723devpi: Database contents leak
- CVE-2026-134168devpi-server before 6.21.0 Path Traversal via '..' User and Index Names
- CVE-2026-133501Gladys Assistant Backup Restore gateway.downloadBackup.js path traversal
- CVE-2026-126054Path Traversal in Dataform, BigQuery Studio and Colab Enterprise allows Cross-Tenant File Read and Write
- CVE-2026-77355isomorphic-git: NTFS .git::$INDEX_ALLOCATION alias bypass writes into the active gitdir
- CVE-2026-77309AIT-GUI route chain allows unauthenticated Python execution in server process
No corrections so far. Something wrong on this page? Report an error.