CVE-2026-25707

libzypp: A relative path traversal bug problem when processing repository metadata in libzypp before 17.38.10 could be used by...

CVE-2026-25707 is fixed in 3 products on 1 platform, first by SUSE-SU-2026:22172-1, released June 19, 2026. It is not reported as exploited. Patch Radar priority: High.

High
CVSS
8.8
high
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0060
48th percentile

A relative path traversal bug problem when processing repository metadata in libzypp before 17.38.10 could be used by remote attackers supplying repositories to overwrite files on the system, leading to denial of service or privilege escalation.

Where it's fixed

ProductFixed inFixReleased
Linux
libsolv · opensuse-leap 16.0 0.7.39-160000.1.1 OPENSUSE-SU-2026:21096-1 Jun 19, 2026
libsolv · sles 15.6 0.7.39-150600.8.24.1 SUSE-SU-2026:2590-1 Jun 23, 2026
libsolv · sles 15.7 0.7.39-150700.11.10.1 SUSE-SU-2026:2531-1 Jun 23, 2026
libsolv · sles 16.0 0.7.39-160000.1.1 SUSE-SU-2026:22172-1 Jun 19, 2026
libzypp · Debian 14 17.38.11-1 DEBIAN-CVE-2026-25707 Jun 30, 2026
libzypp · opensuse-leap 16.0 17.38.13-160000.1.1 OPENSUSE-SU-2026:21096-1 Jun 19, 2026
libzypp · sles 15.6 17.38.13-150600.3.92.1 SUSE-SU-2026:2590-1 Jun 23, 2026
libzypp · sles 15.7 17.38.13-150700.6.13.1 SUSE-SU-2026:2531-1 Jun 23, 2026
libzypp · sles 16.0 17.38.13-160000.1.1 SUSE-SU-2026:22172-1 Jun 19, 2026
zypper · opensuse-leap 16.0 1.14.98-160000.1.1 OPENSUSE-SU-2026:21096-1 Jun 19, 2026
zypper · sles 15.7 1.14.98-150700.13.6.1 SUSE-SU-2026:2531-1 Jun 23, 2026
zypper · sles 16.0 1.14.98-160000.1.1 SUSE-SU-2026:22172-1 Jun 19, 2026

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.