# CVE-2025-54470: NeuVector telemetry sender is vulnerable to MITM and DoS

> Attackers can intercept telemetry data or cause denial of service in NeuVector when anonymous reporting is enabled due to missing TLS verification and size limits.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Oct 2025
- **Updated:** 30 Oct 2025
- **Also known as:** GHSA-qqj3-g7mx-5p4w, GO-2025-4044

## What is CVE-2025-54470?

CVE-2025-54470 is a high-severity vulnerability in SUSE neuvector, published on 30 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This vulnerability affects NeuVector deployments only when the Report anonymous cluster data option is enabled. When this option is enabled, NeuVector sends anonymous telemetry data to the telemetry server.

In affected versions, NeuVector does not enforce TLS 
certificate verification when transmitting anonymous cluster data to the
 telemetry server. As a result, the communication channel is susceptible
 to man-in-the-middle (MITM) attacks, where an attacker could intercept 
or modify the transmitted data. Additionally, NeuVector loads the 
response of the telemetry server is loaded into memory without size 
limitation, which makes  it vulnerable to a Denial of Service(DoS) 
attack

Weakness: CWE-295 (Improper Certificate Validation)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/neuvector/neuvector` | Go | All versions | None |
| `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 |

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

Upgrade github.com/neuvector/neuvector to 0.0.0-20251020133207-084a437033b4 or later.

## Is CVE-2025-54470 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-54470 is a high-severity vulnerability in SUSE neuvector, published on 30 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-54470 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/neuvector/neuvector (Go): affected all versions; no fix listed
- 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

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

## Sources

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

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