Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2025-8077 — neuvector

🔴 CVSS 9.8 — Critical ✅ No Known Exploit CWE-1393 NVD
9.8
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

NeuVector admin account has insecure default password

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 via Helm.
  • If deploying or upgrading manually, you must create these roles before starting NeuVector.

NOTE: If these roles are not present, the NeuVector controller (from version 5.4.6 onward) does not start.

Behavior in Patched Versions

  • Upgrades: NeuVector does not reset any existing account passwords. It's strongly recommended to change the default admin password to a secure one.
  • New deployments:
  • If bootstrapPassword is not set in the `neuvector-bootstrap-secret, NeuVector generates a secure password and stores it in the same Secret.

On first login, the default admin must retrieve the password using:

```

kubectl get secret -n {neuvector} neuvector-bootstrap-secret \

-o go-template='{{ .data.bootstrapPassword | base64decode }}{{ "\n" }}'

```

The password must be changed during the first login via the NeuVector UI.

NOTE: If the default admin password is set using a Kubernetes ConfigMap or a persistent backup (not a fixed string), this value takes precedence over the Secret-based mechanism.

Workarounds

For existing vulnerable versions, log in to the NeuVector UI immediately after deployment and update the default admin password.

References

If you have any questions or comments about this advisory:

  • Reach out to the [SUSE Rancher Security team](https://github.com/rancher/rancher/security/policy) for security related inquiries.
  • Open an issue in the [NeuVector](https://github.com/neuvector/neuvector/issues/new/choose) repository.
  • Verify with our [support matrix](https://www.suse.com/suse-neuvector/support-matrix/all-supported-versions/neuvector-v-all-versions/) and [product support lifecycle](https://www.suse.com/lifecycle/#suse-security).

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity high, availability high.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

  • Attack vector: Network — reachable from anywhere that can route to the service.
  • Attack complexity: Low — the attack works reliably, with no preparation.
  • Privileges required: None — an unauthenticated stranger can try it.
  • User interaction: None — nobody has to be tricked into anything.
  • Scope: Unchanged — the damage stays inside the vulnerable component.
  • Confidentiality impact: High — total loss, or loss the attacker controls.
  • Integrity impact: High — total loss, or loss the attacker controls.
  • Availability impact: High — total loss, or loss the attacker controls.

Weakness class

CVE-2025-8077 is classified as CWE-1393: Use of Default Password. The product uses default passwords for potentially critical functionality.

Affected software

CVE-2025-8077 is recorded against 2 packages.

  • github.com/neuvector/neuvector
  • unknown

Timeline and source

Published on 8 September 2025 and last revised on 2 July 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.

References

github.com (Advisory)

Other advisories for this package

github.com/neuvector/neuvector has other advisories on record. If you are patching this one, these are worth checking on the same host:

Same weakness in other software

These advisories are the same class of weakness (CWE-1393: Use of Default Password) in other software:

Details

Severity CRITICAL
CVSS Score 9.8
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CWE CWE-1393
Public Exploit ✅ No
Source NVD
Published 2025-09-08
Updated 2026-08-20
Modified 2026-07-02
Fix URL N/A

Affected Packages

Software From version Fixed in
github.com/neuvector/neuvector
unknown

Similar Threats

Exploit Protection

Are you running neuvector?

CVE-2025-8077 carries CVSS 9.8 Critical rating. BotEraser checks your installation against this and other known CVE records, and blocks IPs associated with exploit activity.

Check My Site For CVE-2025-8077 →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2025