← Back
CVE-2026-54909
medium
CVSS 5.3
Vulnerability in github.com/pion/stun/v3 (CVE-2026-54909)
Summary
vulnerability in github.com/pion/stun/v3 (CVE-2026-54909). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `3.1.5` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-54909** has been found in github.com/pion/stun/v3.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade github.com/pion/stun/v3 to **3.1.5** or later.
If unsure, ask your IT team or search "github.com/pion/stun/v3 CVE-2026-54909" on the vendor's site.
CVE-2026-54909 (github.com/pion/stun/v3) — CWE-20 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `3.1.5` — apply immediately
Workaround: No work around; please upgrade to v3.1.5 or a newer version.
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-20) exists in github.com/pion/stun/v3.
📍 Affected scope
github.com/pion/stun/v3 — .
🔥 Severity
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **3.1.5**.
🛡️ Workaround
Workaround: No work around; please upgrade to v3.1.5 or a newer version.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'github.com/pion/stun/v3' .` 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/pion/stun/v3' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/pion/stun/v3` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
No work around; please upgrade to v3.1.5 or a newer version.パッチが適用されるまでの応急処置として、No work around; please upgrade to v3.1.5 or a newer version. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade github.com/pion/stun/v3 to 3.1.5ステージング環境で 3.1.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/pion/stun/v3
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.5"}]}]
go
github.com/pion/stun/v2
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
go
github.com/pion/stun
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]