# CVE-2025-10015: TCC Bypass via Downloader XPC Service in Sparkle

> A local attacker can bypass TCC restrictions in the Sparkle framework to access protected files by registering its XPC service globally.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **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:** 16 Sep 2025
- **Updated:** 16 Sep 2025
- **Also known as:** GHSA-fvpx-gx3c-pq7f

## What is CVE-2025-10015?

CVE-2025-10015 is a medium-severity vulnerability in Sparkle, published on 16 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Sparkle framework includes an XPC service Downloader.xpc, by default this service is private to the application its bundled with. A local unprivileged attacker can register this XPC service globally which will inherit TCC permissions of the application. 
Lack of validation of connecting client allows the attacker to copy TCC-protected files to an arbitrary location. Access to other resources beyond granted-permissions requires user interaction with a system prompt asking for permission.

This issue was fixed in version 2.7.2

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2025-10015?


## How do I fix CVE-2025-10015?

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

## Is CVE-2025-10015 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-10015 and fix it if it is affected.

What it is: CVE-2025-10015 is a medium-severity vulnerability in Sparkle, published on 16 Sep 2025. 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-2025-10015 in the wild and no public exploit code.

Affected product: Sparkle. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2025-10015/ (Markdown: https://insights.sbomify.com/CVE-2025-10015/index.md)
```

## Sources

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

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