Unauthenticated denial of service via unbounded username logging
Published Aug 7, 2026 · Updated Aug 7, 2026
Resource-consumption flaw in JupyterHub before 5.5.0 allows remote attackers to exhaust logging and storage through failed logins. The login handlers and default PAMAuthenticator write the full attacker-controlled username to failed-login logs without a length bound. Only form-based authenticators are exposed; repeated unauthenticated submissions consume log and storage resources, while OAuthenticator deployments are unaffected.
Summary
What happened
Resource-consumption flaw in JupyterHub before 5.5.0 allows remote attackers to exhaust logging and storage through failed logins. The login handlers and default PAMAuthenticator write the full attacker-controlled username to failed-login logs without a length bound. Only form-based authenticators are exposed; repeated unauthenticated submissions consume log and storage resources, while OAuthenticator deployments are unaffected.
The record
- CVE
- CVE-2026-54338
- Published
- Aug 7, 2026
- Updated
- Aug 7, 2026
- Vendor
- Project Jupyter
- Product
- JupyterHub
- Classifications
- CWE-400, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 7, 2026CVE publishedPublication date reported by the CVE source.
- Aug 7, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 5.5.0JupyterHub is software that allows users to create a multi-user server for Jupyter notebooks. Prior to 5.5.0, invalid input to form-based login authenticators can place an unbounded attacker-controlled username in failed-login logs, allowing an unauthenticated attacker to consume logging and storage resources. This issue is fixed in version 5.5.0.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo