GPU VulnDB

Database/AI/ML frameworks & serving

nbconvert: notebook output metadata filename escapes output_files_dir, writing files anywhere the converter can reach

CVSS 8.8CVE-2026-114140AI/ML frameworks & servingcurated

Impact

ExtractOutputPreprocessor joins the cell output metadata filename - which comes from the notebook file, not from the operator - to output_files_dir without confining the result to that directory. Converting an untrusted notebook with the markdown, LaTeX, reStructuredText or AsciiDoc exporter can therefore write attacker-chosen bytes to any path the converting user can write. This matters where nbconvert runs unattended on shared infrastructure: report pipelines, CI jobs and documentation builds that convert user-submitted notebooks can have files planted in a home directory, a job script path or a config location, which is a route to code execution the next time something reads what was written. Simply converting the notebook is enough; the malicious output metadata is only cleared if the cell is executed again. Affects 5.4.0 up to 7.17.2.

Who can reach it

Anyone who can get a notebook file in front of a conversion step - a repository contributor, a user uploading to a report service, or a job submitter in a shared cluster. No authentication to nbconvert itself; it needs a victim or an automated pipeline to run the conversion.

What to do

Upgrade nbconvert to 7.17.2 and redeploy any image or environment that pins it, then restart the pipelines or services that invoke it. No node drain or reboot. Until then, run conversions of untrusted notebooks under an unprivileged account in a disposable container rather than in CI workspaces or user home directories.

References

Related entries

All AI/ML frameworks & serving entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.