# LTI JupyterHub Authenticator: Unbounded Memory Growth via Nonce Storage (Denial of Service)

Advisory record · `GHSA-8mxq-7xr7-2fxj`

- **Identifiers:** `GHSA-8mxq-7xr7-2fxj` · `CVE-2026-34052` · `PYSEC-2026-2533`
- **State:** Confirmed
- **Severity:** CVSS 5.9 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-401](https://cwe.mitre.org/data/definitions/401.html) · [CWE-770](https://cwe.mitre.org/data/definitions/770.html)
- **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md)
- **Published:** 3 Apr 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 3 Apr 2026, 21:42 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `jupyterhub-ltiauthenticator` (PyPI): affected `<1.6.3`; fixed in `1.6.3`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The jupyterhub-ltiauthenticator package is vulnerable before version 1.6.3. Its LTI 1.1 validator stores OAuth nonces in a dictionary that grows without limit, and nonces are recorded before the signature is checked. An attacker who knows a valid consumer key can send repeated requests with unique nonces, gradually exhausting server memory and causing a denial of service. Upgrade to jupyterhub-ltiauthenticator 1.6.3 or later.

Written 1 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.9 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0034, the 28th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:11 UTC: First seen by agentprime
- 31 Oct 2026, 14:11 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-8mxq-7xr7-2fxj)

## Sources

- [GitHub Advisory Database: GHSA-8mxq-7xr7-2fxj](https://github.com/advisories/GHSA-8mxq-7xr7-2fxj)
- [OSV: GHSA-8mxq-7xr7-2fxj](https://osv.dev/vulnerability/GHSA-8mxq-7xr7-2fxj)
- <https://github.com/jupyterhub/ltiauthenticator/security/advisories/GHSA-8mxq-7xr7-2fxj>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-34052>
- <https://github.com/jupyterhub/ltiauthenticator>
- <https://github.com/jupyterhub/ltiauthenticator/releases/tag/1.6.3>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-8mxq-7xr7-2fxj>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-8mxq-7xr7-2fxj/>. Everything for agents: <https://agentprime.io/llms.txt>.
