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 58% 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.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 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
41.8%
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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 51× 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-23 14:18 UTCEPSS rescore
  2. 2026-07-23 03:15 UTCEG score recompute 0.40
  3. 2026-07-22 14:08 UTCEPSS rescore
  4. 2026-07-21 15:24 UTCEPSS rescore
  5. 2026-07-20 17:08 UTCEPSS rescore
  6. 2026-07-19 14:31 UTCEPSS rescore
  7. 2026-07-19 02:29 UTCEPSS rescore
  8. 2026-07-18 10:04 UTCEPSS rescore
  9. 2026-07-17 00:47 UTCGHSA enrichment
  10. 2026-07-16 17:03 UTCEPSS rescore
  11. 2026-07-16 11:36 UTCGHSA enrichment
  12. 2026-07-15 22:24 UTCGHSA enrichment
  13. 2026-07-15 16:57 UTCEPSS rescore
  14. 2026-07-15 09:11 UTCGHSA enrichment
  15. 2026-07-15 02:00 UTCEPSS rescore
  16. 2026-07-14 19:57 UTCGHSA enrichment
  17. 2026-07-14 06:45 UTCGHSA enrichment
  18. 2026-07-13 22:30 UTCEPSS rescore
  19. 2026-07-13 17:26 UTCGHSA enrichment
  20. 2026-07-13 06:13 UTCEPSS rescore
  21. 2026-07-13 04:13 UTCGHSA enrichment
  22. 2026-07-12 14:59 UTCGHSA enrichment
  23. 2026-07-12 05:46 UTCEPSS rescore
  24. 2026-07-12 01:46 UTCGHSA enrichment
  25. 2026-07-11 12:34 UTCGHSA enrichment
Show 26 more
  1. 2026-07-11 08:27 UTCEPSS rescore
  2. 2026-07-10 23:21 UTCGHSA enrichment
  3. 2026-07-10 10:09 UTCGHSA enrichment
  4. 2026-07-09 20:55 UTCGHSA enrichment
  5. 2026-07-09 19:10 UTCEPSS rescore
  6. 2026-07-09 07:43 UTCGHSA enrichment
  7. 2026-07-08 18:31 UTCGHSA enrichment
  8. 2026-07-08 15:16 UTCEPSS rescore
  9. 2026-07-08 05:18 UTCGHSA enrichment
  10. 2026-07-07 18:13 UTCNVD updateCVSS v3 → 8.8
  11. 2026-07-07 16:04 UTCGHSA enrichment
  12. 2026-07-07 13:46 UTCEPSS rescore
  13. 2026-07-07 02:48 UTCGHSA enrichment
  14. 2026-07-06 16:27 UTCEPSS rescore
  15. 2026-07-06 13:35 UTCGHSA enrichment
  16. 2026-07-06 02:23 UTCEPSS rescore
  17. 2026-07-06 00:20 UTCGHSA enrichment
  18. 2026-07-05 11:08 UTCGHSA enrichment
  19. 2026-07-05 02:30 UTCEPSS rescore
  20. 2026-07-04 21:55 UTCGHSA enrichment
  21. 2026-07-04 08:43 UTCGHSA enrichment
  22. 2026-07-04 06:31 UTCEPSS rescore
  23. 2026-07-03 19:30 UTCGHSA enrichment
  24. 2026-07-03 06:18 UTCGHSA enrichment
  25. 2026-07-02 16:59 UTCEG score recompute
  26. 2026-07-02 16:58 UTCNVD updatefirst tracked

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

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