# CVE-2025-53880: susemanager-tftpsync-recv allows arbitrary file creation and deletion due to path traversal

> Remote attackers on adjacent networks can create or delete arbitrary files via path traversal in SUSE Manager Proxy tftpsync scripts.

- **Severity:** High 8.7 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/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:** Not needed
- **Fix available:** Yes
- **Published:** 30 Oct 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-p9pj-xp4g-3h2q

## What is CVE-2025-53880?

CVE-2025-53880 is a high-severity path traversal vulnerability in Container suse/manager/4.3/proxy-httpd:latest, published on 30 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A Path Traversal vulnerability in the tftpsync/add and tftpsync/delete scripts allows a remote attacker on an adjacent network to write or delete files on the filesystem with the privileges of the unprivileged wwwrun user. Although the endpoint is unauthenticated, access is restricted to a list of allowed IP addresses.

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

## Which versions are affected by CVE-2025-53880?


## How do I fix CVE-2025-53880?

Apply the vendor's patch.

## Is CVE-2025-53880 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-53880 and fix it if it is affected.

What it is: CVE-2025-53880 is a high-severity path traversal vulnerability in Container suse/manager/4.3/proxy-httpd:latest, published on 30 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-53880 in the wild and no public exploit code.

Affected product: Container suse/manager/4.3/proxy-httpd:latest. 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-2025-53880/ (Markdown: https://insights.sbomify.com/CVE-2025-53880/index.md)
```

## Sources

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

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