Vulnerability Database · Debian · packagekit · Version
packagekit 1.2.5-2
1.2.5-2 is affected by 5 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 0 High 0 Medium 1 Low 2 Unrated 2
-
Database updated 23/Oct/2026
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
packagekit 1.2.5-2 vulnerabilities
5 vulnerabilities cover packagekit 1.2.5-2. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| Improper Authorization Vulnerability in PackageKit - CVE-2026-10294 | 4.3 medium | No fix published | 01 Jun 2026 |
| Use-After-Free Vulnerability in PackageKit - Memory Access Risk | 3.3 low | No fix published | 03 Jan 2024 |
| CVE-2022-0987: PackageKit File Existence Timing Vulnerability | 3.3 low | No fix published | 28 Jun 2022 |
| Critical Vulnerability in PackageKit: CVE-2026-41651 | N/A unrated | No fix published | 22 Apr 2026 |
| Local User File Existence Disclosure in PackageKit - CVE-2022-0987 | N/A unrated | No fix published | 28 Jun 2022 |
Looking for another version, or everything Vulert holds for packagekit?
Questions
About packagekit 1.2.5-2
Is packagekit 1.2.5-2 vulnerable?
Yes. 5 vulnerabilities in the Vulert database cover packagekit 1.2.5-2: 0 critical, 0 high, 1 medium and 2 low, plus 2 not yet rated. Each entry above names the fixed version to move to.
How do I monitor packagekit for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the packagekit version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.