# CVE-2026-0313: Cortex XSOAR: OS Command Injection Vulnerability

> An authenticated administrator can execute arbitrary OS commands on remote endpoints via the OS Query content pack in Cortex XSOAR and XSIAM.

- **Severity:** Medium 6.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U/U:Amber`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-mxh3-wwwc-mx62

## What is CVE-2026-0313?

CVE-2026-0313 is a medium-severity command injection vulnerability in Palo Alto Networks Cortex XSIAM OS Query, published on 14 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A command injection vulnerability in Palo Alto Networks Cortex XSOAR and Cortex XSIAM OS Query content pack enables an authenticated administrator to execute arbitrary OS commands on remote endpoints.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2026-0313 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-0313 is a medium-severity command injection vulnerability in Palo Alto Networks Cortex XSIAM OS Query, published on 14 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-0313 in the wild and no public exploit code.

Affected product: Palo Alto Networks Cortex XSIAM OS Query. 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-0313/ (Markdown: https://insights.sbomify.com/CVE-2026-0313/index.md)
```

## Sources

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

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