Quick answers
- Is CVE-2026-19816 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-19816 being exploited in the wild.
- How severe is CVE-2026-19816?
- High severity, with a CVSS score of 7.1, published 14 September 2026.
- Which products and versions are affected?
- PackageKit affected versions unknown.
- Is there a fix for CVE-2026-19816?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-19816 attacked?
- It is attacked with local access, in a hosted service.
- Am I affected by CVE-2026-19816?
- Check whether you run PackageKit at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
PackageKit skips polkit authorization checks for transactions marked with the SIMULATE (dry-run) flag. However, in the dnf5 backend, the RepoRemove handler contains a logic error in its guard condition (role == REPO_REMOVE || !SIMULATE), which evaluates to true regardless of the SIMULATE flag. This allows an unprivileged local attacker to execute genuine package removals while claiming to simulate them, bypassing intended authorization controls. The vulnerability is specific to systems running PackageKit with the dnf5 backend and requires local access to the system.
Affected products
- PackageKit PackageKit affected versions unknown
Timeline
- 2026-09-14: disclosed