---
id: "CVE-2026-104619"
page: "https://infrastack.ai/live/CVE-2026-104619"
kind: "vulnerability"
aliases: ["CVE-2026-104619"]
title: "PackageKit Zypp backend lets untrusted users roll back security updates"
severity: "high"
cvss: 7.8
epss: null
exploited: false
status: "open"
category: "infrastructure"
products: []
ecosystems: []
tags: ["infrastructure", "linux", "opensuse", "packagekit", "self-hosted", "suse", "zypp"]
not_affected_if: ["no-packagekit", "no-zypp-backend", "trusted-local-users-only"]
published_at: "2026-11-10T10:16:42+00:00"
first_seen_at: "2026-11-10T10:21:12+00:00"
updated_at: "2026-11-10T10:21:29+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-104619", "first_seen_at": "2026-11-10T10:21:12+00:00"}]
exploit_sources: []
---

# PackageKit Zypp backend lets untrusted users roll back security updates

Link for people: https://infrastack.ai/live/CVE-2026-104619 (this .md is for agents)

The PackageKit Zypp backend before 1.4.1 lets untrusted users roll back installed security updates on the system. Rolling back a patched package can reopen a flaw and allow privilege escalation.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed PackageKit Zypp backend version against the fixed release, for example with `rpm -q PackageKit-backend-zypp` or `zypper info PackageKit-backend-zypp`
- Confirm whether PackageKit with the Zypp backend is installed on the machine at all

## Fix

- PackageKit Zypp backend: move to `1.4.1` or later

## Timeline

- 2026-11-10T10:21:12+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-104619

## From the sources

Untrusted users could roll back security updates when using the PackageKit Zypp Backend before 1.4.1, allowing privilege escalation.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_
