Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-54723 medium CVSS 6.5

Vulnerability in devpi-server (CVE-2026-54723)

Summary

Vulnerability in devpi-server (CVE-2026-54723). Risk of unauthorized operations or information disclosure. Exploitable via primary. Mitigation: upgrade to 6.20.2 or later.

Original description

The description as published by the source.

Impact

If the replication protocol is enabled by using the primary (or deprecated master) role for a server instance, then the +changelog URL route can be used to read the complete database content including password hashes, and the ids and salts of tokens from devpi-tokens by using a trivially modified GET request.

The leaked hashes use the argon2 algorithm, so they are not immediately at risk by brute-force methods, but dictionary attacks are feasible. If a database leak could have happened, it is advised to change the passwords after a patched version or other mitigation is in place.

When devpi-tokens is in use, the quality of the server secret is important. It might be possible to derive the server secret if actual tokens are public by using similar techniques to finding the password for a hash. If a database leak could have happened and any tokens are public, it is advised to change the server secret.

Besides the information leak this can be used to produce significant CPU, IO and bandwidth usage depending on the database size.

Patches

The logic bug causing this issue is fixed with devpi-server 6.20.2 and devpi-server 7.0.0b3.

Workarounds

When replication isn't used the role can explicitly be set to standalone.

If the server instance is exclusively served through nginx with the devpi-lockdown plugin, the request is redirected to the login form due to missing user information. There is no known exploit in this case.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-54723 has been found in devpi-server.
Attackers can target a specific entry point like primary over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.5/10.
What to do: upgrade devpi-server to 6.20.2 or later.
If unsure, ask your IT team or search "devpi-server CVE-2026-54723" on the vendor's site.

CVE-2026-54723 (devpi-server) — CWE-304 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: primary / master / argon2 / standalone
Patched: 6.20.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-304) exists in devpi-server. Attackers reach the vulnerable code path via primary without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of devpi-server. Attack surface: primary / master / argon2 / standalone.

🔥 Severity

Severity: Medium (CVSS 6.5/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 6.20.2.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'devpi-server' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'devpi-server' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で devpi-server を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade devpi-server to 6.20.2

    ステージング環境で 6.20.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

pip devpi-server
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.20.2"}]}]
PyPI devpi-server
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.20.2"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details