CVE-2026-44941 in libzypp
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.
Quick answer
SUSE libzypp should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- libzypp before 17.38.12
Fixed versions
- libzypp 17.38.12 or later
- Install the SUSE libzypp security update for your supported product
How to fix it
CVE-2026-44941 affects libzypp. The issue means a malicious repository may write files as root through path traversal. Treat this as a priority if the system is reachable by users, tenants, or the network. Update to libzypp 17.38.12 or later, or follow the vendor advisory if your branch needs a backport.
- Inventory every libzypp instance, appliance, container, or package in use.
- Compare installed versions with the affected ranges in the vendor advisory.
- Update to libzypp 17.38.12 or later on supported systems.
- If you cannot update today, restrict access to trusted admins and trusted networks only.
- Review logs for unusual access, privilege changes, file access, or failed requests.
- Rotate secrets, tokens, and service accounts if exposure or abuse is suspected.
- Document the change and keep the advisory link with the ticket.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm the installed version is libzypp 17.38.12 or later.
- Confirm exposed admin, API, SFTP, or device access is limited to trusted users.
- Retest the affected workflow after the update or mitigation.
- Review logs again after patching for repeated suspicious activity.
- Run a new Fixnx scan where the affected service is part of the public site.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-44941?
SUSE libzypp versions listed as affected should be reviewed: libzypp before 17.38.12.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.