# CVE-2026-47122: Sparkle's AppInstaller post-stage-1 XPC listener accepts unvalidated connections, allowing spoofed appcast item data injection

> Local attackers can inject spoofed appcast data into Sparkle's update process by connecting to an unvalidated XPC listener after stage 1 installation.

- **Severity:** Medium 4.2 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jul 2026
- **Updated:** 21 Jul 2026
- **Also known as:** GHSA-g3hp-f6mg-559v

## What is CVE-2026-47122?

CVE-2026-47122 is a medium-severity missing authorization vulnerability in sparkle-project Sparkle, published on 21 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-441 (Unintended Proxy or Intermediary), CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-47122?

2 open source packages ship an affected version, including github.com/sparkle-project/Sparkle. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/sparkle-project/Sparkle` | SwiftURL | All versions to 2.9.1 | None |
| `github.com/sparkle-project/Sparkle` | SwiftURL | All versions to 2.9.1 | None |

Products: Sparkle-Project Sparkle.

## How do I fix CVE-2026-47122?

No fix has been published for CVE-2026-47122 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-47122 being exploited?

There is no known exploitation of CVE-2026-47122 in the wild and no public exploit code.

## Other vulnerabilities in sparkle-project Sparkle

- [CVE-2026-47121](https://insights.sbomify.com/CVE-2026-47121/): Sparkle: Binary delta apply intermediate-symlink traversal in malicious .delta (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47122 and fix it if it is affected.

What it is: CVE-2026-47122 is a medium-severity missing authorization vulnerability in sparkle-project Sparkle, published on 21 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-47122 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/sparkle-project/Sparkle (SwiftURL): affected all versions up to 2.9.1; no fix listed
- github.com/sparkle-project/Sparkle (SwiftURL): affected all versions up to 2.9.1; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-47122/ (Markdown: https://insights.sbomify.com/CVE-2026-47122/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47122
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47122
- OSV: https://osv.dev/vulnerability/CVE-2026-47122

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-47122/
Summaries are generated and may contain mistakes; the official description above is the record.