← Back
OSV-2026-970
Vulnerability in open5gs (OSV-2026-970)
Summary
vulnerability in open5gs (OSV-2026-970). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `76d2237c0e99dd8cd01f03351a375a4c21d003c0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **OSV-2026-970** has been found in open5gs.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade open5gs to **76d2237c0e99dd8cd01f03351a375a4c21d003c0** or later.
If unsure, ask your IT team or search "open5gs OSV-2026-970" on the vendor's site.
OSV-2026-970 (open5gs) —
Patched: `76d2237c0e99dd8cd01f03351a375a4c21d003c0` — 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** (unclassified) exists in open5gs.
📍 Affected scope
open5gs — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **76d2237c0e99dd8cd01f03351a375a4c21d003c0**.
🛡️ 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 'open5gs' .` 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 'open5gs' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `open5gs` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade open5gs to 76d2237c0e99dd8cd01f03351a375a4c21d003c0ステージング環境で 76d2237c0e99dd8cd01f03351a375a4c21d003c0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
OSS-Fuzz
open5gs
[{"repo":"https:\/\/github.com\/open5gs\/open5gs.git","type":"GIT","events":[{"introduced":"ec6b76dccf975373cf108a09b1a4a284aaca20c5"},{"fixed":"76d2237c0e99dd8cd01f03351a375a4c21d003c0"}]}]