CVE-2026-34052 | jupyterhub ltiauthenticator up to 1.6.2 memory leak (GHSA-8mxq-7xr7-2fxj)
VulDBArchived Apr 04, 2026✓ Full text saved
A vulnerability was found in jupyterhub ltiauthenticator up to 1.6.2 . It has been rated as problematic . This issue affects some unknown processing. The manipulation leads to memory leak. This vulnerability is documented as CVE-2026-34052 . The attack can be initiated remotely. There is not any exploit available. Upgrading the affected component is advised.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-355272 · CVE-2026-34052 · GHSA-8MXQ-7XR7-2FXJ
JUPYTERHUB LTIAUTHENTICATOR UP TO 1.6.2 MEMORY LEAK
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
4.7 $0-$5k 0.31+
Summaryinfo
A vulnerability categorized as problematic has been discovered in jupyterhub ltiauthenticator up to 1.6.2. Impacted is an unknown function. The manipulation results in memory leak. This vulnerability is reported as CVE-2026-34052. The attack can be launched remotely. No exploit exists. It is advisable to upgrade the affected component.
Detailsinfo
A vulnerability was found in jupyterhub ltiauthenticator up to 1.6.2. It has been classified as problematic. Affected is an unknown functionality. The manipulation with an unknown input leads to a memory leak vulnerability. CWE is classifying the issue as CWE-401. The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory. This is going to have an impact on availability. CVE summarizes:
LTI JupyterHub Authenticator is a JupyterHub authenticator for LTI. Prior to version 1.6.3, the LTI 1.1 validator stores OAuth nonces in a class-level dictionary that grows without bounds. Nonces are added before signature validation, so an attacker with knowledge of a valid consumer key can send repeated requests with unique nonces to gradually exhaust server memory, causing a denial of service. This issue has been patched in version 1.6.3.
The advisory is shared for download at github.com. This vulnerability is traded as CVE-2026-34052 since 03/25/2026. The exploitability is told to be difficult. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1499.
Upgrading to version 1.6.3 eliminates this vulnerability. The upgrade is hosted for download at github.com.
Productinfo
Vendor
jupyterhub
Name
ltiauthenticator
Version
1.6.0
1.6.1
1.6.2
Website
Product: https://github.com/jupyterhub/ltiauthenticator/
CPE 2.3info
🔒
🔒
🔒
CPE 2.2info
🔒
🔒
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv3info
VulDB Meta Base Score: 4.8
VulDB Meta Temp Score: 4.7
VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.9
CNA Vector (GitHub_M): 🔒
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Memory leak
CWE: CWE-401 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: Upgrade
Status: 🔍
0-Day Time: 🔒
Upgrade: ltiauthenticator 1.6.3
Timelineinfo
03/25/2026 CVE reserved
04/04/2026 +9 days Advisory disclosed
04/04/2026 +0 days VulDB entry created
04/04/2026 +0 days VulDB entry last update
Sourcesinfo
Product: github.com
Advisory: GHSA-8mxq-7xr7-2fxj
Status: Confirmed
CVE: CVE-2026-34052 (🔒)
GCVE (CVE): GCVE-0-2026-34052
GCVE (VulDB): GCVE-100-355272
Entryinfo
Created: 04/04/2026 08:09
Changes: 04/04/2026 08:09 (65)
Complete: 🔍
Cache ID: 99:555:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸