CVE-2026-44941

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 57% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
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 in the "keyhint" option in repomd.xml parsing of libzypp before 17.38.12 can be used by attackers able to supply a malicious repository to inject or overwrite files in the target system as root.

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
43%
KEV
Not listed

Published

July 2, 2026

Last Modified

July 7, 2026

Advisory Details (2)

Auto-updated Jul 2, 2026
🔬 Proof of concept available. Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic🟡 PoC Available

1267426 – (CVE-2026-44941) VUL-0: CVE-2026-44941: libzypp: path traversal via "keyhint"

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

commit 294b1bad442d (openSUSE/libzypp)

Fix landed in openSUSE/libzypp commit 294b1bad442d — awaiting tagged release

https://github.com/openSUSE/libzypp/commit/294b1bad442d089ca671c5c03adc8031e3b29e04

Vendor Advisories for CVE-2026-44941(1)

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

Affected Packages

(2 across 2 ecosystems)
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 (14 versions)17.38.12-1

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 24× in last 7d / 105× 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 167 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-44941?
CVE-2026-44941 is a high vulnerability published on July 2, 2026. A relative path traversal in the "keyhint" option in repomd.xml parsing of libzypp before 17.38.12 can be used by attackers able to supply a malicious repository to inject or overwrite files in the target system as root.
When was CVE-2026-44941 disclosed?
CVE-2026-44941 was first published in the National Vulnerability Database on July 2, 2026, with the most recent update on July 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44941 actively exploited?
CVE-2026-44941 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 57.2% of all scored CVEs.
What is the CVSS score of CVE-2026-44941?
CVE-2026-44941 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-44941?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44941, 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-44941

Explore →

Is Your Infrastructure Affected by CVE-2026-44941?

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