← Back
CVE-2026-47865
critical
CVSS 9.8
Authentication Bypass in broadcom (CVE-2026-47865)
Summary
authentication bypass in broadcom (CVE-2026-47865). Successful exploitation can lead to full system takeover. Mitigation: upgrade to `31.2.2-2p3` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-47865** has been found in broadcom.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade broadcom to **31.2.2-2p3** or later.
If unsure, ask your IT team or search "broadcom CVE-2026-47865" on the vendor's site.
CVE-2026-47865 (broadcom) — CWE-287 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `31.2.2-2p3` — 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
**authentication bypass** (CWE-287) exists in broadcom.
📍 Affected scope
broadcom — .
🔥 Severity
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **31.2.2-2p3**.
🛡️ 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 'broadcom' .` 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 'broadcom' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `broadcom` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade broadcom to 31.2.2-2p3ステージング環境で 31.2.2-2p3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。