nbconvert: Arbitrary file write through path traversal in cell output filenames when exporting to md, latex, rst and asciidoc

Why it is Amber

• CVSS 8.8 high
• On your watchlist: PyPI

Affected packages

References

• https://github.com/advisories/GHSA-pjvx-prjx-h659
• https://github.com/jupyter/nbconvert/security/advisories/GHSA-pjvx-prjx-h659
• https://nvd.nist.gov/vuln/detail/CVE-2026-114140
• https://github.com/jupyter/nbconvert/commit/ce4bd99aec31d81d759fa8eeb8643179392ec66f
• https://github.com/jupyter/nbconvert/releases/tag/v7.17.2
• https://github.com/advisories/GHSA-pjvx-prjx-h659

Original description

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.