CVE-2026-47122

MEDIUMPre-NVD 4.24.2—
EchelonGraph scoreLOW confidence

Score 4.2 from GitHub Security Advisory published 2026-05-29. the CNA's CVSS baseline 4.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:github_m, epss, ghsa
4.2
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.2Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

Summary

AppInstaller post-stage-1 XPC listener accepts unvalidated connections, allowing spoofed appcast item data injection.

Details

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.

The following chain of events enables an attacker to inject a spoofed SPUSentUpdateAppcastItemData payload:

  • Installer finishes unarchiving the update successfully (_willCompleteInstallation is set).
  • The app responsible for updating the bundle crashes or is forcefully quit before it has a chance to send SPUSentUpdateAppcastItemData to the installer. There is no user interaction between the prior step and this one, so the timing window is tight.
  • After stage 1 of the installer is performed (_performedStage1Installation = YES), but before final installation completes (since all services are cleaned up by then), an attacker process connects to the -spki Mach service - no code-signing validation is enforced - and sends a spoofed SPUSentUpdateAppcastItemData message containing an attacker-crafted SUAppcastItem.
  • A Sparkle-aware app that checks for updates on the bundle being updated launches before installation completes. The progress agent re-broadcasts the spoofed SUAppcastItem on its -spks status service, and the launching app displays attacker-controlled release notes (name, version, critical flag).

Note: Sparkle can be used to update other app bundles, so the "app doing the updating" and the "app being updated" are not necessarily the same bundle.

In the system-domain case (SPUUsesSystemDomainForBundlePath = true), the AppInstaller runs as root via SMJobSubmit to kSMDomainSystemLaunchd, and the Mach service is reachable by any local user process.

Affected versions: 2.x branch including 2.9.1.

Impact

A local user-level process can inject a forged SUAppcastItem (arbitrary name, version, critical flag) into the progress agent's status broadcast. Other Sparkle-aware clients on the system will display attacker-controlled release notes as authoritative installation state.

The integrity of the installed code is not affected - the bundle moved into place is the legitimate, signature-validated update from stage 1. The impact is limited to UI spoofing of installation metadata.

Remediation

Enforce SUCodeSigningVerifier validateConnection: on all new connections regardless of installation stage, or disallow SPUSentUpdateAppcastItemData after the active connection invalidates.

CVSS v3
4.2
EG Score
4.2(low)
EPSS
2.4%
KEV
Not listed

Published

May 29, 2026

Last Modified

May 29, 2026

Vendor Advisories for CVE-2026-47122(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
swiftgithub.com/sparkle-project/Sparkle—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-16 01:49 UTCEG score recompute
  2. 2026-07-16 01:49 UTCGHSA enrichment
  3. 2026-07-14 13:55 UTCEG score recompute
  4. 2026-07-14 13:55 UTCGHSA enrichment
  5. 2026-07-11 17:23 UTCEG score recompute
  6. 2026-07-11 17:23 UTCGHSA enrichment
  7. 2026-07-08 17:17 UTCEG score recompute
  8. 2026-07-08 17:17 UTCGHSA enrichment
  9. 2026-07-02 03:48 UTCEG score recompute
  10. 2026-07-02 03:48 UTCGHSA enrichment
  11. 2026-07-01 01:28 UTCEG score recompute
  12. 2026-07-01 01:28 UTCGHSA enrichment
  13. 2026-06-29 21:29 UTCEG score recompute
  14. 2026-06-29 21:29 UTCGHSA enrichment
  15. 2026-06-28 19:46 UTCEG score recompute
  16. 2026-06-28 19:46 UTCGHSA enrichment
  17. 2026-06-27 17:58 UTCEG score recompute
  18. 2026-06-27 17:58 UTCGHSA enrichment
  19. 2026-06-26 16:11 UTCEG score recompute
  20. 2026-06-26 16:10 UTCGHSA enrichment
  21. 2026-06-25 06:19 UTCEG score recompute
  22. 2026-06-25 06:19 UTCGHSA enrichment
  23. 2026-06-24 02:49 UTCEG score recompute
  24. 2026-06-24 02:49 UTCGHSA enrichment
  25. 2026-06-18 04:08 UTCEG score recompute
Show 38 more
  1. 2026-06-18 04:08 UTCGHSA enrichment
  2. 2026-06-17 02:26 UTCEG score recompute
  3. 2026-06-17 02:25 UTCGHSA enrichment
  4. 2026-06-16 00:42 UTCEG score recompute
  5. 2026-06-16 00:42 UTCGHSA enrichment
  6. 2026-06-14 23:18 UTCEPSS rescore
  7. 2026-06-14 22:59 UTCEG score recompute
  8. 2026-06-14 22:59 UTCGHSA enrichment
  9. 2026-06-13 23:00 UTCEPSS rescore
  10. 2026-06-13 21:17 UTCEG score recompute
  11. 2026-06-13 21:17 UTCGHSA enrichment
  12. 2026-06-12 23:12 UTCEPSS rescore
  13. 2026-06-12 19:33 UTCEG score recompute
  14. 2026-06-12 19:33 UTCGHSA enrichment
  15. 2026-06-11 17:50 UTCEG score recompute
  16. 2026-06-11 17:50 UTCGHSA enrichment
  17. 2026-06-10 16:07 UTCEG score recompute
  18. 2026-06-10 16:07 UTCGHSA enrichment
  19. 2026-06-09 14:25 UTCEG score recompute
  20. 2026-06-09 14:25 UTCGHSA enrichment
  21. 2026-06-08 12:41 UTCEG score recompute
  22. 2026-06-08 12:41 UTCGHSA enrichment
  23. 2026-06-07 10:59 UTCEG score recompute
  24. 2026-06-07 10:59 UTCGHSA enrichment
  25. 2026-06-06 09:17 UTCEG score recompute
  26. 2026-06-06 09:17 UTCGHSA enrichment
  27. 2026-06-05 07:33 UTCEG score recompute
  28. 2026-06-05 07:33 UTCGHSA enrichment
  29. 2026-06-04 05:51 UTCEG score recompute
  30. 2026-06-04 05:51 UTCGHSA enrichment
  31. 2026-06-03 04:08 UTCEG score recompute
  32. 2026-06-03 04:08 UTCGHSA enrichment
  33. 2026-06-02 02:25 UTCEG score recompute
  34. 2026-06-02 02:25 UTCGHSA enrichment
  35. 2026-06-01 00:42 UTCEG score recompute
  36. 2026-06-01 00:42 UTCGHSA enrichment
  37. 2026-05-29 20:20 UTCEG score recompute
  38. 2026-05-29 20:20 UTCGHSA enrichment

Related CVEs(same product + same CWE)

Same product

1 shown

swift:github.com/sparkle-project/Sparkle

Frequently asked(5)

What is CVE-2026-47122?
CVE-2026-47122 is a medium vulnerability published on May 29, 2026. Sparkle's AppInstaller post-stage-1 XPC listener accepts unvalidated connections, allowing spoofed appcast item data injection Summary AppInstaller post-stage-1 XPC listener accepts unvalidated connections, allowing spoofed appcast item data injection. Details Autoupdate/AppInstaller.m's…
When was CVE-2026-47122 disclosed?
CVE-2026-47122 was first published in the National Vulnerability Database on May 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47122 actively exploited?
CVE-2026-47122 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-47122?
CVE-2026-47122 has a CVSS v4.0 base score of 4.2 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-47122?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47122, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-47122

Explore →

Is Your Infrastructure Affected by CVE-2026-47122?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs