CVE-2026-86049

Jupyter Server: 5xx request logging leaks token-bearing Referer header values

Published Sep 17, 2026 CVSS 3.1 · 7.1 High EPSS < 1% KEV · Not listed
Description
Jupyter Server is the backend for Jupyter web applications. Prior to version 2.21.0, the 5xx request logging path in jupyter_server/log.py copies the Referer header into a JSON header block without applying the token scrubbing used for the request URI. A request that returns HTTP 500 while the Referer contains a token-bearing URL can therefore write that token to server logs in plaintext. An attacker who can read those logs can recover the token and use the affected user's Jupyter Server permissions. This issue is fixed in version 2.21.0.

Analysis

AI-generated

Technical impact

Back in Jupyter Server releases before 2.21.0, the 5xx request logging routine copied the entire Referer header into a JSON header block without removing any access token present in that URL. When a request that triggers a server error also includes a token-bearing Referer, the plain‑text token is written to the server logs. An individual who can read those logs therefore can recover the token and employ it to access the Jupyter Server with the affected user's permissions.

Affected Systems

The flaw affects the Jupyter Server (jupyter_server) product from any version older than 2.21.0. Any installation that remains on or before the pre‑2.21.0 releases is vulnerable.

Risk and Exploitability

The CVSS score is 7.1, indicating moderate severity, and the EPSS score is below 1%, suggesting a low likelihood of exploitation. The vulnerability is not listed in CISA’s KEV catalog. The likely attack path involves steering the server to produce an HTTP 500 response while an attacker supplies a crafted Referer header containing a token. Crucially, the attacker must also be able to read the server logs, typically restricting practical exploitation to users with privileged or elevated log‑access rights. Consequently, while the risk is moderate, the impact can be significant if log visibility is not tightly controlled.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Jupyter Server to version 2.21.0 or later to apply the official fix.
  • Validate that the revised logging no longer records token-bearing Referer headers by reviewing recent error logs.
  • Limit log file permissions so that only authorized administrators can read server logs, and audit access regularly.

Generated by OpenCVE AI on September 23, 2026 at 01:53 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-c3mw-737p-c7g2 Jupyter Server: 5xx request logging leaks token-bearing Referer header values
History
Type Values Removed Values Added
First Time appeared Jupyter
Jupyter jupyter Server
Vendors & Products Jupyter
Jupyter jupyter Server
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description Jupyter Server is the backend for Jupyter web applications. Prior to version 2.21.0, the 5xx request logging path in jupyter_server/log.py copies the Referer header into a JSON header block without applying the token scrubbing used for the request URI. A request that returns HTTP 500 while the Referer contains a token-bearing URL can therefore write that token to server logs in plaintext. An attacker who can read those logs can recover the token and use the affected user's Jupyter Server permissions. This issue is fixed in version 2.21.0.
Title Jupyter Server: 5xx request logging leaks token-bearing Referer header values
Weaknesses CWE-532
References
Metrics cvssV3_1

{'score': 7.1, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H'}

Weaknesses
  • CWE-117

    Improper Output Neutralization for Logs

  • CWE-532

    Insertion of Sensitive Information into Log File

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Sep 18, 2026, 6:32 PM
Reserved
Sep 4, 2026, 7:29 PM
Status
Awaiting Analysis
Published
Sep 17, 2026, 9:17 PM
Modified
Sep 24, 2026, 9:19 PM
Severity
Moderate
Public date
Sep 17, 2026, 8:28 PM