Skip to main content

PackageKit CVE-2026-10294

| EUVDEUVD-2026-33818 LOW
Improper Authorization (CWE-285)
2026-06-01 VulDB GHSA-9m6p-w8rp-5v54
2.1
CVSS 4.0 · Vendor: VulDB
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain low-privilege account with PackageKit API access
  2. Delivery
    Connect to PackageKit D-Bus API over network
  3. Exploit
    Submit crafted transaction with malicious frontend-socket argument
  4. Execution
    g_file_test authorization check bypassed in pk-transaction.c
  5. Impact
    Read confidential package data beyond caller's authorization

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization verification
MITRE ATT&CK

1 technique across 1 tactic: Defense Evasion

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires low-privilege authenticated access to the PackageKit API (confirmed by CVSS PR:L). The attacker must be able to submit a transaction request with a controlled frontend-socket argument to the pk-transaction.c API component - this is the specific triggering condition. The attack is network-reachable (AV:N) with low complexity (AC:L) and requires no user interaction (UI:N). Exploitation is limited by the PR:L authentication requirement: unauthenticated attackers cannot exploit this without first obtaining at least a low-privilege account or session. Impact is further limited to confidentiality (C:L) with no integrity or availability consequences. The scope is unchanged (S:U), meaning the vulnerability cannot be leveraged to compromise components outside PackageKit's trust boundary. No special non-default configuration was described as required beyond having PackageKit deployed with its API accessible.

Impact

The CVSS 3.1 vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N yields a base score of 4.3, reflecting a medium-low severity: network-reachable, low complexity, requires low-privilege authentication, no user interaction, no integrity or availability impact, and limited confidentiality exposure. The temporal modifiers (E:P for proof-of-concept, RL:X for no remediation level confirmed, RC:R for reasonable but unconfirmed confidence) marginally adjust the score but confirm active POC existence. There is no CISA KEV entry, so confirmed active exploitation cannot be stated. EPSS data was not provided, preventing probability-of-exploitation comparison. The PR:L requirement meaningfully limits the attack surface - unauthenticated exploitation is not supported by the CVSS vector. The scope is unchanged (S:U), meaning the vulnerability cannot be used to pivot beyond PackageKit's security boundary per CVSS modeling. Overall, this is a real but bounded risk: the POC lowers exploitation bar for accounts with any PackageKit API access, but the confidentiality-only impact and authenticated precondition limit blast radius.

Exploit ScenarioDerived

An attacker with a low-privileged account on a system or network segment with access to the PackageKit D-Bus API submits a crafted transaction request with a manipulated frontend-socket argument. The g_file_test authorization check in pk-transaction.c fails to correctly reject the request, allowing the attacker to read confidential package state information they would not ordinarily be authorized to access. A publicly available proof-of-concept at https://github.com/PackageKit/PackageKit/issues/969 demonstrates this bypass, lowering the skill threshold for exploitation.

Monitor Track and reassess. Why: LOW severity (CVSS 0.1-3.9).
No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jun 01, 2026

Improper authorization in PackageKit up to 1.3.5 allows a low-privileged authenticated remote attacker to bypass access controls via manipulation of the frontend-socket argument in the g_file_test function within pk-transaction.c, resulting in unauthorized confidentiality exposure (C:L). The vulnerability is tagged as an authentication bypass and publicly available exploit code exists, disclosed via GitHub issue #969 against the PackageKit project. No CISA KEV listing is present, but the combination of a publicly known proof-of-concept and low attack complexity (AC:L) elevates practical risk beyond what the base CVSS score of 4.3 alone suggests.

RemediationAI

No vendor-released patched version was identified at time of analysis; the upstream fix status should be tracked via the GitHub issue at https://github.com/PackageKit/PackageKit/issues/969, which serves as the primary POC and potential fix discussion thread. As a compensating control, restrict access to the PackageKit D-Bus API by tightening PolicyKit (polkit) rules to limit which users or processes may initiate transactions, reducing the pool of PR:L authenticated callers who could reach the vulnerable code path. Disabling or firewalling remote D-Bus exposure (if applicable to the deployment) would reduce the AV:N attack surface. Monitoring PackageKit transaction logs for anomalous frontend-socket arguments is an additional detective control. Note that restricting polkit rules may break legitimate package management workflows for non-root users; test in a staging environment before deploying broadly. Reference the VulDB entry at https://vuldb.com/vuln/367587 for updated patch status.

Affected VersionsENISA

packagekit 1.3.0
packagekit 1.3.1
packagekit 1.3.2
packagekit 1.3.5
packagekit 1.3.3
packagekit 1.3.4

Affected Packages

euvd packagekit no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

PackageKit is a Linux system service that abstracts package management operations across distributions via a D-Bus API, enabling frontend applications to install, remove, and query packages without direct root interaction. The vulnerable code resides in src/pk-transaction.c, which handles the lifecycle of package management transactions. The g_file_test() function - a GLib utility for file existence and property checks - is called against an attacker-influenced frontend-socket argument, and the authorization logic gating that check can be bypassed. CWE-285 (Improper Authorization) identifies the root cause as a failure to correctly enforce access controls, specifically when evaluating whether a caller is permitted to interact with a given socket path. The CPE string (cpe:2.3:a:n/a:packagekit:*:*:*:*:*:*:*:*) confirms all PackageKit application variants through version 1.3.5 are in scope, though the vendor/namespace field is unresolved (n/a), suggesting NVD CPE assignment is incomplete.

Know when Packagekit gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulDB) PRIMARY 2.1 LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P

Primary rating from Vendor (VulDB) · only source for this CVE.

CVSS VectorVendor: VulDB

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

2
Severity Changed
Jun 01, 2026 - 22:22 NVD
MEDIUM LOW
CVSS changed
Jun 01, 2026 - 22:22 NVD
4.3 (MEDIUM) 2.1 (LOW)

DescriptionCVE.org

A vulnerability has been found in PackageKit up to 1.3.5. Affected is the function g_file_test of the file src/pk-transaction.c of the component API. Such manipulation of the argument frontend-socket leads to improper authorization. The attack can be executed remotely. The exploit has been disclosed to the public and may be used.

Threat Intelligence Overview

EPSS Score
0.0%
Top 91% exploitable
Exploit
POC
Public exploit code exists
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity LOW
CISA KEV No
Public POC Yes
EPSS 0.0%
Patch available No
Active threat No
Deciding rule
LOW severity (CVSS 0.1-3.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Low
Technical Impact
Partial

Priority Score

30
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +10
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy