Auth bypass in Sparkle Project
CVE-2025-10016
The Sparkle framework includes a helper tool Autoupdate. Due to lack of authentication of connecting clients a local unprivileged attacker can request installation of crafted malicious PKG file by racing to connect to the daemon when other app spawns it as root. This results in local privilege escalation to root privileges. It is worth noting that it is possible to spawn Autopudate manually via Installer XPC service. However this requires the victim to enter credentials upon system authorization dialog creation that can be modified by the attacker. This issue was fixed in version 2.7.2
Vulnerability class: Broken Access Control
Published · last modified .
EPSS exploit prediction
EPSS: 0.002 (8.1th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 8th percentile — 8.1% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.002 · newest: 0.002 · change: 0.000
Affected products
- Sparkle Project — versions 0
Weakness classification (CWE)
Public proof-of-concept exploits
References
- cert.pl/en/posts/2025/09/CVE-2025-10015 (third-party-advisory)
- github.com/sparkle-project/Sparkle (product)
- github.com/sparkle-project/Sparkle/discussions/2764 (vendor-advisory)
Frequently asked questions
- What is CVE-2025-10016?
- CVE-2025-10016 is a vulnerability in Sparkle Project, classified under Incorrect Authorization. Published 2025-09-16.
- Is CVE-2025-10016 known to be exploited?
- 2 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.