Skip to main content
VulnerabilityPublished Updated

CVE-2026-126347: Tornado · Open redirect via triple-slash redirect paths

Affects jupyterlabSource GCVE Database

0
Compare

Mentioned vulnerabilities

Authoritative record:CVE-2026-126347· Low 3.1

Not known to be exploited · CVSS 3.1 Low : upgrade to 4.6.6_1 when convenient.

Data as of 18 Nov 2026, 19:24 UTC

CVSS 3.1 base score
3.1Low
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.13.1
Patch
Available – fixed in 4.6.6_1
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 17 Nov 2026.

What to do

Upgrade jupyterlab to 4.6.6_1.

Affected software

ProductAffectedFixed in
Homebrewjupyterlabpkg:brew/jupyterlabOther threatsAffected
  • >=1.2.0 <4.6.6_1
Fixed in
  • 4.6.6_1

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

AI-suggested

A patch is available and included in version 4.6.6_1 of the affected product. Users should upgrade to version 4.6.6_1 or later to remediate this vulnerability. No additional mitigation steps are indicated by the vendor advisory.

Description

Tornado versions from 1.2.0 up to but not including 4.6.6_1 contain an open redirect vulnerability due to inconsistent URL parsing between browsers and Python's urllib. This allows specially crafted URLs with triple-slash redirect paths to bypass previous redirect protections. The issue was addressed in version 4.6.6_1, which improves detection and fixes a regression introduced in the prior fix.

References

Community reviews

Loading reviews…