CVE-2026-55068

free5GC: NRF nnrf-nfm lacks NF Profile input validation — enables NF Registration Poisoning with arbitrary service endpoints

Published Aug 28, 2026 CVSS 4.0 · 9.3 Critical EPSS < 1% KEV · Not listed
Description
free5GC is an open-source implementation of the 5G core network. In 4.2.2 and earlier, the NRF RegisterNFInstance handler at PUT /nnrf-nfm/v1/nf-instances/{nfInstanceID} accepts NF Profiles without enforcing UUID format, nfStatus enum values, heartBeatTimer ranges, mandatory profile fields, or nfServices.ipEndPoints address constraints. The invalid profiles are persisted in the MongoDB NfProfile collection and returned by NFDiscover, allowing an attacker with SBI access to advertise attacker-controlled network-function endpoints and redirect control-plane signaling. This can expose credentials and signaling, alter service discovery integrity, and deny service across network functions that trust the NRF. This issue is fixed in version 4.2.3.

Analysis

AI-generated

Technical impact

free5GC’s NRF RegisterNFInstance handler accepts NF Profiles without enforcing mandatory validation rules such as UUID format, nfStatus enum values, heartBeatTimer ranges, and endpoint address constraints. This lack of input validation allows an attacker to register malicious NF profiles that the NRF stores and later returns through NFDiscover. With an attacker‑controlled profile, the NRF can redirect control‑plane signaling to arbitrary service endpoints, exposing credentials, compromising signaling integrity, and potentially causing denial of service across network functions that trust the NRF. The weakness is classified as CWE‑20 (Improper Input Validation).

Affected Systems

The open‑source 5G core network implementation known as free5GC is affected. All releases through version 4.2.2, inclusive, contain the flaw. The problem was addressed in free5GC release 4.2.3 and subsequent versions. The vulnerability resides in the NRF component of the free5GC distribution.

Risk and Exploitability

The CVSS score of 9.3 indicates critical severity. EPSS data is not available, so the likelihood of exploitation remains uncertain, but the lack of input validation gives a clear attack path. An adversary with access to the NRF registration API (PUT /nnrf‑nfm/v1/nf‑instances/{nfInstanceID}) can craft arbitrary NF profiles, acquire the NRF’s stored payload, and redirect traffic. The vulnerability is not listed in CISA’s KEV catalog, suggesting there are currently no publicly known exploits, yet its high severity and the breadth of impact warrant close monitoring and swift remediation.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to free5GC version 4.2.3 or later to obtain the fixed profile validation logic.
  • Limit access to the NRF registration endpoint (PUT /nnrf‑nfm/v1/nf‑instances/{nfInstanceID}) by enforcing strong authentication and network segmentation, ensuring only legitimate NF instances can submit registrations.
  • Enable logging and audit of NF profile submissions; check for deviations from the expected profile schema, and consider blocking registrations that do not conform to the validated format.

Generated by OpenCVE AI on August 28, 2026 at 20:57 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-x8mj-6p3q-g5pp free5GC NRF nnrf-nfm lacks NF Profile input validation — enables NF Registration Poisoning with arbitrary service endpoints
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Free5gc
Free5gc free5gc
Vendors & Products Free5gc
Free5gc free5gc
Type Values Removed Values Added
Description free5GC is an open-source implementation of the 5G core network. In 4.2.2 and earlier, the NRF RegisterNFInstance handler at PUT /nnrf-nfm/v1/nf-instances/{nfInstanceID} accepts NF Profiles without enforcing UUID format, nfStatus enum values, heartBeatTimer ranges, mandatory profile fields, or nfServices.ipEndPoints address constraints. The invalid profiles are persisted in the MongoDB NfProfile collection and returned by NFDiscover, allowing an attacker with SBI access to advertise attacker-controlled network-function endpoints and redirect control-plane signaling. This can expose credentials and signaling, alter service discovery integrity, and deny service across network functions that trust the NRF. This issue is fixed in version 4.2.3.
Title free5GC: NRF nnrf-nfm lacks NF Profile input validation — enables NF Registration Poisoning with arbitrary service endpoints
Weaknesses CWE-20
References
Metrics cvssV4_0

{'score': 9.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-20

    Improper Input Validation

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Aug 31, 2026, 6:56 PM
Reserved
Jun 16, 2026, 2:33 PM
Status
Deferred
Published
Aug 28, 2026, 8:18 PM
Modified
Sep 8, 2026, 9:11 PM