CVE-2026-25707

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH 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.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 8.8Exploit: NoneExposed: 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(high)
EPSS
44.4%
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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 41× in last 7d / 45× 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.

  1. 2026-07-07 02:37 UTCEG score recompute
  2. 2026-07-07 02:37 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 15:07 UTCEG score recompute
  6. 2026-07-06 15:07 UTCGHSA enrichment
  7. 2026-07-06 03:31 UTCEG score recompute
  8. 2026-07-06 03:30 UTCGHSA enrichment
  9. 2026-07-06 02:23 UTCEPSS rescore
  10. 2026-07-06 02:23 UTCEPSS rescore
  11. 2026-07-05 15:50 UTCEG score recompute
  12. 2026-07-05 15:50 UTCGHSA enrichment
  13. 2026-07-05 04:21 UTCEG score recompute
  14. 2026-07-05 04:21 UTCGHSA enrichment
  15. 2026-07-05 02:30 UTCEPSS rescore
  16. 2026-07-04 16:50 UTCEG score recompute
  17. 2026-07-04 16:50 UTCGHSA enrichment
  18. 2026-07-04 06:31 UTCEPSS rescore
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-04 05:20 UTCEG score recompute
  21. 2026-07-04 05:20 UTCGHSA enrichment
  22. 2026-07-03 17:47 UTCEG score recompute
  23. 2026-07-03 17:47 UTCGHSA enrichment
  24. 2026-07-03 06:18 UTCEG score recompute
  25. 2026-07-03 06:18 UTCGHSA enrichment
Show 20 more
  1. 2026-07-02 18:45 UTCEG score recompute
  2. 2026-07-02 18:45 UTCGHSA enrichment
  3. 2026-07-02 07:16 UTCEG score recompute
  4. 2026-07-02 07:16 UTCGHSA enrichment
  5. 2026-07-01 19:46 UTCEG score recompute
  6. 2026-07-01 19:46 UTCGHSA enrichment
  7. 2026-07-01 15:06 UTCEPSS rescore
  8. 2026-07-01 15:06 UTCEPSS rescore
  9. 2026-07-01 08:17 UTCEG score recompute
  10. 2026-07-01 08:17 UTCGHSA enrichment
  11. 2026-06-30 23:22 UTCEPSS rescore
  12. 2026-06-30 23:22 UTCEPSS rescore
  13. 2026-06-30 20:47 UTCEG score recompute
  14. 2026-06-30 20:47 UTCGHSA enrichment
  15. 2026-06-30 09:17 UTCEG score recompute
  16. 2026-06-30 09:17 UTCGHSA enrichment
  17. 2026-06-29 21:47 UTCEG score recompute
  18. 2026-06-29 21:47 UTCGHSA enrichment
  19. 2026-06-29 10:18 UTCEG score recompute
  20. 2026-06-29 10:17 UTCMITRE cvelistV5first tracked

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 44.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs