What is CVE-2026-54723?

CVE-2026-54723 is a medium-severity security vulnerability in devpi-server (pip), affecting versions < 6.20.2. It is fixed in 6.20.2.

How severe is CVE-2026-54723?

CVE-2026-54723 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of devpi-server are affected by CVE-2026-54723?

devpi-server (pip) versions < 6.20.2 is affected.

Is there a fix for CVE-2026-54723?

Yes. CVE-2026-54723 is fixed in 6.20.2. Upgrade to this version or later.

Is CVE-2026-54723 exploitable, and should I be worried?

Whether CVE-2026-54723 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-54723 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-54723?

Upgrade devpi-server to 6.20.2 or later.

CVE-2026-54723 in devpi-server

Q: How severe is CVE-2026-54723?

CVE-2026-54723 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of devpi-server are affected by CVE-2026-54723?

devpi-server (pip) versions < 6.20.2 is affected.

Q: Is there a fix for CVE-2026-54723?

Yes. CVE-2026-54723 is fixed in 6.20.2. Upgrade to this version or later.

Q: Is CVE-2026-54723 exploitable, and should I be worried?

Whether CVE-2026-54723 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-54723 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-54723?

Upgrade devpi-server to 6.20.2 or later.

Summary

devpi-server may leak database contents

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.

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.

CVE-2026-54723 has a CVSS score of 6.5 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (6.20.2); upgrading removes the vulnerable code path.

Affected versions

devpi-server (< 6.20.2)

Security releases

devpi-server → 6.20.2 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

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

Frequently Asked Questions

What is CVE-2026-54723? CVE-2026-54723 is a medium-severity security vulnerability in devpi-server (pip), affecting versions < 6.20.2. It is fixed in 6.20.2.
How severe is CVE-2026-54723? CVE-2026-54723 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of devpi-server are affected by CVE-2026-54723? devpi-server (pip) versions < 6.20.2 is affected.
Is there a fix for CVE-2026-54723? Yes. CVE-2026-54723 is fixed in 6.20.2. Upgrade to this version or later.
Is CVE-2026-54723 exploitable, and should I be worried? Whether CVE-2026-54723 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-54723 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-54723? Upgrade devpi-server to 6.20.2 or later.