EUVD-2026-77701
GHSA-m5pq-69xg-vcq3
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L
Full database dump via unauthenticated network request justifies C:H over NVD's C:L; A:L reflects bandwidth and CPU exhaustion; no integrity impact applies.
Primary rating from Vendor (https://github.com/devpi/devpi).
CVSS VectorVendor: https://github.com/devpi/devpi
Lifecycle Timeline
2DescriptionCVE.org
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.
AnalysisAI
Unauthenticated full database disclosure in devpi-server affects instances configured in primary or master replication mode, allowing any network-reachable attacker to retrieve the complete database via a trivially modified GET request to the +changelog endpoint. Exposed data includes argon2 password hashes and devpi-tokens metadata (IDs and salts), enabling offline dictionary attacks against credentials and potential server-secret derivation if tokens are public. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | The server must be explicitly configured with the primary or deprecated master replication role - the default standalone mode does not expose the +changelog endpoint and is entirely unaffected. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The NVD CVSS 3.1 score of 6.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L) likely underrepresents the confidentiality impact: C:L typically implies partial data disclosure, but the +changelog endpoint returns the complete database including all user credentials and token material - a more accurate characterization is C:H. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | Upgrade devpi-server to version 6.20.2 (stable) or 7.0.0b3 (beta) immediately, as these releases contain the logic bug fix for the +changelog endpoint. … Detailed patch versions, workarounds, and compensating controls in full report. |
Threat intelligence, references, and detailed analysis are available after sign-in.
Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour
The ngx_http_parse_chunked function in http/ngx_http_parse.c in nginx 1.3.9 through 1.4.0 allows remote attackers to cau
A critical vulnerability in Kubernetes ingress-nginx controller allows unauthenticated attackers with pod network access
nginx 0.8.41 through 1.4.3 and 1.5.x before 1.5.7 allows remote attackers to bypass intended restrictions via an unescap
An issue was discovered on GL.iNet devices before version 4.5.0. Rated critical severity (CVSS 9.8), this vulnerability
Nginx versions since 0.5.6 up to and including 1.13.2 are vulnerable to integer overflow vulnerability in nginx range fi
The resolver in nginx before 1.8.1 and 1.9.x before 1.9.10 allows remote attackers to cause a denial of service (invalid
Kubernetes ingress-nginx contains a configuration injection vulnerability via the mirror-target and mirror-host Ingress
A security issue was discovered in ingress-nginx https://github.com/kubernetes/ingress-nginx where the `auth-url` Ingres
A security issue was discovered in ingress-nginx https://github.com/kubernetes/ingress-nginx where the `auth-tls-match-c
Roxy-WI is a web interface for managing Haproxy, Nginx, Apache and Keepalived servers. Rated critical severity (CVSS 9.8
The STARTTLS implementation in mail/ngx_mail_smtp_handler.c in the SMTP proxy in nginx 1.5.x and 1.6.x before 1.6.1 and
Same weakness CWE-304 – Missing Critical Step in Authentication
View allSame technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today