Vulnerability in github.com/sparkle-project/Sparkle (CVE-2026-47122)
Summary
Vulnerability in github.com/sparkle-project/Sparkle (CVE-2026-47122). Risk of unauthorized operations or information disclosure. Exploitable via SPUSentUpdateAppcastItemData.
Original description
The description as published by the source.
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 -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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-47122 has been found in github.com/sparkle-project/Sparkle.
Attackers can target a specific entry point like SPUSentUpdateAppcastItemData over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.2/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "github.com/sparkle-project/Sparkle CVE-2026-47122" on the vendor's site.
CVE-2026-47122 (github.com/sparkle-project/Sparkle) — CWE-306 / CVSS v3 4.2
Attack vector: local / no user interaction
Attack surface: SPUSentUpdateAppcastItemData / _willCompleteInstallation / SUAppcastItem / SMJobSubmit
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-306) exists in github.com/sparkle-project/Sparkle. Attackers reach the vulnerable code path via SPUSentUpdateAppcastItemData.
Check the vendor advisory for the affected versions of github.com/sparkle-project/Sparkle. Attack surface: SPUSentUpdateAppcastItemData / _willCompleteInstallation / SUAppcastItem / SMJobSubmit.
Severity: Medium (CVSS 4.2/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/sparkle-project/Sparkle' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/sparkle-project/Sparkle' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/sparkle-project/Sparkleを grep し、稼働しているサービス・バージョンを把握する。 -
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- web github.com