Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

BIT-jupyterlab-2026-42557: jupyterlab: Command linker attributes in HTML enable one-click command execution from untrusted content

0
High
Published: 05/15/2026 (05/15/2026, 08:42:30 UTC)
Source: GCVE Database
Product: jupyterlab

Description

JupyterLab versions prior to 4.5.7 contain a vulnerability where HTML sanitizer allowlists certain command linker attributes on button elements. This allows a notebook with a pre-saved HTML cell output containing a deceptive button to trigger arbitrary JupyterLab commands, including arbitrary code execution, on a single user click without explicit code submission. The issue is fixed in version 4.5.7.

Affected software

Bitnamimore threats →ghsa
jupyterlab
pkg:bitnami/jupyterlab
Affected versions
<4.5.7

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 07/06/2026, 23:06:57 UTC

Technical Analysis

JupyterLab's HTML sanitizer prior to version 4.5.7 permits data-commandlinker-command and data-commandlinker-args attributes on button elements. The CommandLinker component listens for all click events on the document body and executes the named command without verifying if the element originated from trusted JupyterLab UI. This flaw enables an attacker to embed a deceptive button in notebook HTML output that, when clicked by a user, can execute arbitrary JupyterLab commands, potentially leading to arbitrary code execution. The vulnerability is resolved in JupyterLab 4.5.7.

Potential Impact

An attacker can craft a notebook with malicious HTML output containing a button that executes arbitrary commands in JupyterLab when clicked by a user. This can lead to arbitrary code execution without the user explicitly submitting code for execution, posing a high security risk to users running vulnerable versions.

Mitigation Recommendations

This vulnerability is fixed in JupyterLab version 4.5.7. Users should upgrade to version 4.5.7 or later to remediate this issue. No additional mitigations are indicated by the vendor advisory.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
BIT-jupyterlab-2026-42557
Osv Schema Version
1.6.2
Aliases
["CVE-2026-42557"]
Ecosystems
["Bitnami"]
Database Specific Severity
High
Cvss Version
null

Threat ID: 6a4c347627e9c79719603fe0

Added to database: 07/06/2026, 23:04:22 UTC

Last enriched: 07/06/2026, 23:06:57 UTC

Last updated: 07/06/2026, 23:08:36 UTC

Views: 2

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

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

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses