# CVE-2025-11921: iStat Menus 7.10.4 - Local Privilege Escalation

> Local attackers can exploit an insecure XPC service in iStat Menus to inject commands and escalate privileges to root.

- **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`)
- **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:** 24 Nov 2025
- **Updated:** 19 Dec 2025
- **Also known as:** GHSA-cph3-9r5x-3xqh

## What is CVE-2025-11921?

CVE-2025-11921 is a high-severity command injection vulnerability in Bjango iStats, published on 24 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

iStats contains an insecure XPC service that allows local, unprivileged users to escalate their privileges to root via command injection.This issue affects iStats: 7.10.4.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command), CWE-732 (Incorrect Permission Assignment for Critical Resource)

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


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

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

## Is CVE-2025-11921 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-11921 is a high-severity command injection vulnerability in Bjango iStats, published on 24 Nov 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-11921 exists.

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

## Sources

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

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