# CVE-2026-44942: libzypp .repo files can have an optional path which can lead to path traversal attacks

> Attackers can exploit path traversal in libzypp .repo files to write content to arbitrary directories outside the cache.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Jun 2026
- **Updated:** 18 Jun 2026
- **Also known as:** DEBIAN-CVE-2026-44942, GHSA-m2f8-w9q8-gvj5, SUSE-SU-2026:22064-1, UBUNTU-CVE-2026-44942

## What is CVE-2026-44942?

CVE-2026-44942 is a medium-severity path traversal vulnerability in SUSE libzypp, published on 18 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A path traversal in handling the "path" component of .repo files processed by libzypp before 17.38.13 in the 17.x series, or before 16.22.19 could be used by attackers to fill directories on the system outside of the zypp cache with content.

Weakness: CWE-24 (Path Traversal: '../filedir')

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libzypp` | SUSE:Linux Micro 6.0 | All versions | 17.38.13-1.1 |

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

Upgrade to a fixed version.

## Is CVE-2026-44942 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44942 is a medium-severity path traversal vulnerability in SUSE libzypp, published on 18 Jun 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-44942 in the wild and no public exploit code.

Affected product: SUSE libzypp. 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-44942/ (Markdown: https://insights.sbomify.com/CVE-2026-44942/index.md)
```

## Sources

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

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