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
Trending — 3 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

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%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
47%
KEV
Not listed

Published

June 29, 2026

Last Modified

June 30, 2026

Advisory Details (2)

Auto-updated Jun 29, 2026
Upstream fix merged — awaiting tagged release. 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 rangeFixed inDependents
libzypp17.25.7-1 ... 17.38.9-1 (76 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
libzypp17.25.7-2.4 ... 17.38.9-1 (71 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libzypp17.36.7-1 ... 17.38.9-1 (18 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libzypp17.36.7-1 ... 17.38.9-1 (13 versions)17.38.11-1

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 50× 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 229 total refreshes for this CVE.

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

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 in the National Vulnerability Database 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 1% probability of exploitation in the next 30 days, which ranks it in the top 52.6% of all scored CVEs.
What is the CVSS score of CVE-2026-25707?
CVE-2026-25707 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-25707?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-25707, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.