nbconvert 7.17.0
PkgFire would install this release with a warning.·Checked 12 hours ago·Published 29 January 2026
Why
-
warnVulnerability
PYSEC-2026-2229 (fixed in 7.17.1)
-
warnVulnerability
PYSEC-2026-2230 (fixed in 7.17.1)
-
warnVulnerability
nbconvert has an Arbitrary File Write via Path Traversal in Cell Attachment Filenames (fixed in 7.17.1)
-
warnVulnerability
nbconvert has an Arbitrary File Read via Path Traversal in HTMLExporter Image Embedding (fixed in 7.17.1)
-
warnVulnerability
nbconvert: Arbitrary file write through path traversal in cell output filenames when exporting to md, latex, rst and asciidoc (fixed in 7.17.2)
Provenance
A registry signature proves the registry served these bytes unaltered. Build provenance proves which workflow built them from which commit; a stolen publishing token can fake the first but not the second.
- Signature
- Not signed
- Build provenance
- None, and no earlier version had any
What the code does
On its own this is weak signal: plenty of honest libraries read files or talk to the network. What PkgFire watches is a release gaining something the one before it did not.
Code reading
PkgFire's own reading of the files: what the code can do.
Source patterns
Patterns found in the source, including those malware is known to use.
Other checked releases
Check every dependency before it installs
This page is one release. PkgFire checks every package in your lockfile, on every install and in every pull request, and blocks the bad ones before they run.