CVE-2026-54528: CWE-178: Improper Handling of Case Sensitivity in jupyterlab jupyterlab-git
JupyterLab Git versions prior to 0.54.0 contain a vulnerability where the extension improperly handles case sensitivity when enforcing excluded paths. This allows an authenticated user on a case-insensitive filesystem to bypass path exclusions by varying URL path casing and access directories that should be excluded. The issue is fixed in version 0.54.0.
AI Analysis
Technical Summary
The vulnerability in jupyterlab-git before version 0.54.0 arises from the use of fnmatch.fnmatchcase() in GitHandler.prepare() to enforce excluded_paths. On case-insensitive filesystems, this improper handling of case sensitivity allows an authenticated user to manipulate URL path casing to read directories that are intended to be excluded. This is classified as CWE-178 (Improper Handling of Case Sensitivity). The vulnerability has a CVSS 3.1 base score of 7.1, indicating high severity, with network attack vector, low attack complexity, requiring low privileges, no user interaction, unchanged scope, high confidentiality impact, low integrity impact, and no availability impact. The issue is resolved in jupyterlab-git version 0.54.0.
Potential Impact
An authenticated user on a case-insensitive filesystem can bypass excluded path restrictions by varying URL path casing, potentially gaining unauthorized read access to directories that should be excluded. This results in a high confidentiality impact, with limited integrity impact and no availability impact.
Mitigation Recommendations
Upgrade jupyterlab-git to version 0.54.0 or later, where this issue is fixed. Patch status is confirmed by the vendor's versioning information. No other mitigation is indicated.
CVE-2026-54528: CWE-178: Improper Handling of Case Sensitivity in jupyterlab jupyterlab-git
Description
JupyterLab Git versions prior to 0.54.0 contain a vulnerability where the extension improperly handles case sensitivity when enforcing excluded paths. This allows an authenticated user on a case-insensitive filesystem to bypass path exclusions by varying URL path casing and access directories that should be excluded. The issue is fixed in version 0.54.0.
CVSS v3.1
Score 7.1high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in jupyterlab-git before version 0.54.0 arises from the use of fnmatch.fnmatchcase() in GitHandler.prepare() to enforce excluded_paths. On case-insensitive filesystems, this improper handling of case sensitivity allows an authenticated user to manipulate URL path casing to read directories that are intended to be excluded. This is classified as CWE-178 (Improper Handling of Case Sensitivity). The vulnerability has a CVSS 3.1 base score of 7.1, indicating high severity, with network attack vector, low attack complexity, requiring low privileges, no user interaction, unchanged scope, high confidentiality impact, low integrity impact, and no availability impact. The issue is resolved in jupyterlab-git version 0.54.0.
Potential Impact
An authenticated user on a case-insensitive filesystem can bypass excluded path restrictions by varying URL path casing, potentially gaining unauthorized read access to directories that should be excluded. This results in a high confidentiality impact, with limited integrity impact and no availability impact.
Mitigation Recommendations
Upgrade jupyterlab-git to version 0.54.0 or later, where this issue is fixed. Patch status is confirmed by the vendor's versioning information. No other mitigation is indicated.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-15T18:40:01.651Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a4ebdf5c9d9e3dbe3bf8b05
Added to database: 07/08/2026, 21:15:33 UTC
Last enriched: 07/08/2026, 21:28:27 UTC
Last updated: 07/08/2026, 21:28:27 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.