NeuVector admin account has insecure default password

Exploitation

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

CVSS

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

EPSS

• CVE-2025-8077: 0.56% estimated exploitation activity in the next 30 days; percentile 46.53 (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 A vulnerability exists in NeuVector versions up to and including 5.4.5, where a fixed string is used as the default password for the built-in admin account. If this password is not changed immediately after deployment, any workload with network access within the cluster could use the default credentials to obtain an authentication token. This token can then be used to perform any operation via NeuVector APIs. In earlier versions, NeuVector supports setting the default (bootstrap) password for the admin account using a Kubernetes Secret named neuvector-bootstrap-secret. This Secret must contain a key named bootstrapPassword. However, if NeuVector fails to retrieve this value, it falls back to the fixed default password. Patches This issue is resolved in NeuVector version 5.4.6 and later. For rolling upgrades, it's strongly recommended to change the default admin password to a secure one. Starting from version 5.4.6, NeuVector introduces additional Kubernetes RBAC permissions to…

Published by the source

28 Aug 2025, 13:33 UTC

Last modified by the source

2 Jul 2026, 20:22 UTC

Source last checked

26 Oct 2026, 15:24 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-8pxw-9c75-6w56

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

# Patch Next advisory brief: CVE-2025-8077

Advisory: NeuVector admin account has insecure default password
IDs: CVE-2025-8077, GHSA-8pxw-9c75-6w56
Record: https://patchnext.com/advisories/cve-2025-8077 (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: Critical (CVSS 9.8)
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-8pxw-9c75-6w56 (GitHub-reviewed advisory GHSA-8pxw-9c75-6w56 lists affected ranges: Go github.com/neuvector/neuvector >=0 <0.0.0-20250825191744-da1a462074c3)

Commands are suggestions: review each one before running it.