Categories
CVE-2026-47121 medium CVSS 6.1

Path Traversal in github.com/sparkle-project/Sparkle (CVE-2026-47121)

Summary

Path traversal in github.com/sparkle-project/Sparkle (CVE-2026-47121). Data can be tampered with by attackers. Exploitable via Extract. Mitigation: upgrade to 2.9.2 or later.

Original description

The description as published by the source.

Sparkle is a software update framework for macOS. Prior to version 2.9.2, Autoupdate/SUBinaryDeltaApply.m enforces relativePath.pathComponents containsObject:@".." and rejects writes whose immediate parent directory IS itself a symbolic link, but does not detect symlinks deeper in the relative path. Autoupdate/SPUSparkleDeltaArchive.m's extractItem: will create symlinks in the destination tree from archive content (no .. check on the symlink target), and a subsequent Extract item targeting /foo/bar then escapes the destination tree via fopen(path, "wb") because the kernel resolves the intermediate symlink during the open call. This is a defense-in-depth issue: exploitation requires a maliciously-crafted .delta that passes EdDSA signature verification, i.e. EdDSA private-key compromise. With the AppInstaller running as root for system-domain installs, it gives the holder of a stolen signing key arbitrary file write at root level via the delta-apply path, which is a strictly broader primitive than the "drop-in replacement bundle" install they would otherwise have. Version 2.9.2 contains a patch for the issue.

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-47121 has been found in github.com/sparkle-project/Sparkle.
Attackers can target a specific entry point like Extract over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 6.1/10.
What to do: upgrade github.com/sparkle-project/Sparkle to 2.9.2 or later.
If unsure, ask your IT team or search "github.com/sparkle-project/Sparkle CVE-2026-47121" on the vendor's site.

CVE-2026-47121 (github.com/sparkle-project/Sparkle) — CWE-22 / CVSS v3 6.1
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: Extract / destinationPath / destinationParentDirectory / NSFileTypeDirectory
Patched: 2.9.2 — apply immediately
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.

❓ What is the problem

Path traversal (CWE-22) exists in github.com/sparkle-project/Sparkle. Attackers reach the vulnerable code path via Extract without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/sparkle-project/Sparkle. Attack surface: Extract / destinationPath / destinationParentDirectory / NSFileTypeDirectory.

🔥 Severity

Severity: Medium (CVSS 6.1/10). Data can be tampered with by attackers.

🔧 How to fix

Update to 2.9.2.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

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

  1. 1
    Identify 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 し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade github.com/sparkle-project/Sparkle to 2.9.2

    ステージング環境で 2.9.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

swift github.com/sparkle-project/Sparkle
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.9.2"}]}]
SwiftURL github.com/sparkle-project/Sparkle
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.9.2"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details