Local UI spoofing via unvalidated XPC connections
Published Jul 21, 2026 · Updated Jul 21, 2026
UI spoofing in Sparkle 2.9.1 and earlier allows local users to inject forged appcast metadata through the AppInstaller XPC service. AppInstaller's shouldAcceptNewConnection: stops validating code signatures after stage 1, allowing any local process to submit an SUAppcastItem. Exploitation requires terminating the updating app within a tight race window; the result is forged release-note metadata, not modification of installed code.
Summary
What happened
UI spoofing in Sparkle 2.9.1 and earlier allows local users to inject forged appcast metadata through the AppInstaller XPC service. AppInstaller's shouldAcceptNewConnection: stops validating code signatures after stage 1, allowing any local process to submit an SUAppcastItem. Exploitation requires terminating the updating app within a tight race window; the result is forged release-note metadata, not modification of installed code.
The record
- CVE
- CVE-2026-47122
- Published
- Jul 21, 2026
- Updated
- Jul 21, 2026
- Vendor
- Sparkle Project
- Product
- Sparkle
- Classifications
- CWE-306, CWE-441, T1559.003
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 21, 2026CVE publishedPublication date reported by the CVE source.
- Jul 21, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=<= 2.9.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo