Skip to content
Fencer Intel
critical 9.8

CVE-2025-8077 json

NeuVector admin account has insecure default password

published last yr. modified 22d ago also GHSA-8pxw-9c75-6w56 , GO-2025-3918 , EUVD-2025-29463

cvss
9.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 46%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/neuvector/neuvector 0.0.0-20250825191744-da1a462074c3
  • SUSE neuvector 5.4.6
  • 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-1openSUSE-SU-2025:15538-1

Is CVE-2025-8077 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
last yr.

Exploit prediction

0.56% chance of exploitation in the next 30 days, higher than 46% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

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

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

References

Sources

Fencer Intel 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.