CVE-2026-54528: JupyterLab Git is a Git extension for JupyterLab

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

jupyterlab-git: upgrade to 0.54.0. Exact commands for each OS are on this page.

Q: Is CVE-2026-54528 being exploited?

CVE-2026-54528 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-54528 affect?

CVE-2026-54528 affects jupyterlab-git. Severity is high (CVSS 7.1). JupyterLab Git is a Git extension for JupyterLab. Prior to 0.54.0, jupyterlab-git uses fnmatch.fnmatchcase() in GitHandler.prepare() in jupyterlab_git/handlers.py to enforce excluded_paths, allowing an authenticated user on a case-insensiti

Q: How urgent is CVE-2026-54528?

Priority 39/100. High severity; Public exploit reference

Routine

HIGH 7.1UPGRADE

CVE-2026-54528 is a high-severity flaw (CVSS 7.1) affecting jupyterlab-git. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

JupyterLab Git is a Git extension for JupyterLab. Prior to 0.54.0, jupyterlab-git uses fnmatch.fnmatchcase() in GitHandler.prepare() in jupyterlab_git/handlers.py to enforce excluded_paths, allowing an authenticated user on a case-insensitive filesystem to vary URL path casing and read excluded directories. This issue is fixed in version 0.54.0.

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	7.1 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.4% (top 65%)
CISA exploited list	No
Weakness	CWE-178
Published	2026-07-08
Last modified	2026-10-25

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

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

Am I affected?

Timeline

2026-07-08 21:16 UTCPublished CVE record published
2026-10-25 17:10 UTCUpdated Record last modified

jupyter jupyterlab-git UPGRADE

Affected: < 0.54.0

Fixed in: 0.54.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy jupyterlab-git || rpm -q jupyterlab-git || jupyterlab-git --version

2. UPGRADE to 0.54.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade jupyterlab-git

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade jupyterlab-git

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-54528?

jupyterlab-git: upgrade to 0.54.0. Exact commands for each OS are on this page.

Is CVE-2026-54528 being exploited?

CVE-2026-54528 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-54528 affect?

CVE-2026-54528 affects jupyterlab-git. Severity is high (CVSS 7.1). JupyterLab Git is a Git extension for JupyterLab. Prior to 0.54.0, jupyterlab-git uses fnmatch.fnmatchcase() in GitHandler.prepare() in jupyterlab_git/handlers.py to enforce excluded_paths, allowing an authenticated user on a case-insensiti

How urgent is CVE-2026-54528?

Priority 39/100. High severity; Public exploit reference

Software pages

Git vulnerabilities · Jupyter vulnerabilities

Related CVEs

CVE-2026-54527 CRITICAL 9.0 UPGRADE JupyterLab Git is a Git extension for JupyterLab

References

← Back to latest CVEs