File overwrite via unsanitized repository metadata paths
Published Jun 29, 2026 · Updated Jun 29, 2026
Relative path traversal in SUSE libzypp before 17.38.10 allows remote attackers supplying a repository to overwrite system files. The YUM RepomdFileReader and susetags ContentFileReader accept metadata paths containing parent-directory segments and pass locations outside the repository cache to download processing. Exploitation requires the system to consume attacker-supplied repository metadata; chosen-file overwrites can interrupt services or enable privilege escalation.
Summary
What happened
Relative path traversal in SUSE libzypp before 17.38.10 allows remote attackers supplying a repository to overwrite system files. The YUM RepomdFileReader and susetags ContentFileReader accept metadata paths containing parent-directory segments and pass locations outside the repository cache to download processing. Exploitation requires the system to consume attacker-supplied repository metadata; chosen-file overwrites can interrupt services or enable privilege escalation.
The record
- CVE
- CVE-2026-25707
- Published
- Jun 29, 2026
- Updated
- Jun 29, 2026
- Vendor
- NeuVector
- Product
- libzypp
- Classifications
- CWE-23, CAPEC-165, T1195.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 29, 2026CVE publishedPublication date reported by the CVE source.
- Jun 29, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <17.38.10
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo