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.

Affected: Go: github.com/neuvector/neuvector

### 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 ensure the bootstrap password can be securely managed via Secrets:

``` kubectl create role neuvector-binding-secret-controller \ --verb=create,patch,update --resource=secrets -n {neuvector}

kubectl create rolebinding neuvector-binding-secret-controller \ --role=neuvector-binding-secret-controller \ --serviceaccount=neuvector:controller \ --serviceaccount=neuvector:default -n {neuvector} ```

- These RBAC roles are automatically applied when deploying…

govulncheck-vulndb-0.0.20250908T141310-1.1 on GA media