# CVE-2026-44933: Path Traversal in Plugin Loading in libzypp

> Attackers can exploit path traversal in libzypp plugin loading to execute arbitrary host binaries with root privileges when chroot is ineffective.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 20 May 2026
- **Updated:** 21 May 2026
- **Also known as:** GHSA-w74x-gjhj-gxwp, SUSE-SU-2026:21738-1, SUSE-SU-2026:21786-1, UBUNTU-CVE-2026-44933, openSUSE-SU-2026:10826-1

## What is CVE-2026-44933?

CVE-2026-44933 is a high-severity path traversal vulnerability in SUSE Linux Enterprise, published on 20 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

`PluginScript` attempts to `chroot` the plugin to the `repoManagerRoot`, this root is frequently `/` (the system root) in standard configurations or when using `--root`. If the chroot target is `/`, it is a no-op, allowing the traversed path to execute host binaries (like `/bin/bash`) with root privileges.

Weakness: CWE-35 (Path Traversal: '.../...//')

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libzypp` | openSUSE:Tumbleweed | All versions | 17.38.9-1.1 |

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

Apply the vendor's patch.

## Is CVE-2026-44933 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44933 is a high-severity path traversal vulnerability in SUSE Linux Enterprise, published on 20 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-44933 in the wild and no public exploit code.

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

## Sources

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

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