Sign in Sign up
JA · EN · FR
SecPulse
← Back
CVE-2026-44328

Vulnerability in github.com/free5gc/smf (CVE-2026-44328)

Summary

vulnerability in github.com/free5gc/smf (CVE-2026-44328). Risk of unauthorized operations or information disclosure. Exploitable via `DELETE /upi/v1/upNodesLinks/{upNodeRef}`. Mitigation: upgrade to `1.4.3` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-44328** has been found in github.com/free5gc/smf. Attackers can target a specific entry point like `DELETE /upi/v1/upNodesLinks/{upNodeRef}` over the network to misuse the product. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: upgrade github.com/free5gc/smf to **1.4.3** or later. If unsure, ask your IT team or search "github.com/free5gc/smf CVE-2026-44328" on the vendor's site.
CVE-2026-44328 (github.com/free5gc/smf) — CWE-306 / Attack surface: DELETE /upi/v1/upNodesLinks/{upNodeRef} / DELETE /upi/v1/upNodesLinks/gNB1 / GET /nsmf-oam/v1/ / DELETE /upi/v1/upNodesLinks/{ref} Patched: `1.4.3` — 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-306) exists in github.com/free5gc/smf. Attackers reach the vulnerable code path via `DELETE /upi/v1/upNodesLinks/{upNodeRef}` without authentication.
📍 Affected scope
github.com/free5gc/smf — . Attack surface: DELETE /upi/v1/upNodesLinks/{upNodeRef} / DELETE /upi/v1/upNodesLinks/gNB1 / GET /nsmf-oam/v1/ / DELETE /upi/v1/upNodesLinks/{ref}.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.4.3**.
🛡️ 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 `DELETE /upi/v1/upNodesLinks/{upNodeRef}` requests with malformed payloads or SQL meta-characters. Run `grep -r 'github.com/free5gc/smf' .` 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

  1. 1
    Identify exposure identify 
    grep -r 'github.com/free5gc/smf' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/free5gc/smf` を grep し、稼働しているサービス・バージョンを把握する。

  2. 3
    Hunt for indicators of compromise detect 
    grep 'DELETE /upi/v1/upNodesLinks/{upNodeRef}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで `DELETE /upi/v1/upNodesLinks/{upNodeRef}` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 6
    Apply patch patch 
    Upgrade github.com/free5gc/smf to 1.4.3

    ステージング環境で 1.4.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

  4. 7
    Post-deployment verification verify 
    Replay attack against DELETE /upi/v1/upNodesLinks/{upNodeRef} on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

go github.com/free5gc/smf
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.4.3"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →