sparkle-project Sparkle up to 2.9.1 Autoupdate AppInstaller.m shouldAcceptNewConnection Local Privilege Escalation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 1.11 |
Summary
A vulnerability has been found in sparkle-project Sparkle up to 2.9.1 and classified as problematic. Affected is the function shouldAcceptNewConnection of the file Autoupdate/AppInstaller.m of the component Autoupdate. This manipulation causes Local Privilege Escalation.
The identification of this vulnerability is CVE-2026-47122. The attack can only be executed locally. There is no exploit available.
Details
A vulnerability has been found in sparkle-project Sparkle up to 2.9.1 and classified as problematic. Affected by this vulnerability is the function shouldAcceptNewConnection of the file Autoupdate/AppInstaller.m of the component Autoupdate. The manipulation with an unknown input leads to a local privilege escalation vulnerability. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Sparkle is a software update framework for macOS. In versions up to and including 2.9.1, `Autoupdate/AppInstaller.m`'s `shouldAcceptNewConnection:` only enforces `SUCodeSigningVerifier validateConnection:` before stage 1 completes. After `_performedStage1Installation = YES`, new connections to the registered Mach service `<bundleId>-spki` are accepted from any local process without team-ID or code-signing checks. As of time of publication, no known patched versions are available.
The advisory is shared at github.com. This vulnerability is known as CVE-2026-47122 since 05/18/2026. The exploitation appears to be easy. An attack has to be approached locally. Technical details are known, but no exploit is available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Local Privilege EscalationCWE: Unknown
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
05/18/2026 CVE reserved07/21/2026 Advisory disclosed
07/21/2026 VulDB entry created
07/21/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Not defined
CVE: CVE-2026-47122 (🔒)
GCVE (CVE): GCVE-0-2026-47122
GCVE (VulDB): GCVE-100-380929
Entry
Created: 07/21/2026 17:03Changes: 07/21/2026 17:03 (54)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.