# CVE-2026-104103: Ludwig: Path traversal in dataset archive extraction allows arbitrary file write via symlink members

> Attackers can write arbitrary files via symlink members in crafted archives, potentially leading to code execution or data modification in Ludwig AI framework.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-qvrm-3x4c-rcxf

## What is CVE-2026-104103?

CVE-2026-104103 is a high-severity path traversal vulnerability in ludwig-ai ludwig, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Ludwig is a low-code framework for building custom LLMs, neural networks, and other AI models. Prior to 0.17.8, ludwig.datasets.archives.extract_archive() validated tar member names before calling TarFile.extractall() but did not validate symlink members or hard-link members. A crafted archive could create a link that escaped the extraction directory and then write a later member through that link, placing attacker-controlled content at an arbitrary filesystem path with the extracting process's privileges. The same containment check used os.path.commonprefix, so a sibling path sharing the destination's character prefix could also pass. The dataset-loading path can download and extract configured archive URLs, but exploitation requires a user to process an archive from a source controlled or compromised by the attacker on supported Python 3.12 and 3.13 runtimes. Python 3.14 is not affected because its default tar data filter rejects escaping links. This issue is fixed in version 0.17.8.

Weakness: CWE-59 (Improper Link Resolution Before File Access), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-104103?


## How do I fix CVE-2026-104103?

No fix has been published for CVE-2026-104103 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-104103 being exploited?

There is no known exploitation of CVE-2026-104103 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-104103 and fix it if it is affected.

What it is: CVE-2026-104103 is a high-severity path traversal vulnerability in ludwig-ai ludwig, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-104103 in the wild and no public exploit code.

Affected product: ludwig-ai ludwig. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-104103/ (Markdown: https://insights.sbomify.com/CVE-2026-104103/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-104103
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-104103
- OSV: https://osv.dev/vulnerability/CVE-2026-104103

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-104103/
Summaries are generated and may contain mistakes; the official description above is the record.