NeuVector has an insecure password storage vulnerable to rainbow attack

published 2025-08-28 14 mo ago modified 2026-09-10 1 mo ago also GHSA-8ff6-pc43-jwv3 , GO-2025-3917 , EUVD-2025-29462

cvss: 5.3; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.2%; EPSS 0.2% chance of exploitation in 30 days, percentile 6%
public exploits: 0; none known

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).

Patch / fix

fixed in 2 distros 2 links 4

go github.com/neuvector/neuvector 0.0.0-20250825191744-da1a462074c3
SUSE neuvector 5.4.6

suse opensuse

govulncheck-vulndb SLE Module for Package Hub 15 SP6, openSUSE Leap 15.6 0.0.20250918T182144-150000.1.107.1

suse advisories SUSE-SU-2025:03289-1

govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
govulncheck-vulndb openSUSE Tumbleweed 0.0.20250908T141310-1.1

opensuse advisories openSUSE-SU-2026:21483-1 openSUSE-SU-2025:15538-1

github.com/neuvector/neuvector@addc930 commit
github.com/neuvector/neuvector@da1a462 commit
github.com/neuvector/neuvector#2084 pull request
github.com/neuvector/neuvector#2085 pull request

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: partial
Assessed: 13 mo ago (2025-09-17)

Exploit prediction

0.18% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	5.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
GitHub	3.1	5.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem	package	affected	fixed in
go	github.com/neuvector/neuvector	<0.0.0-20250825191744-da1a462074c3 all versions	0.0.0-20250825191744-da1a462074c3

Affected products

SUSE neuvector

Classification

Weakness

CWE-759 Use of a One-Way Hash without a Salt
CWE-916 Use of Password Hash With Insufficient Computational Effort

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary