jupyterlab-git-10825

Ecosystem: npm

Downloads: 2.25 K

Vulnerabilities from the last (months)
  • 0CriticalAffects 0 versions
  • 1HighAffects 1 version
  • 0MediumAffects 0 versions
  • 0ModerateAffects 0 versions
  • 0LowAffects 0 versions
Severity distribution (all time)
1vulnerability
  • Critical0 (0.0%)
  • High1 (100.0%)
  • Medium0 (0.0%)
  • Moderate0 (0.0%)
  • Low0 (0.0%)

Monthly breakdown

  • 1 vulnerabilities
    • Critical: 0
    • High: 1
    • Medium: 0
    • Moderate: 0
    • Low: 0

Vulnerabilities (1)

Known vulnerabilities affecting jupyterlab-git-10825, based on data from OSV.

Vulnerabilities affecting jupyterlab-git-10825
IDSeveritySummaryAffected versionsPublishedSource
GHSA-f962-v9hr-pfg5Highjupyterlab-git extension: Stored XSS leading to RCEOverview Amazon Web Services (AWS) Security has identified a stored cross-site scripting (XSS) issue in the jupyterlab-git JupyterLab extension that can lead to remote code execution (RCE). The issue exists in the PlainTextDiff.ts component, where the createHeader() method passes Git filenames directly to innerHTML without sanitization when rendering diffs for renamed files in commit history. This allows an adversary to craft a filename containing arbitrary HTML/JavaScript that executes when another user views the rename diff in the Git History tab. The issue can be leveraged through the ren
  • >= 0.30.0-beta.3, < 0.54.0
GitHub (opens in a new tab)
  • GHSA-f962-v9hr-pfg5High
    jupyterlab-git extension: Stored XSS leading to RCE
    • >= 0.30.0-beta.3, < 0.54.0

    Overview Amazon Web Services (AWS) Security has identified a stored cross-site scripting (XSS) issue in the jupyterlab-git JupyterLab extension that can lead to remote code execution (RCE). The issue exists in the PlainTextDiff.ts component, where the createHeader() method passes Git filenames directly to innerHTML without sanitization when rendering diffs for renamed files in commit history. This allows an adversary to craft a filename containing arbitrary HTML/JavaScript that executes when another user views the rename diff in the Git History tab. The issue can be leveraged through the ren

    CVE: CVE-2026-54527

Showing 1-1 of 1 vulnerabilities