← Back
CVE-2025-54470
Vulnerability in github.com/neuvector/neuvector (CVE-2025-54470)
Summary
vulnerability in github.com/neuvector/neuvector (CVE-2025-54470). Risk of unauthorized operations or information disclosure. Exploitable via ``hostname``. Mitigation: upgrade to `0.0.0-20251020133207-084a437033b4` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-54470** has been found in github.com/neuvector/neuvector.
Attackers can target a specific entry point like ``hostname`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade github.com/neuvector/neuvector to **0.0.0-20251020133207-084a437033b4** or later.
If unsure, ask your IT team or search "github.com/neuvector/neuvector CVE-2025-54470" on the vendor's site.
CVE-2025-54470 (github.com/neuvector/neuvector) — CWE-295 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `hostname`
Patched: `0.0.0-20251020133207-084a437033b4` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-295) exists in github.com/neuvector/neuvector. Attackers reach the vulnerable code path via ``hostname`` without authentication.
📍 Affected scope
github.com/neuvector/neuvector — . Attack surface: `hostname`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.0.0-20251020133207-084a437033b4**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'github.com/neuvector/neuvector' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/neuvector/neuvector' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/neuvector/neuvector` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade github.com/neuvector/neuvector to 0.0.0-20251020133207-084a437033b4ステージング環境で 0.0.0-20251020133207-084a437033b4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/neuvector/neuvector
[{"type":"SEMVER","events":[{"introduced":"0.0.0-20230727023453-1c4957d53911"},{"fixed":"0.0.0-20251020133207-084a437033b4"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-54470
- package https://github.com/neuvector/neuvector
- web https://github.com/neuvector/neuvector/security/advisories/GHSA-qqj3-g7mx-5p4w
- web https://github.com/neuvector/neuvector/commit/06424701e69bf1eb76ff90180d78853fded93021
- web https://github.com/neuvector/neuvector/commit/415737cbec581a5dc5f204fac1c78b7f29ad7dc2
- web https://bugzilla.suse.com/show_bug.cgi?id=CVE-2025-54470
- web https://github.com/advisories/GHSA-qqj3-g7mx-5p4w