Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-55068

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

Summary

Vulnerability in github.com/free5gc/free5gc (CVE-2026-55068). Risk of unauthorized operations or information disclosure. Exploitable via RegisterNFInstance. Mitigation: upgrade to 4.2.2 or later.

Original description

The description as published by the source.

Summary

free5GC NRF (Docker image free5gc-fuzz:latest) accepts NF registration requests without validating any field constraints against 3GPP TS 29.510, allowing unauthenticated attackers to inject fake NF profiles with arbitrary service endpoint IP addresses. All 17 constraint violations tested (UUID format, enum values, numeric ranges, mandatory fields, IP endpoint integrity) were accepted with HTTP 200/201. Legitimate NFs discover these fake profiles via NFDiscover and route control-plane traffic to attacker-controlled endpoints, an attacker with SBI network access can intercept control-plane signaling, harvest OAuth2 credentials, and deny service to subscribers.

Details

free5GC NRF's RegisterNFInstance handler (PUT /nnrf-nfm/v1/nf-instances/{nfInstanceID}) accepts the full NF profile body without field-level validation. The following 3GPP TS 29.510 constraints are violated:

Format validation: nfInstanceId accepts non-UUID strings (e.g., "not-a-uuid", "11111111-1111-1111-1111-111111111111"), violating TS 29.510 §6.1.6.2.2 UUID v4 requirement.

Enum validation: nfStatus accepts values outside the {REGISTERED, SUSPENDED, UNDISCOVERABLE} enum (e.g., "INVALID_STATUS").

Range validation: heartBeatTimer accepts values outside the valid range [1, 3600] (e.g., 0, 99999), violating TS 29.510 §5.2.2.2.

Mandatory field enforcement: nfProfile is accepted as null, violating the required field constraint in §5.2.2.2.

**Servic…

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-55068 has been found in github.com/free5gc/free5gc.
Attackers can target a specific entry point like RegisterNFInstance over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/free5gc/free5gc to 4.2.2 or later.
If unsure, ask your IT team or search "github.com/free5gc/free5gc CVE-2026-55068" on the vendor's site.

CVE-2026-55068 (github.com/free5gc/free5gc) — CWE-20
Attack surface: RegisterNFInstance / nfInstanceId / nfStatus / heartBeatTimer
Patched: 4.2.2 — 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-20) exists in github.com/free5gc/free5gc. Attackers reach the vulnerable code path via RegisterNFInstance.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/free5gc/free5gc. Attack surface: RegisterNFInstance / nfInstanceId / nfStatus / heartBeatTimer.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 4.2.2.

🛡️ 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 'github.com/free5gc/free5gc' . 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/free5gc' . | grep -v node_modules

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

  2. 2
    Apply patch patch 
    Upgrade github.com/free5gc/free5gc to 4.2.2

    ステージング環境で 4.2.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

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

Affected packages

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

References

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