Is CVE-2025-54470 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2025-54470 being exploited in the wild.

How severe is CVE-2025-54470?

High severity, with a CVSS score of 8.6, published 30 October 2025.

Which products and versions are affected?

github.com/neuvector/neuvector (Go) >= 0.0.0-20230727023453-1c4957d53911, < 0.0.0-20251020133207-084a437033b4, SEMVER:introduced=0, SEMVER:introduced=0.0.0-20230727023453-1c4957d53911,fixed=0.0.0-20251020133207-084a437033b4; Suse NeuVector < v5.4.7.

Is there a fix for CVE-2025-54470?

Yes. github.com/neuvector/neuvector (Go): upgrade to 0.0.0-20251020133207-084a437033b4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2025-54470 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2025-54470?

Check whether you run github.com/neuvector/neuvector (Go) or Suse NeuVector 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.

CVE-2025-54470: SUSE NeuVector MITM and DoS in telemetry sender

Q: Is there a fix for CVE-2025-54470?

Yes. github.com/neuvector/neuvector (Go): upgrade to 0.0.0-20251020133207-084a437033b4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2025-54470 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2025-54470?

Check whether you run github.com/neuvector/neuvector (Go) or Suse NeuVector 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.

CVE-2025-54470 · Severity: high · CVSS 8.6 · Published 2025-10-30

NeuVector, a container security platform, contains vulnerabilities in its telemetry reporting component. If the anonymous data reporting feature is enabled, attackers could intercept or modify transmitted data or crash the service by sending an oversized response from a spoofed server. This could lead to a loss of service availability or the exposure of cluster metadata.

Technologies: github.com/neuvector/neuvector (Go), Suse NeuVector. Vendors: Go, Suse.

Quick answers

Is CVE-2025-54470 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-54470 being exploited in the wild.
How severe is CVE-2025-54470?: High severity, with a CVSS score of 8.6, published 30 October 2025.
Which products and versions are affected?: github.com/neuvector/neuvector (Go) >= 0.0.0-20230727023453-1c4957d53911, < 0.0.0-20251020133207-084a437033b4, SEMVER:introduced=0, SEMVER:introduced=0.0.0-20230727023453-1c4957d53911,fixed=0.0.0-20251020133207-084a437033b4; Suse NeuVector < v5.4.7.
Is there a fix for CVE-2025-54470?: Yes. github.com/neuvector/neuvector (Go): upgrade to 0.0.0-20251020133207-084a437033b4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2025-54470 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2025-54470?: Check whether you run github.com/neuvector/neuvector (Go) or Suse NeuVector 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 or later
```
go get github.com/neuvector/neuvector@v0.0.0-20251020133207-084a437033b4
```

Technical details

NeuVector's telemetry sender component fails to enforce TLS certificate verification (CWE-295) when communicating with its remote telemetry server. A network-positioned attacker can perform a man-in-the-middle attack to intercept or modify anonymous cluster data. Furthermore, the component lacks size limits when loading server responses into memory (CWE-770), allowing an attacker to trigger a Denial of Service via memory exhaustion. These issues are resolved in version 5.4.7 by enforcing certificate chain/hostname verification and implementing a 256-byte response limit.

Affected products

SUSE NeuVector < v5.4.7

Identifiers

CVE-2025-54470
GHSA-qqj3-g7mx-5p4w
GO-2025-4044

Timeline

2025-10-21: advisory: Original GHSA advisory published
2025-10-21: patched: Version 5.4.7 released with fixes

References

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