# CVE-2025-7958: Code injection in Trellix Network Security NX, EX, FX, AX, and CMS

> A locally authenticated admin can execute arbitrary code via the web interface in Trellix Network Security appliances.

- **Severity:** High 7.1 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **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:** 26 Jun 2026
- **Updated:** 26 Jun 2026
- **Also known as:** GHSA-9639-6pf9-jh9r

## What is CVE-2025-7958?

CVE-2025-7958 is a high-severity code injection vulnerability in Trellix Network Security NX, EX, FX, AX, and CMS, published on 26 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A Code Injection vulnerability existed in Trellix Network Security CM and NX. A locally authenticated admin user can execute arbitrary code using the web interface and Alert artifact details.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

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

## Is CVE-2025-7958 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-7958 is a high-severity code injection vulnerability in Trellix Network Security NX, EX, FX, AX, and CMS, published on 26 Jun 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-2025-7958 in the wild and no public exploit code.

Affected product: Trellix Network Security NX, EX, FX, AX, and CMS. 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-7958/ (Markdown: https://insights.sbomify.com/CVE-2025-7958/index.md)
```

## Sources

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

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