CVE-2025-54471: GO-2025-4043 - NeuVector is shipping cryptographic material into its binary in github.com/neuvector/neuvector

CVE-2025-54471 · Severity: medium · CVSS 6.5 · Published 2025-10-30

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.

Technologies: github.com/neuvector/neuvector (Go). Vendors: Go.

Quick answers

Is CVE-2025-54471 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-54471 being exploited in the wild.
How severe is CVE-2025-54471?
Medium severity, with a CVSS score of 6.5, published 30 October 2025.
Which products and versions are affected?
github.com/neuvector/neuvector (Go) SEMVER:introduced=0.0.0-20230727023453-1c4957d53911,fixed=0.0.0-20251020133207-084a437033b4, SEMVER:introduced=5.3.0,fixed=5.4.7.
Is there a fix for CVE-2025-54471?
Yes. github.com/neuvector/neuvector (Go): upgrade to 0.0.0-20251020133207-084a437033b4, 5.4.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2025-54471?
Check whether you run github.com/neuvector/neuvector (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/neuvector/neuvector (Go): upgrade to 0.0.0-20251020133207-084a437033b4, 5.4.7 or later
    go get github.com/neuvector/neuvector@v5.4.7

Affected products

  • github.com/neuvector/neuvector (Go) SEMVER:introduced=0.0.0-20230727023453-1c4957d53911,fixed=0.0.0-20251020133207-084a437033b4, SEMVER:introduced=5.3.0,fixed=5.4.7

Identifiers

  • CVE-2025-54471
  • GHSA-h773-7gf7-9m2x
  • GO-2025-4043

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.