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

> Attackers can bypass GPG signature checks and credential validation in SUSE's libzypp and zypper package managers, potentially installing 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:** 11 Sep 2026

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

SUSE-SU-2026:4129-1 is a vulnerability in libzypp, published on 11 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).
- libzypp: X-ZYpp-AnonymousId header anomaly (bsc#1268321).
- 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).
- dependency issue for package 'python3-vsts-cd-manager' after starting the upgrade (bsc#1261038).

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)
  - zypp.conf: add solver.NoUpdateProvide (default: false) option.

Changes for zypper:

- Update to version 1.14.101.

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libzypp` | SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | All versions | 17.38.15-150500.6.77.1 |
| `zypper` | SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | All versions | 1.14.101-150500.6.48.1 |
| `libzypp` | SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS | All versions | 17.38.15-150500.6.77.1 |
| `zypper` | SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS | All versions | 1.14.101-150500.6.48.1 |
| `libzypp` | SUSE:Linux Enterprise Installer Updates 15 SP5 | All versions | 17.38.15-150500.6.77.1 |
| `libzypp` | SUSE:Linux Enterprise Micro 5.5 | All versions | 17.38.15-150500.6.77.1 |
| `zypper` | SUSE:Linux Enterprise Micro 5.5 | All versions | 1.14.101-150500.6.48.1 |
| `libzypp` | SUSE:Linux Enterprise Server 15 SP5-LTSS | All versions | 17.38.15-150500.6.77.1 |
| `zypper` | SUSE:Linux Enterprise Server 15 SP5-LTSS | All versions | 1.14.101-150500.6.48.1 |
| `libzypp` | SUSE:Linux Enterprise Server for SAP Applications 15 SP5 | All versions | 17.38.15-150500.6.77.1 |
| `zypper` | SUSE:Linux Enterprise Server for SAP Applications 15 SP5 | All versions | 1.14.101-150500.6.48.1 |

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

Upgrade to a fixed version.

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

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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