# CVE-2025-0121: Cortex XDR Agent: Local Windows User Can Crash the Agent

> A local user can crash the Cortex XDR agent, allowing malware to operate undetected by disabling security monitoring.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/AU:N/R:U/V:D/RE:M/U:Amber`)
- **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:** 11 Apr 2025
- **Updated:** 11 Apr 2025
- **Also known as:** GHSA-crr6-98cq-p482

## What is CVE-2025-0121?

CVE-2025-0121 is a medium-severity vulnerability in Palo Alto Networks Cortex XDR Agent, published on 11 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A null pointer dereference vulnerability in the Palo Alto Networks Cortex® XDR agent on Windows devices allows a low-privileged local Windows user to crash the agent. Additionally, malware can use this vulnerability to perform malicious activity without Cortex XDR being able to detect it.

Weakness: CWE-476 (NULL Pointer Dereference)

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


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

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

## Is CVE-2025-0121 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-0121 is a medium-severity vulnerability in Palo Alto Networks Cortex XDR Agent, published on 11 Apr 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-0121 in the wild and no public exploit code.

Affected product: Palo Alto Networks Cortex XDR Agent. 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-0121/ (Markdown: https://insights.sbomify.com/CVE-2025-0121/index.md)
```

## Sources

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

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