Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-44322 high CVSS 7.5

Vulnerability in github.com/free5gc/nef (CVE-2026-44322)

Summary

Vulnerability in github.com/free5gc/nef (CVE-2026-44322). Risk of unauthorized operations or information disclosure. Exploitable via PATCH /3gpp-pfd-management/v1/{afId}/transactions/{transId}/applications/{appId}. Mitigation: upgrade to 1.2.3 or later.

Original description

The description as published by the source.

Summary

free5GC's NEF PATCH /3gpp-pfd-management/v1/{afId}/transactions/{transId}/applications/{appId} handler panics with a nil-pointer dereference when the upstream UDR call fails AND the consumer wrapper returns err != nil together with a nil *ProblemDetails. The handler's errPfdData != nil branch builds its own problemDetailsErr correctly, but immediately after it reads problemDetails.Cause (the OTHER value, which is nil in this branch) and panics. Gin recovery converts the panic into HTTP 500, so a single PATCH against this endpoint returns 500 instead of the intended controlled error response whenever UDR access is failing.

This is a second-order bug: the trigger requires UDR access to be failing (e.g. NRF or UDR is unreachable, registration broken, transient network failure). The attacker does not directly control that condition, so this is scored as AC:H. Once the upstream condition exists, the trigger is a single PATCH request and is repeatable.

The HTTP request itself in v4.2.1 is reachable without an Authorization header because the underlying NEF 3gpp-pfd-management route group is mounted without inbound auth middleware (see free5gc/free5gc#858). So in the validation lab the entire trigger chain is unauthenticated end-to-end.

Details

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

  • Source repo tag: v4.2.1
  • Running Docker image: free5gc/nef:v4.2.1
  • Runtime NEF commit: 5ce35eab
  • Docker validation date: 2…

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-44322 has been found in github.com/free5gc/nef.
Attackers can target a specific entry point like PATCH /3gpp-pfd-management/v1/{afId}/transactions/{transId}/applications/{appId} over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade github.com/free5gc/nef to 1.2.3 or later.
If unsure, ask your IT team or search "github.com/free5gc/nef CVE-2026-44322" on the vendor's site.

CVE-2026-44322 (github.com/free5gc/nef) — CWE-476 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: PATCH /3gpp-pfd-management/v1/{afId}/transactions/{transId}/applications/{appId} / Authorization header / problemDetailsErr / problemDetails.Cause
Patched: 1.2.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-476) exists in github.com/free5gc/nef. Attackers reach the vulnerable code path via PATCH /3gpp-pfd-management/v1/{afId}/transactions/{transId}/applications/{appId} without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/free5gc/nef. Attack surface: PATCH /3gpp-pfd-management/v1/{afId}/transactions/{transId}/applications/{appId} / Authorization header / problemDetailsErr / problemDetails.Cause.

🔥 Severity

Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.2.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 PATCH /3gpp-pfd-management/v1/{afId}/transactions/{transId}/applications/{appId} requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/free5gc/nef' . 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/nef' . | grep -v node_modules

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

  2. 2
    Hunt for indicators of compromise detect 
    grep 'PATCH /3gpp-pfd-management/v1/{afId}/transactions/{transId}/applications/{appId}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで PATCH /3gpp-pfd-management/v1/{afId}/transactions/{transId}/applications/{appId} への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch 
    Upgrade github.com/free5gc/nef to 1.2.3

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

  4. 4
    Post-deployment verification verify 
    Replay attack against PATCH /3gpp-pfd-management/v1/{afId}/transactions/{transId}/applications/{appId} on staging to confirm patch closes the vector

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

Affected packages

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

References

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