CVE-2026-25707

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-29. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation1% × 40%
Automatability0% × 15%
EPSS PROB
0.6%
EPSS %ILE
47th
KEV
Not listed

Published

June 29, 2026

Last Modified

June 30, 2026

Advisory Details (2)

Auto-updated Jun 29, 2026
Patch available. Sources: github_commit.
github_commit

commit f09feda7fca0 (openSUSE/libzypp)

Fix landed in openSUSE/libzypp commit f09feda7fca0 — awaiting tagged release

https://github.com/openSUSE/libzypp/commit/f09feda7fca03c941218aab0bb161cc82b185b6b
generic

1259802 – (CVE-2026-25707) VUL-0: CVE-2026-25707: libzypp: Handcrafted repo metadata may cause arbitrary local files to be overwritten.

https://bugzilla.suse.com/show_bug.cgi?id=1259802

Vendor Advisories for CVE-2026-25707(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
libzypp17.25.7-1 ... 17.38.9-1 (76 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
libzypp17.25.7-2.4 ... 17.38.9-1 (73 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
libzypp17.36.7-1 ... 17.38.9-1 (20 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libzypp17.36.7-1 ... 17.38.9-1 (13 versions)
  • every version up to 17.38.11-1: fixed in 17.38.11-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 29× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 245 total refreshes for this CVE.

  1. 2026-10-10 20:00 UTCEPSS rescore
  2. 2026-10-09 20:07 UTCEPSS rescore
  3. 2026-10-08 17:11 UTCEPSS rescore
  4. 2026-10-07 23:47 UTCEPSS rescore
  5. 2026-10-06 15:17 UTCEPSS rescore
  6. 2026-10-05 17:42 UTCEPSS rescore
  7. 2026-10-04 23:21 UTCEPSS rescore
  8. 2026-10-03 14:25 UTCEPSS rescore
  9. 2026-10-01 19:49 UTCEPSS rescore
  10. 2026-09-30 15:03 UTCEPSS rescore
  11. 2026-09-28 13:51 UTCEPSS rescore
  12. 2026-09-26 15:58 UTCEPSS rescore
  13. 2026-09-26 00:26 UTCEPSS rescore
  14. 2026-09-24 14:03 UTCEPSS rescore
  15. 2026-09-23 07:34 UTCEG score recompute
  16. 2026-09-23 07:34 UTCGHSA enrichment
  17. 2026-09-18 19:27 UTCEPSS rescore
  18. 2026-09-18 07:00 UTCEG score recompute
  19. 2026-09-18 07:00 UTCGHSA enrichment
  20. 2026-09-16 14:07 UTCEPSS rescore
  21. 2026-09-16 05:15 UTCEPSS rescore
  22. 2026-09-14 00:53 UTCEG score recompute
  23. 2026-09-14 00:53 UTCGHSA enrichment
  24. 2026-09-13 16:47 UTCEPSS rescore
  25. 2026-09-13 09:26 UTCGHSA enrichment
Show 75 more
  1. 2026-09-12 15:16 UTCEG score recompute
  2. 2026-09-12 15:16 UTCGHSA enrichment
  3. 2026-09-12 15:01 UTCEPSS rescore
  4. 2026-09-11 14:52 UTCEPSS rescore
  5. 2026-09-10 09:34 UTCEPSS rescore
  6. 2026-09-08 22:00 UTCEPSS rescore
  7. 2026-09-07 16:01 UTCEPSS rescore
  8. 2026-09-06 14:45 UTCEG score recompute
  9. 2026-09-06 14:45 UTCGHSA enrichment
  10. 2026-09-06 13:47 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-04 05:06 UTCEPSS rescore
  13. 2026-09-02 14:11 UTCEPSS rescore
  14. 2026-09-01 13:53 UTCEPSS rescore
  15. 2026-09-01 04:39 UTCEPSS rescore
  16. 2026-08-30 19:17 UTCEPSS rescore
  17. 2026-08-30 18:49 UTCEG score recompute
  18. 2026-08-30 18:49 UTCGHSA enrichment
  19. 2026-08-30 01:22 UTCEPSS rescore
  20. 2026-08-28 21:41 UTCEPSS rescore
  21. 2026-08-27 22:48 UTCEG score recompute
  22. 2026-08-27 22:48 UTCGHSA enrichment
  23. 2026-08-27 14:25 UTCEPSS rescore
  24. 2026-08-26 14:46 UTCEPSS rescore
  25. 2026-08-25 13:48 UTCEPSS rescore
  26. 2026-08-25 00:12 UTCEG score recompute
  27. 2026-08-25 00:12 UTCGHSA enrichment
  28. 2026-08-24 12:41 UTCEG score recompute
  29. 2026-08-24 12:41 UTCGHSA enrichment
  30. 2026-08-23 20:00 UTCGHSA enrichment
  31. 2026-08-23 08:30 UTCEG score recompute
  32. 2026-08-23 08:30 UTCGHSA enrichment
  33. 2026-08-23 00:19 UTCEPSS rescore
  34. 2026-08-22 20:56 UTCGHSA enrichment
  35. 2026-08-22 09:06 UTCEG score recompute
  36. 2026-08-22 09:06 UTCGHSA enrichment
  37. 2026-08-21 23:49 UTCEPSS rescore
  38. 2026-08-21 17:23 UTCGHSA enrichment
  39. 2026-08-21 04:54 UTCEG score recompute
  40. 2026-08-21 04:54 UTCGHSA enrichment
  41. 2026-08-20 22:55 UTCEPSS rescore
  42. 2026-08-20 17:23 UTCGHSA enrichment
  43. 2026-08-20 05:52 UTCEG score recompute
  44. 2026-08-20 05:52 UTCGHSA enrichment
  45. 2026-08-19 17:03 UTCEPSS rescore
  46. 2026-08-19 10:56 UTCGHSA enrichment
  47. 2026-08-18 23:21 UTCEG score recompute
  48. 2026-08-18 23:21 UTCGHSA enrichment
  49. 2026-08-18 13:48 UTCEPSS rescore
  50. 2026-08-17 13:47 UTCEPSS rescore
  51. 2026-08-17 07:36 UTCGHSA enrichment
  52. 2026-08-16 20:07 UTCEG score recompute
  53. 2026-08-16 20:07 UTCGHSA enrichment
  54. 2026-08-16 14:56 UTCEPSS rescore
  55. 2026-08-16 08:37 UTCEG score recompute
  56. 2026-08-16 08:37 UTCGHSA enrichment
  57. 2026-08-16 02:14 UTCEPSS rescore
  58. 2026-08-15 21:08 UTCGHSA enrichment
  59. 2026-08-15 09:38 UTCEG score recompute
  60. 2026-08-15 09:38 UTCGHSA enrichment
  61. 2026-08-15 01:30 UTCEPSS rescore
  62. 2026-08-14 22:08 UTCGHSA enrichment
  63. 2026-08-14 10:39 UTCGHSA enrichment
  64. 2026-08-13 23:09 UTCEG score recompute
  65. 2026-08-13 23:09 UTCGHSA enrichment
  66. 2026-08-13 22:00 UTCEPSS rescore
  67. 2026-08-13 11:33 UTCGHSA enrichment
  68. 2026-08-13 00:03 UTCEG score recompute
  69. 2026-08-13 00:03 UTCGHSA enrichment
  70. 2026-08-12 13:50 UTCEPSS rescore
  71. 2026-08-12 12:34 UTCGHSA enrichment
  72. 2026-08-12 01:04 UTCEG score recompute
  73. 2026-08-12 01:04 UTCGHSA enrichment
  74. 2026-08-11 13:42 UTCEPSS rescore
  75. 2026-08-11 13:35 UTCGHSA enrichment

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-25707?
CVE-2026-25707 is a high vulnerability published on June 29, 2026. 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.
When was CVE-2026-25707 disclosed?
CVE-2026-25707 was first published on June 29, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-25707 actively exploited?
CVE-2026-25707 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (47th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-25707?
CVE-2026-25707 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-25707?
A fix for CVE-2026-25707 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-25707 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-25707

Explore →

Is Your Infrastructure Affected by CVE-2026-25707?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs