# SUSE-SU-2026:23507-1: Security update for libzypp, zypper

> Attackers can bypass GPG signature checks on unsigned repositories if previously accepted, allowing installation of malicious packages.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Sep 2026

## What is SUSE-SU-2026:23507-1?

SUSE-SU-2026:23507-1 is a vulnerability in libzypp, published on 8 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).

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.1:

- Prevent libgpgme from launching gpg-agents; we don't need them.
- defaultLoadSystem: Hand out the ZYpp::Ptr as return value.
- Log all solver problem rules (bsc#1277790)
 The log contains the most relevant problem rule, but sometimes it
 helps to know all rules associated with this problem. zypper
 shows them on demand as 'detail'. The log now remembers them as
 well.
- Replace popen cat/zcat with solv_xfopen for testcase loaders
 (fixes #749)
- repoGpgCheck: Strictly follow the repo_gpgcheck setting
 (bsc#1274625)
 There's been a legacy exception for unsigned repositories which
 were explicitly accepted in the past. After switching the
 repo_gpgcheck from off to on, they were allowed to stay unsigned
 until a first signed version was retrieved. From there on the
 handling was strict.
 Now the handling is strict as soon as the repo_gpgcheck turned
 on. The next set of metadata retrieved must be signed.
- Iniparser: each new file starts in the unnamed section
 (bsc#1272534)
- Fix hasCredentials() to require both username AND password to
 be non-empty (bsc#1273242)
 This avoids an unnecessary 2nd 401 response sending just the
 username in case the username but no password is known. Now it
 immediately fetches the credentials from disk if no password is
 known.
- GPG Key hints in repoindex.xml require at least a long id to
 allow auto-import (bsc#1271730)
 The short Id (32bit/8byte) is not considered to be a safe
 identifier for a gpg key. A long id (64bit/16byte) or even better
 the full fingerprint is needed to identify the key.
- zypp: Improve Testcase Loading for MCP Tools.

Changes for zypper:

Update to version 1.14.99:

- Show solver problem details per default in not-interactive mode
 (bsc#1277790)
 This way they see all details when capturing zypper's output
 because the (d)etail button can't be pressed in not-interactive
 mode.
- Add --servicesd-dir global option to relocate
 /etc/zypp/services.d (bsc#1257249)
- info: check for missing positional args before systemSetup
 (bsc#1274091)
- Remove deprecated installRecommends option from zypper.conf.
 The system wide default for all libzypp based applications is
 defined in zypp.conf(5). It is not recommended to define this in
 zypper exclusively.

## Which versions are affected by SUSE-SU-2026:23507-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libzypp` | SUSE:Linux Micro 6.2 | All versions | 17.38.15-160000.1.1 |
| `zypper` | SUSE:Linux Micro 6.2 | All versions | 1.14.101-160000.1.1 |

## How do I fix SUSE-SU-2026:23507-1?

Apply the vendor's patch.

## Is SUSE-SU-2026:23507-1 being exploited?

There is no known exploitation of SUSE-SU-2026:23507-1 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for SUSE-SU-2026:23507-1 and fix it if it is affected.

What it is: SUSE-SU-2026:23507-1 is a vulnerability in libzypp, published on 8 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:23507-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-23507-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2026-23507-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2026:23507-1

---
From sbomify Insights: https://insights.sbomify.com/SUSE-SU-2026-23507-1/
Summaries are generated and may contain mistakes; the official description above is the record.