Service interruption via pre-validation nonce accumulation
Published Apr 3, 2026 · Updated Apr 3, 2026
Resource exhaustion in LTI JupyterHub Authenticator before 1.6.3 allows remote attackers to interrupt service through LTI 1.1 requests. The LTI 1.1 validator inserts each OAuth nonce into a class-level dictionary before checking the request signature, and the dictionary has no size bound or eviction path. Knowledge of a valid consumer key is required; repeated requests carrying unique nonces steadily consume server memory until the JupyterHub service becomes unavailable.
Summary
What happened
Resource exhaustion in LTI JupyterHub Authenticator before 1.6.3 allows remote attackers to interrupt service through LTI 1.1 requests. The LTI 1.1 validator inserts each OAuth nonce into a class-level dictionary before checking the request signature, and the dictionary has no size bound or eviction path. Knowledge of a valid consumer key is required; repeated requests carrying unique nonces steadily consume server memory until the JupyterHub service becomes unavailable.
The record
- CVE
- CVE-2026-34052
- Published
- Apr 3, 2026
- Updated
- Apr 3, 2026
- Vendor
- Project Jupyter
- Product
- LTI JupyterHub Authenticator
- Classifications
- CWE-770, CWE-401, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 3, 2026CVE publishedPublication date reported by the CVE source.
- Apr 3, 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=< 1.6.3
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