CVE-2026-47122: CWE-306: Missing Authentication for Critical Function in sparkle-project Sparkle
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.
AI Analysis
Technical Summary
CVE-2026-47122 describes a missing authentication vulnerability in Sparkle up to version 2.9.1. Specifically, after the internal flag `_performedStage1Installation` is set to YES, the method `shouldAcceptNewConnection:` in `Autoupdate/AppInstaller.m` stops enforcing team-ID or code-signing checks on new connections to the Mach service named `<bundleId>-spki`. Initially, connections are validated using `SUCodeSigningVerifier validateConnection:`, but this enforcement is bypassed after stage 1 completes, allowing any local process to connect. This represents a missing authentication control (CWE-306) and potentially unintended access (CWE-441). No official fix or patch is available at the time of publication.
Potential Impact
The vulnerability allows local processes to connect to a critical Mach service without proper authentication after a certain installation stage. This can lead to unauthorized local interactions that may result in limited integrity and availability impacts, as indicated by the CVSS vector (no confidentiality impact, low integrity and availability impact). There are no known exploits in the wild currently.
Mitigation Recommendations
No official patch or fix is currently available for this vulnerability. Users should monitor the vendor's advisories for updates. Until a fix is released, restricting local access to the affected Mach service or limiting execution privileges of untrusted local processes may reduce risk, but no vendor-recommended mitigation is provided.
CVE-2026-47122: CWE-306: Missing Authentication for Critical Function in sparkle-project Sparkle
Description
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.
CVSS v3.1
Score 4.2medium
Affected software
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-47122 describes a missing authentication vulnerability in Sparkle up to version 2.9.1. Specifically, after the internal flag `_performedStage1Installation` is set to YES, the method `shouldAcceptNewConnection:` in `Autoupdate/AppInstaller.m` stops enforcing team-ID or code-signing checks on new connections to the Mach service named `<bundleId>-spki`. Initially, connections are validated using `SUCodeSigningVerifier validateConnection:`, but this enforcement is bypassed after stage 1 completes, allowing any local process to connect. This represents a missing authentication control (CWE-306) and potentially unintended access (CWE-441). No official fix or patch is available at the time of publication.
Potential Impact
The vulnerability allows local processes to connect to a critical Mach service without proper authentication after a certain installation stage. This can lead to unauthorized local interactions that may result in limited integrity and availability impacts, as indicated by the CVSS vector (no confidentiality impact, low integrity and availability impact). There are no known exploits in the wild currently.
Mitigation Recommendations
No official patch or fix is currently available for this vulnerability. Users should monitor the vendor's advisories for updates. Until a fix is released, restricting local access to the affected Mach service or limiting execution privileges of untrusted local processes may reduce risk, but no vendor-recommended mitigation is provided.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-18T19:50:18.694Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a5f856d2a4a8d598947259a
Added to database: 07/21/2026, 14:42:53 UTC
Last enriched: 07/21/2026, 14:58:32 UTC
Last updated: 07/21/2026, 21:16:10 UTC
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.