Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.9

NeuVector Enforcer is vulnerable to Command Injection and Buffer overflow

CVE-2025-54469GHSA-c8g6-qrwh-m3vp

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/neuvector/neuvector 5.4.7, 5.3.5, 0.0.0-20251020133207-084a437033b4), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/neuvector/neuvector

    Affected
    >= 5.3.0, < 5.3.5>= 5.4.0, <= 5.4.6>= 0.0.0-20230727023453-1c4957d53911, < 0.0.0-20251020133207-084a437033b4
    Fixed in
    0.0.0-20251020133207-084a437033b4, 5.3.5, 5.4.7

Sources

  • GitHub Advisory Database and maintainer security advisories on GitHub

    GitHub-reviewed advisory GHSA-c8g6-qrwh-m3vp lists affected ranges: Go github.com/neuvector/neuvector >=5.3.0 =5.4.0 =0.0.0-20230727023453-1c4957d53911 <0.0.0-20251020133207-084a437033b4

    VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.9 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS
  • CVE-2025-54469: 0.47% estimated exploitation activity in the next 30 days; percentile 40.82 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact A vulnerability was identified in NeuVector, where the enforcer used environment variables CLUSTERRPCPORT and CLUSTERLANPORT 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 CLUSTERRPCPORT and CLUSTERLANPORT 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. In the patched version, the monitor process validates the values of CLUSTERRPCPORT and CLUSTERLANPORT to ensure they contain only valid port…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-c8g6-qrwh-m3vp

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-54469

Advisory: NeuVector Enforcer is vulnerable to Command Injection and Buffer overflow
IDs: CVE-2025-54469, GHSA-c8g6-qrwh-m3vp
Record: https://patchnext.com/advisories/cve-2025-54469 (revision 1, source checked 26 Oct 2026, 15:13 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/neuvector/neuvector 5.4.7, 5.3.5, 0.0.0-20251020133207-084a437033b4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/neuvector/neuvector: affected >= 5.3.0, < 5.3.5; >= 5.4.0, <= 5.4.6; >= 0.0.0-20230727023453-1c4957d53911, < 0.0.0-20251020133207-084a437033b4; fixed in 0.0.0-20251020133207-084a437033b4, 5.3.5, 5.4.7

## Suggested inspection (read-only)
- Go github.com/neuvector/neuvector: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/neuvector/neuvector.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-c8g6-qrwh-m3vp (GitHub-reviewed advisory GHSA-c8g6-qrwh-m3vp lists affected ranges: Go github.com/neuvector/neuvector >=5.3.0 =5.4.0 =0.0.0-20230727023453-1c4957d53911 <0.0.0-20251020133207-084a437033b4)

Commands are suggestions: review each one before running it.

Loading voting…