# CVE-2025-53884: NeuVector has an insecure password storage vulnerable to rainbow attack

> Attackers can recover user passwords and API keys via rainbow table attacks due to unsalted hashing, compromising NeuVector accounts.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2025
- **Updated:** 17 Sep 2025
- **Also known as:** GHSA-8ff6-pc43-jwv3, GO-2025-3917

## What is CVE-2025-53884?

CVE-2025-53884 is a medium-severity vulnerability in SUSE neuvector, published on 17 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

NeuVector stores user passwords and API keys using a simple, unsalted hash. This method is vulnerable to rainbow table attack (offline attack where hashes of known passwords are precomputed).

Weakness: CWE-759 (Use of a One-Way Hash without a Salt)

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

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 | All versions | 0.0.0-20250825191744-da1a462074c3 |
| `github.com/neuvector/neuvector` | Go | All versions | 0.0.0-20250825191744-da1a462074c3 |

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

Upgrade github.com/neuvector/neuvector to 0.0.0-20250825191744-da1a462074c3 or later.

## Is CVE-2025-53884 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-53884 is a medium-severity vulnerability in SUSE neuvector, published on 17 Sep 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-53884 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 all versions; fixed in 0.0.0-20250825191744-da1a462074c3
- github.com/neuvector/neuvector (Go): affected all versions; fixed in 0.0.0-20250825191744-da1a462074c3

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

## Sources

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

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