Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-55068 – NF Registration Poisoning / Signaling Traffic Redirection – free5GC NRF (≤ 4.2.2)

Be the first to know when new zero-days emerge:

Summary

CVE-2026-55068 is a critical improper input validation vulnerability (CWE-20) in the Network Repository Function (NRF) of free5GC, an open-source 5G core network implementation. The NRF’s RegisterNFInstance handler accepts Network Function (NF) profiles without enforcing 3GPP TS 29.510 field constraints, allowing an attacker with access to the Service-Based Interface (SBI) to register fraudulent NF profiles with attacker-controlled service endpoints. The issue is rated CRITICAL with a CVSS v4.0 base score of 9.3.

Technical details

  • Root cause: the NRF endpoint PUT /nnrf-nfm/v1/nf-instances/{nfInstanceID} accepts NF Profiles without enforcing UUID format for nfInstanceId, valid nfStatus enum values, heartBeatTimer range limits, presence of mandatory profile fields, or address constraints on nfServices.ipEndPoints.
  • Trigger condition: an attacker with network access to the SBI can submit a crafted NF registration request; malformed and malicious profiles are accepted and persisted (returning HTTP 200/201) rather than being rejected.
  • Attack vector: network-based, no privileges or user interaction required.
  • Impact: the invalid/malicious NF profiles are stored in the NRF’s backing datastore and returned to legitimate NFs via NFDiscover, enabling "NF Registration Poisoning." Attacker-controlled endpoints can be advertised as legitimate network functions, allowing interception of control-plane signaling, harvesting of OAuth2 credentials, and denial of service to subscribers relying on NFs that trust the NRF.

Affected software

  • free5GC (github.com/free5gc/free5gc) versions prior to 4.2.3
  • free5GC NRF component (github.com/free5gc/nrf) versions prior to 1.4.5

Severity

CVSS v4.0 Base Score: 9.3 (Critical)
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

Mitigation and recommended actions

  • Immediate: Upgrade free5GC to version 4.2.3 or later, and the NRF component to v1.4.5 or later, which add validation for UUID format, enum values, numeric ranges, mandatory fields, and IP endpoint constraints on NF registration requests.
  • If patching is not immediately possible: restrict network access to the SBI (Service-Based Interface) to trusted network functions only, place the NRF behind strict network segmentation/firewalling so untrusted hosts cannot reach nnrf-nfm endpoints, and monitor NF registrations/NFDiscover results for unexpected or malformed NF profiles.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge