CVE-2020-26261: JupyterHub-Systemdspawner - User-Readable API Tokens in Systemd Units

jupyterhub-systemdspawner Updated 02 Oct 2025

Summary

09/12/2020
Yes i
High
7.9

CVE-2020-26261: user-readable api tokens in systemd units for JupyterHub. Affects jupyterhub-systemdspawner versions < 0.15.0. Fixed in 0.15.0. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

JupyterHub-Systemdspawner is a package available on PyPI that is commonly used in JupyterHub deployments. It provides a spawner for JupyterHub that uses systemd units to manage single-user servers. Systemd units are used to define and manage system services in Linux distributions. JupyterHub-Systemdspawner allows users to launch and manage their own Jupyter notebook servers within a JupyterHub environment.

Vulnerability Detail

The vulnerability identified as CVE-2020-26261 involves the exposure of user-readable API tokens in systemd units for JupyterHub. These API tokens, which are issued to single-user servers, are specified in the environment of systemd units. Unfortunately, these tokens are accessible to all users on the system, potentially leading to unauthorized access and misuse of the tokens. This vulnerability affects the-littlest-jupyterhub, which utilizes systemdspawner by default. The issue has been assigned a CVSS score of 7.9, indicating a high severity level.

How To Fix

Minimum fixed version

0.15.0

This is the first release that contains the fix.

pip install --upgrade "jupyterhub-systemdspawner==0.15.0"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability other than upgrading to systemdspawner v0.15 or later.

Conclusion

In conclusion, the vulnerability CVE-2020-26261 exposes user-readable API tokens in systemd units for JupyterHub deployments using the-littlest-jupyterhub. To mitigate this vulnerability, it is crucial to upgrade to systemdspawner v0.15 or later. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for jupyterhub-systemdspawner →

Share this vulnerability

FAQ

The vulnerability allows all users on the system to access user-readable API tokens, potentially leading to unauthorized access and misuse of these tokens.

The vulnerability affects jupyterhub-systemdspawner, specifically versions prior to 0.15.

To fix this vulnerability, upgrade systemdspawner to version 0.15 or later.

No, the only known solution is to upgrade to systemdspawner v0.15 or later.

For more information, you can visit the Jupyter forum or contact security@ipython.org.

How To Fix

Minimum fixed version

0.15.0

This is the first release that contains the fix.

pip install --upgrade "jupyterhub-systemdspawner==0.15.0"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback