# CVE-2025-9815: alaneuler batteryKid NSXPCListener PrivilegeHelper.swift missing authentication

> Local attackers can bypass authentication in the NSXPCListener component to escalate privileges in the batteryKid macOS application.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **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:** 2 Sep 2025
- **Updated:** 2 Sep 2025
- **Also known as:** GHSA-g336-gvx8-vrrh

## What is CVE-2025-9815?

CVE-2025-9815 is a high-severity missing authorization vulnerability in alaneuler batteryKid, published on 2 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A weakness has been identified in alaneuler batteryKid up to 2.1 on macOS. The affected element is an unknown function of the file PrivilegeHelper/PrivilegeHelper.swift of the component NSXPCListener. This manipulation causes missing authentication. It is possible to launch the attack on the local host. The exploit has been made available to the public and could be exploited.

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Alaneuler Batterykid.

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

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

## Is CVE-2025-9815 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-9815 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-9815 is a high-severity missing authorization vulnerability in alaneuler batteryKid, published on 2 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-9815 exists.

Affected product: alaneuler batteryKid. 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-9815/ (Markdown: https://insights.sbomify.com/CVE-2025-9815/index.md)
```

## Sources

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

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