# CVE-2026-106126: Command Injection

> Authenticated low-privileged attackers can execute arbitrary commands as SYSTEM on the PDCe via the Active Directory Events Listener.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Oct 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-4gpr-m24h-pm75

## What is CVE-2026-106126?

CVE-2026-106126 is a critical command injection vulnerability in Tenable, Inc. Tenable Identity Exposure (SaaS), published on 8 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A command injection vulnerability in the Active Directory Events Listener of Tenable Identity Exposure (SaaS) allows an authenticated, low-privileged attacker to execute arbitrary commands as SYSTEM on the PDCe.

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

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


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

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

## Is CVE-2026-106126 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-106126 is a critical command injection vulnerability in Tenable, Inc. Tenable Identity Exposure (SaaS), published on 8 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-106126 in the wild and no public exploit code.

Affected product: Tenable, Inc. Tenable Identity Exposure (SaaS). 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-106126/ (Markdown: https://insights.sbomify.com/CVE-2026-106126/index.md)
```

## Sources

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

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