# CVE-2025-54471: NeuVector is shipping cryptographic material into its binary > Attackers can extract hard-coded cryptographic keys from NeuVector binaries to decrypt sensitive stored configurations. - **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 30 Oct 2025 - **Updated:** 30 Oct 2025 - **Also known as:** GHSA-h773-7gf7-9m2x, GO-2025-4043 ## What is CVE-2025-54471? CVE-2025-54471 is a medium-severity vulnerability in SUSE neuvector, published on 30 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description NeuVector used a hard-coded cryptographic key embedded in the source code. At compilation time, the key value was replaced with the secret key value and used to encrypt sensitive configurations when NeuVector stores the data. Weakness: CWE-321 (Use of Hard-coded Cryptographic Key) ## Which versions are affected by CVE-2025-54471? 5 open source packages ship an affected version, including github.com/neuvector/neuvector. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/neuvector/neuvector` | Go | From 0.0.0-20230727023453-1c4957d53911 | 0.0.0-20251020133207-084a437033b4 | | `github.com/neuvector/neuvector` | Go | From 0.0.0-20230727023453-1c4957d53911 | 0.0.0-20251020133207-084a437033b4 | | `github.com/neuvector/neuvector` | Go | From 0.0.0-20230727023453-1c4957d53911 | 0.0.0-20251020133207-084a437033b4 | | `github.com/neuvector/neuvector` | Go | From 5.3.0 | 5.4.7 | | `github.com/neuvector/neuvector` | Go | From 5.3.0 | 5.4.7 | ## How do I fix CVE-2025-54471? Upgrade github.com/neuvector/neuvector to a fixed version for your release line: 0.0.0-20251020133207-084a437033b4 or 5.4.7. ## Is CVE-2025-54471 being exploited? There is no known exploitation of CVE-2025-54471 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-54471 and fix it if it is affected. What it is: CVE-2025-54471 is a medium-severity vulnerability in SUSE neuvector, published on 30 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-54471 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/neuvector/neuvector (Go): affected from 0.0.0-20230727023453-1c4957d53911; fixed in 0.0.0-20251020133207-084a437033b4 - github.com/neuvector/neuvector (Go): affected from 0.0.0-20230727023453-1c4957d53911; fixed in 0.0.0-20251020133207-084a437033b4 - github.com/neuvector/neuvector (Go): affected from 0.0.0-20230727023453-1c4957d53911; fixed in 0.0.0-20251020133207-084a437033b4 - github.com/neuvector/neuvector (Go): affected from 5.3.0; fixed in 5.4.7 - github.com/neuvector/neuvector (Go): affected from 5.3.0; fixed in 5.4.7 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-54471/ (Markdown: https://insights.sbomify.com/CVE-2025-54471/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-54471 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-54471 - OSV: https://osv.dev/vulnerability/CVE-2025-54471 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-54471/ Summaries are generated and may contain mistakes; the official description above is the record.