# CVE-2026-103870: Pulp-rpm: distribution tree publish creates directories from .treeinfo ids

> An attacker with sync or upload permissions can create directories outside the intended work area and write metadata, potentially corrupting the repository structure.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** GHSA-wx3c-cxf8-mpww

## What is CVE-2026-103870?

CVE-2026-103870 is a medium-severity path traversal vulnerability in Red Hat Satellite 6, published on 7 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in pulp-rpm when it publishes a distribution tree. Addon and variant ids from .treeinfo are used as directory names. A user who can sync or upload that tree can make the publish task create a new directory outside the task work area and write that tree's repository metadata and packages there, as the Pulp worker user. An existing file or directory is not replaced. The flaw does not disclose data and does not stop the service.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-103870 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-103870 is a medium-severity path traversal vulnerability in Red Hat Satellite 6, published on 7 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-103870 in the wild and no public exploit code.

Affected product: Red Hat Satellite 6. 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-103870/ (Markdown: https://insights.sbomify.com/CVE-2026-103870/index.md)
```

## Sources

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

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