cve.bz

CVE-2025-8077 suse neuvector: Use of Default Password

9.8 criticalEPSS 0.6%Fix available

Critical (9.8) in suse neuvector. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/neuvector/neuvector 0.0.0-20250825191744-da1a462074c3.

On this page
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.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.6% (unchanged from 0.6% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 47th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2025-09-18. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-1393 Use of Default Password
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-8077 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-8077?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-8077?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-8077 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
SUSE neuvectorfrom 5.0.0 before 5.4.6

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-8pxw-9c75-6w56Gogithub.com/neuvector/neuvector<0.0.0-20250825191744-da1a462074c30.0.0-20250825191744-da1a462074c3
GO-2025-3918Gogithub.com/neuvector/neuvectorall versionsno fix published

Linux distributions

DistributionReleasePackageFixed inAdvisory
SUSELinux Enterprise Module for Package Hub 15 SP6govulncheck-vulndb0.0.20250918T182144-150000.1.107.1SUSE-SU-2025:03289-1
openSUSELeap 15.6govulncheck-vulndb0.0.20250918T182144-150000.1.107.1SUSE-SU-2025:03289-1
openSUSELeap 16.0govulncheck-vulndb0.0.20260723T184607-160000.1.1openSUSE-SU-2026:21483-1
openSUSETumbleweedgovulncheck-vulndb0.0.20250908T141310-1.1openSUSE-SU-2025:15538-1

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: SUSE · openSUSE.

References

Check your stackJSON