Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-44329 critical CVSS 10.0

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

Summary

Vulnerability in github.com/free5gc/smf (CVE-2026-44329). Data can be tampered with by attackers. Exploitable via GET /upi/v1/upNodesLinks. Mitigation: upgrade to 1.4.3 or later.

Original description

The description as published by the source.

Summary

free5GC's SMF mounts the UPI management route group without OAuth2/bearer-token authorization middleware. A network attacker who can reach SMF on the SBI can hit UPI endpoints with no Authorization header at all, and the requests reach the SMF business handlers. In the running Docker lab this was directly demonstrated for read (GET /upi/v1/upNodesLinks), write (POST /upi/v1/upNodesLinks with attacker-controlled UP-node and link payload), and delete (DELETE /upi/v1/upNodesLinks/{nodeID}) operations.

The defect is route-group-scoped: there is no inbound auth middleware on the UPI group at all, while a control comparison against the sibling nsmf-oam group on the same SMF instance shows OAM IS protected (no-token request returns 401 Unauthorized). So this is not a global config gap -- it is specifically that the UPI group was mounted without the auth middleware that the OAM group has.

Details

Validated against the SMF container in the official Docker compose lab.

  • Source repo tag: v4.2.1
  • Running Docker image: free5gc/smf:v4.2.0
  • Docker validation date: 2026-03-13

Control comparison on the same SMF instance:

  • GET /upi/v1/upNodesLinks (no token) -> 200 OK
  • GET /nsmf-oam/v1/ (no token) -> 401 Unauthorized

This side-by-side proves OAuth2 middleware is wired in for nsmf-oam but not for UPI on the same process.

Code evidence (paths in free5gc/smf):

  • UPI group mounted WITHOUT auth middleware: `NFs/smf/internal/sbi/server.go:7…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-44329 has been found in github.com/free5gc/smf.
Attackers can target a specific entry point like GET /upi/v1/upNodesLinks over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 10.0/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-44329" on the vendor's site.

CVE-2026-44329 (github.com/free5gc/smf) — CWE-306 / CVSS v3 10.0
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: GET /upi/v1/upNodesLinks / POST /upi/v1/upNodesLinks / DELETE /upi/v1/upNodesLinks/{nodeID} / GET /nsmf-oam/v1/
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 GET /upi/v1/upNodesLinks without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/free5gc/smf. Attack surface: GET /upi/v1/upNodesLinks / POST /upi/v1/upNodesLinks / DELETE /upi/v1/upNodesLinks/{nodeID} / GET /nsmf-oam/v1/.

🔥 Severity

Severity: Critical (CVSS 10.0/10). Data can be tampered with by attackers.

🔧 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 GET /upi/v1/upNodesLinks 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

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. 2
    Hunt for indicators of compromise detect 
    grep 'GET /upi/v1/upNodesLinks' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

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

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

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

  4. 4
    Post-deployment verification verify 
    Replay attack against GET /upi/v1/upNodesLinks on staging to confirm patch closes the vector

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

Affected packages

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

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details