# CVE-2026-0230: Cortex XDR Agent: Local Administrator can disable the agent on macOS

> A local administrator can bypass protection mechanisms to disable the Cortex XDR agent on macOS, allowing malware to operate undetected.

- **Severity:** Medium 4.0 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:U/AU:Y/R:U/V:D/RE:M/U:Amber`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Mar 2026
- **Updated:** 11 Mar 2026
- **Also known as:** GHSA-2ghj-fm9g-w3jm

## What is CVE-2026-0230?

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

### Official description

A problem with a protection mechanism in the Palo Alto Networks Cortex XDR agent on macOS allows a local administrator to disable the agent. This issue could be leveraged by malware to perform malicious activity without detection.

Weakness: CWE-754 (Improper Check for Unusual or Exceptional Conditions)

## Which versions are affected by CVE-2026-0230?


## How do I fix CVE-2026-0230?

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

## Is CVE-2026-0230 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-0230 and fix it if it is affected.

What it is: CVE-2026-0230 is a medium-severity vulnerability in Palo Alto Networks Cortex XDR Agent, published on 11 Mar 2026. 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-2026-0230 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-2026-0230/ (Markdown: https://insights.sbomify.com/CVE-2026-0230/index.md)
```

## Sources

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

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