Jupyter nbconvert
nbconvert: File write via path traversal in cell output filenames
The nbconvert tool, jupyter nbconvert, converts Jupyter notebooks to various other formats via Jinja templates. From 5.4.0 until 7.17.2, ExtractOutputPreprocessor in nbconvert/preprocessors/extractoutput.py joins the attacker-controlled cell output metadata filename to output_files_dir without limiting the result to the intended directory. When a victim converts a malicious notebook with the markdown, LaTeX, reStructuredText, or AsciiDoc exporter, path traversal in the output filename can write attacker-controlled output data to arbitrary locations accessible to the victim. Running the notebook cell again replaces the malicious output metadata, but merely converting the supplied notebook does not. This issue is fixed in version 7.17.2.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 5.4.0, < 7.17.2
Fixed in 7.17.2
Mitigation
Upgrade nbconvert to 7.17.2 or later.
References
- Vendor advisory github.com/jupyter/nbconvert/security/advisori…
- Patch github.com/jupyter/nbconvert/commit/ce4bd99aec…
- Release notes github.com/jupyter/nbconvert/releases/tag/v7.1…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.1 pending
Pending 1
| Repository | Created | Found by us | Stars | Assessment |
|---|---|---|---|---|
| federiconbaez/cortex9-nbconvert-output-filename-traversal-model | 9 Nov 2026 +19 d | 14 Nov 2026 | 0 | Pending
Flags · score 15
Below the suspicion threshold (50); does not change the assessment. |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.