# CVE-2025-54467: NeuVector process with sensitive arguments lead to leakage

> Attackers can read sensitive passwords from NeuVector security event logs when Java processes with password arguments are terminated by process rules.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2025
- **Updated:** 17 Sep 2025
- **Also known as:** GHSA-w54x-xfxg-4gxq, GO-2025-3919

## What is CVE-2025-54467?

CVE-2025-54467 is a medium-severity vulnerability in SUSE neuvector, published on 17 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

When a Java command with password parameters is executed and terminated by NeuVector for Process rule violation the password will appear in the NeuVector security event log.

Weakness: CWE-522 (Insufficiently Protected Credentials)

## Which versions are affected by CVE-2025-54467?

3 open source packages ship an affected version, including github.com/neuvector/neuvector.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/neuvector/neuvector` | Go | All versions | None |
| `github.com/neuvector/neuvector` | Go | All versions | 0.0.0-20250902144615-f9ddbdf42031 |
| `github.com/neuvector/neuvector` | Go | All versions | 0.0.0-20250902144615-f9ddbdf42031 |

## How do I fix CVE-2025-54467?

Upgrade github.com/neuvector/neuvector to 0.0.0-20250902144615-f9ddbdf42031 or later.

## Is CVE-2025-54467 being exploited?

There is no known exploitation of CVE-2025-54467 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-54467 and fix it if it is affected.

What it is: CVE-2025-54467 is a medium-severity vulnerability in SUSE neuvector, published on 17 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-54467 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/neuvector/neuvector (Go): affected all versions; no fix listed
- github.com/neuvector/neuvector (Go): affected all versions; fixed in 0.0.0-20250902144615-f9ddbdf42031
- github.com/neuvector/neuvector (Go): affected all versions; fixed in 0.0.0-20250902144615-f9ddbdf42031

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-54467/ (Markdown: https://insights.sbomify.com/CVE-2025-54467/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-54467
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-54467
- OSV: https://osv.dev/vulnerability/CVE-2025-54467

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-54467/
Summaries are generated and may contain mistakes; the official description above is the record.