Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.5

NeuVector is shipping cryptographic material into its binary

CVE-2025-54471GHSA-h773-7gf7-9m2x

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, 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.4.6>= 0.0.0-20230727023453-1c4957d53911, < 0.0.0-20251020133207-084a437033b4
    Fixed in
    0.0.0-20251020133207-084a437033b4, 5.4.7

Sources

  • GitHub Advisory Database and maintainer security advisories on GitHub

    GitHub-reviewed advisory GHSA-h773-7gf7-9m2x lists affected ranges: Go github.com/neuvector/neuvector >=5.3.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
6.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS
  • CVE-2025-54471: 0.27% estimated exploitation activity in the next 30 days; percentile 18.98 (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 NeuVector used a hard-coded cryptographic key embedded in the source code. At compilation time, the key value was replaced with the secret key value and used to encrypt sensitive configurations when NeuVector stores the data. In the patched version, NeuVector leverages the Kubernetes secret neuvector-store-secret in neuvector namespace to dynamically generate cryptographically secure random keys. This approach removes the reliance on static key values and ensures that encryption keys are managed securely within Kubernetes. During rolling upgrade or restoring from persistent storage, the NeuVector controller checks each encrypted configured field. If a sensitive field in the configuration is found to be encrypted by the default encryption key, it’s decrypted with the default encryption key and then re-encrypted with the new dynamic encryption key. If the NeuVector controller does not have the correct RBAC for accessing the new secret, it writes this error log : Required…

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

    Published from ghsa record GHSA-h773-7gf7-9m2x

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-54471

Advisory: NeuVector is shipping cryptographic material into its binary
IDs: CVE-2025-54471, GHSA-h773-7gf7-9m2x
Record: https://patchnext.com/advisories/cve-2025-54471 (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: Medium (CVSS 6.5)
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, 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.4.6; >= 0.0.0-20230727023453-1c4957d53911, < 0.0.0-20251020133207-084a437033b4; fixed in 0.0.0-20251020133207-084a437033b4, 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-h773-7gf7-9m2x (GitHub-reviewed advisory GHSA-h773-7gf7-9m2x lists affected ranges: Go github.com/neuvector/neuvector >=5.3.0 =0.0.0-20230727023453-1c4957d53911 <0.0.0-20251020133207-084a437033b4)

Commands are suggestions: review each one before running it.

Loading voting…