PackageKit/ZYpp local privilege escalation using InstallFiles(SIMULATE)
- Exploited
- No known exploitation
- Fix
- Fixed in 1.4.1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 1.4.1.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 10/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
A local attacker with low-privileged access to a system running PackageKit with the Zypp backend can exploit a path traversal flaw in its simulated install action (InstallFiles with SIMULATE) to gain full root privileges. No user interaction is needed to carry out the attack.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
A path traversal attack in simulation of actions in the Zypp backend of PackageKit before 1.4.1 could be used by local attackers to gain root privileges.
cve.now Index
- Exploitation0/40No signal
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.5/10CVSS 8.5, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 32 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 1.4.1.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- PackageKit
fixed in 1.4.1
Evidence 1
- Report
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-104620
Is CVE-2026-104620 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-104620?
PackageKit: before 1.4.1.Source: cve.now feed data
How do I fix CVE-2026-104620?
Upgrade to a fixed version: 1.4.1.Source: cve.now feed data