CVE-2026-44941: A relative path traversal in the "keyhint" option in repomd.xml parsing of libzypp before 17.38.12 can be used
CVE-2026-44941 is a high-severity flaw (CVSS 8.4) affecting libzypp. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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.
Why this priority
- High severity
- Public exploit reference
A fixed release or distro patch exists.
Risk facts
| CVSS score | 8.4 (High) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | High |
| User interaction | Required |
| EPSS exploit chance | 0.5% (top 55%) |
| CISA exploited list | No |
| Weakness | CWE-23 |
| Published | 2026-07-02 |
| Last modified | 2026-10-25 |
Last updated 2026-10-25 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2026-44941?
libzypp: upgrade to 17.38.12. Exact commands for each OS are on this page.
Is CVE-2026-44941 being exploited?
CVE-2026-44941 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2026-44941 affect?
CVE-2026-44941 affects libzypp. Severity is high (CVSS 8.4). 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.
How urgent is CVE-2026-44941?
Priority 46/100. High severity; Public exploit reference
Related CVEs
- CVE-2026-25707 HIGH 8.8 UPGRADE A relative path traversal bug problem when processing repository metadata in libzypp before 17.38.10 could be