Skip to main content
VulnerabilityPublished Updated

CVE-2025-59842: JupyterLab LaTeX typesetter links did not enforce `noopener` attribute

Affects jupyterlabSource GCVE Database

0

Not known to be exploited : upgrade to 4.4.8 when convenient.

Data as of 26 Oct 2026, 14:05 UTC

Severity
Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS
0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.4.8

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade jupyterlab to 4.4.8.

Affected software

ProductAffectedFixed in
Bitnamijupyterlabpkg:bitnami/jupyterlabOther threatsAffected
  • <4.4.8
Fixed in
  • 4.4.8

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade JupyterLab to version 4.4.8 or later, where the issue is patched by enforcing the noopener attribute on LaTeX-generated links. No additional mitigation is required for default installations or in the absence of vulnerable third-party extensions.

Description

JupyterLab versions prior to 4.4.8 did not enforce the noopener attribute on links generated by LaTeX typesetters in Markdown files and cells. This could theoretically allow reverse tabnabbing attacks if third-party LaTeX-rendering extensions generated links with target=_blank, although no such extensions are currently known. The issue has been fixed in version 4.4.8.

References

Community reviews

Loading reviews…