CVE-2026-34052: LTI JupyterHub Authenticator is a JupyterHub authenticator for LTI

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

lti jupyterhub authenticator: upgrade to 1.6.3. Exact commands for each OS are on this page.

Q: Is CVE-2026-34052 being exploited?

CVE-2026-34052 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-34052 affect?

CVE-2026-34052 affects lti jupyterhub authenticator. Severity is medium (CVSS 5.9). 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

Q: How urgent is CVE-2026-34052?

Priority 32/100. Remotely exploitable, no login, no user action

Routine

MEDIUM 5.9REMOTEUPGRADE

CVE-2026-34052 is a medium-severity flaw (CVSS 5.9) affecting lti jupyterhub authenticator. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.9 (Medium)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.3% (top 74%)
CISA exploited list	No
Weakness	CWE-401, CWE-770
Published	2026-04-03
Last modified	2026-07-24

Publisher (CNA): GitHub, Inc. · Vendor: jupyter

Last updated 2026-07-24 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-04-03 23:17 UTCPublished CVE record published
2026-07-24 22:10 UTCUpdated Record last modified

jupyter lti jupyterhub authenticator UPGRADE

Affected: < 1.6.3

Fixed in: 1.6.3

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy lti-jupyterhub-authenticator || rpm -q lti-jupyterhub-authenticator || lti-jupyterhub-authenticator --version

2. UPGRADE to 1.6.3 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade lti-jupyterhub-authenticator

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade lti-jupyterhub-authenticator

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-34052?

lti jupyterhub authenticator: upgrade to 1.6.3. Exact commands for each OS are on this page.

Is CVE-2026-34052 being exploited?

CVE-2026-34052 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-34052 affect?

CVE-2026-34052 affects lti jupyterhub authenticator. Severity is medium (CVSS 5.9). 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

How urgent is CVE-2026-34052?

Priority 32/100. Remotely exploitable, no login, no user action

Software pages

Jupyter vulnerabilities

References

← Back to latest CVEs