NeuVector has an insecure password storage and is vulnerable to rainbow attack

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

EPSS

• CVE-2025-53884: 0.18% estimated exploitation activity in the next 30 days; percentile 6.97 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact 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). NeuVector generates a cryptographically secure, random 16-character salt and uses it with the PBKDF2 algorithm to create the hash value for the following actions: - Creating a user - Updating a user’s password - Creating an API key Note: After upgrading to NeuVector 5.4.6, users must log in again so that NeuVector can regenerate the password hash. For API keys, you must send at least one request per API key to regenerate its hash value. Patches This issue is fixed in NeuVector version 5.4.6 and later. Workarounds There is no workaround. Upgrade to a patched version of NeuVector as soon as possible. References If you have any questions or comments about this advisory: - Reach out to the SUSE Rancher Security team for security related inquiries. - Open an issue in the NeuVector repository.…

Published by the source

28 Aug 2025, 13:33 UTC

Last modified by the source

2 Jul 2026, 20:20 UTC

Source last checked

26 Oct 2026, 15:24 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-8ff6-pc43-jwv3

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-53884

Advisory: NeuVector has an insecure password storage and is vulnerable to rainbow attack
IDs: CVE-2025-53884, GHSA-8ff6-pc43-jwv3
Record: https://patchnext.com/advisories/cve-2025-53884 (revision 1, source checked 26 Oct 2026, 15:24 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/neuvector/neuvector 0.0.0-20250825191744-da1a462074c3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/neuvector/neuvector: affected < 0.0.0-20250825191744-da1a462074c3; fixed in 0.0.0-20250825191744-da1a462074c3

## Suggested inspection (read-only)
- Go github.com/neuvector/neuvector: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/neuvector/neuvector.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-8ff6-pc43-jwv3 (GitHub-reviewed advisory GHSA-8ff6-pc43-jwv3 lists affected ranges: Go github.com/neuvector/neuvector >=0 <0.0.0-20250825191744-da1a462074c3)

Commands are suggestions: review each one before running it.