NeuVector process with sensitive arguments lead to leakage

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

EPSS

• CVE-2025-54467: 0.25% estimated exploitation activity in the next 30 days; percentile 16.37 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact When a Java command with password parameters is executed and terminated by NeuVector for Process rule violation. For example, The command with the password appears in the NeuVector security event. To prevent this, NeuVector uses the following default regular expression to detect and redact sensitive data from process commands: Also, you can define custom patterns to redact by creating a Kubernetes ConfigMap. For example: Sample secret-patterns.yaml content: NeuVector uses the default and custom regex to decide whether the process command in a security event should be redacted. Note: If numerous regular expression (regex) patterns are configured in the Kubernetes ConfigMap for extended coverage of sensitive data matching, it can significantly impact performance of NeuVector enforcer, particularly in scenarios involving large inputs or frequent execution. The primary factor contributing to performance issues in regex is backtracking, where the regex engine attempts various…

Published by the source

28 Aug 2025, 13:33 UTC

Last modified by the source

2 Jul 2026, 20:27 UTC

Source last checked

26 Oct 2026, 15:24 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-w54x-xfxg-4gxq

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-54467

Advisory: NeuVector process with sensitive arguments lead to leakage
IDs: CVE-2025-54467, GHSA-w54x-xfxg-4gxq
Record: https://patchnext.com/advisories/cve-2025-54467 (revision 1, source checked 26 Oct 2026, 15:24 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/neuvector/neuvector 0.0.0-20250902144615-f9ddbdf42031. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/neuvector/neuvector: affected < 0.0.0-20250902144615-f9ddbdf42031; fixed in 0.0.0-20250902144615-f9ddbdf42031

## Suggested inspection (read-only)
- Go github.com/neuvector/neuvector: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/neuvector/neuvector.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-w54x-xfxg-4gxq (GitHub-reviewed advisory GHSA-w54x-xfxg-4gxq lists affected ranges: Go github.com/neuvector/neuvector >=0 <0.0.0-20250902144615-f9ddbdf42031)

Commands are suggestions: review each one before running it.