SUSE-SU-2026:23547-1 Security update for libzypp, zypper
Not scored
Published
Check this codebase for SUSE-SU-2026:23547-1 and fix it if it is affected.
What it is: SUSE-SU-2026:23547-1 is a vulnerability in libzypp, published on 9 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of SUSE-SU-2026:23547-1 in the wild and no public exploit code.
Affected product: libzypp. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/SUSE-SU-2026-23547-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2026-23547-1/index.md)
Attackers can bypass GPG signature verification and credential checks in SUSE package managers, potentially installing malicious packages.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is SUSE-SU-2026:23547-1?
SUSE-SU-2026:23547-1 is a vulnerability in libzypp, published on 9 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
This update for libzypp, zypper fixes the following issues:
Security issue fixed:
- invalidating legacy libzypp unsigned-repository cache state [LIBZYPP-LEGACY-CACHE-01] (bsc#1274625).
- hasCredentials() requires both username AND password to be non-empty (bsc#1273242).
- GPG Key hints in repoindex.xml require at least a long id to allow auto-import (bsc#1271730).
Non security issues fixed:
- Econf parser adds tags in drop-in files outside any section to [main] (bsc#1272534).
- Need zypper option to disable services to fix Dockerfile builds in OBS (bsc#1257249).
- zypper loads repository data and installed packages prior to checking for required arguments (bsc#1274091).
- Zypper patch doesn't give enough details about conflicts (bsc#1277790).
Changes for libzypp:
Update to version 17.38.15:
- Prevent libgpgme from launching gpg-agents; we don't need them.
- defaultLoadSystem: Hand out the ZYpp::Ptr as return value.
- Replace popen cat/zcat with solv_xfopen for testcase loaders (fixes #749)
- zypp: Improve Testcase Loading for MCP Tools.
- spec: Remove useless %bcond visibility_hidden (is always ON in cmake)
Changes for zypper:
- Update to version 1.14.101.
Which versions are affected by SUSE-SU-2026:23547-1?
Linux distribution packages (2)
libzypp SUSE:Linux Micro 6.0 | All versions | 17.38.15-1.1 |
zypper SUSE:Linux Micro 6.0 | All versions | 1.14.101-1.1 |
How do I fix SUSE-SU-2026:23547-1?
Upgrade to a fixed version.
Is SUSE-SU-2026:23547-1 being exploited?
There is no known exploitation of SUSE-SU-2026:23547-1 in the wild and no public exploit code.