# CVE-2025-54469: NeuVector Enforcer is vulnerable to Command Injection and Buffer overflow

> Attackers can inject malicious commands via unsanitized environment variables in the NeuVector enforcer container, leading to code execution.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Oct 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-c8g6-qrwh-m3vp, GO-2025-4042

## What is CVE-2025-54469?

CVE-2025-54469 is a critical command injection vulnerability in SUSE neuvector, published on 30 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was identified in NeuVector, where the enforcer used environment variables CLUSTER_RPC_PORT and CLUSTER_LAN_PORT to generate a command to be executed via popen, without first sanitising their values.

The entry process of the enforcer container is the monitor
 process. When the enforcer container stops, the monitor process checks 
whether the consul subprocess has exited. To perform this check, the 
monitor process uses the popen function to execute a shell command that determines whether the ports used by the consul subprocess are still active.

The values of environment variables CLUSTER_RPC_PORT and CLUSTER_LAN_PORT
 are used directly to compose shell commands via popen without 
validation or sanitization.  This behavior could allow a malicious user 
to inject malicious commands through these variables within the enforcer
 container.

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

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

7 open source packages ship an affected version, including github.com/neuvector/neuvector.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/neuvector/neuvector` | Go | From 0.0.0-20230727023453-1c4957d53911 | 0.0.0-20251020133207-084a437033b4 |
| `github.com/neuvector/neuvector` | Go | From 0.0.0-20230727023453-1c4957d53911 | 0.0.0-20251020133207-084a437033b4 |
| `github.com/neuvector/neuvector` | Go | From 0.0.0-20230727023453-1c4957d53911 | 0.0.0-20251020133207-084a437033b4 |
| `github.com/neuvector/neuvector` | Go | From 5.3.0 | 5.3.5 |
| `github.com/neuvector/neuvector` | Go | From 5.3.0 | 5.3.5 |
| `github.com/neuvector/neuvector` | Go | From 5.4.0 | 5.4.7 |
| `github.com/neuvector/neuvector` | Go | From 5.4.0 | 5.4.7 |

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

Upgrade github.com/neuvector/neuvector to a fixed version for your release line: 0.0.0-20251020133207-084a437033b4, 5.3.5 or 5.4.7.

## Is CVE-2025-54469 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-54469 is a critical command injection vulnerability in SUSE neuvector, published on 30 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-54469 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/neuvector/neuvector (Go): affected from 0.0.0-20230727023453-1c4957d53911; fixed in 0.0.0-20251020133207-084a437033b4
- github.com/neuvector/neuvector (Go): affected from 0.0.0-20230727023453-1c4957d53911; fixed in 0.0.0-20251020133207-084a437033b4
- github.com/neuvector/neuvector (Go): affected from 0.0.0-20230727023453-1c4957d53911; fixed in 0.0.0-20251020133207-084a437033b4
- github.com/neuvector/neuvector (Go): affected from 5.3.0; fixed in 5.3.5
- github.com/neuvector/neuvector (Go): affected from 5.3.0; fixed in 5.3.5
- github.com/neuvector/neuvector (Go): affected from 5.4.0; fixed in 5.4.7
- github.com/neuvector/neuvector (Go): affected from 5.4.0; fixed in 5.4.7

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-54469/ (Markdown: https://insights.sbomify.com/CVE-2025-54469/index.md)
```

## Sources

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

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