Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
HIGH severity

user-readable api tokens in systemd units for JupyterHubGHSA-cg54-gpgr-4rm6

HIGHFix: jupyterhub/systemdspawner@a4d08fd

GHSA-cg54-gpgr-4rm6 is a high-severity (CVSS 7.9) CWE-668 vulnerability in jupyterhub-systemdspawner. A fix is available for jupyterhub-systemdspawner — see the affected versions and patch details below.

Also known asCVE-2020-26261PYSEC-2020-52
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs40th percentile — riskier than 40% of all scored CVEsHighest risk
0.00%0.33%0.65%0.98%0.2%0.5%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-cg54-gpgr-4rm6 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected
🐍jupyterhub-systemdspawner

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Impact

user API tokens issued to single-user servers are specified in the environment of systemd units, which are accessible to all users.

In particular, the-littlest-jupyterhub is affected, which uses systemdspawner by default.

Patches

Patched in jupyterhub-systemdspawner v0.15

Workarounds

No workaround other than upgrading systemdspawner to 0.15

For more information

If you have any questions or comments about this advisory:

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIjupyterhub-systemdspawnerall versions0.15.0pip install --upgrade 'jupyterhub-systemdspawner==0.15.0'

Affected Products

1 product · 1 configurations
Application
systemdspawnerjupyterhub
< 0.15
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for jupyterhub-systemdspawner, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update jupyterhub-systemdspawner to 0.15.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cg54-gpgr-4rm6 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact user API tokens issued to single-user servers are specified in the environment of systemd units, which are accessible to all users. In particular, the-littlest-jupyterhub is affected, which uses systemdspawner by default. ### Patches Patched in jupyterhub-systemdspawner v0.15 ### Workarounds No workaround other than upgrading systemdspawner to 0.15 ### For more information If you have any questions or comments about this advisory: * Open a thread in [the Jupyter forum](https://discourse.jupyter.org) * Email us at [[email protected]](mailto:[email protected])
O3 Security · Impact-Aware SCA

Is GHSA-cg54-gpgr-4rm6 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works
user-readable api tokens in systemd units for JupyterHub