Monitor vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
9.9

CVE-2026-55068: free5GC can register fake network functions

CVE-2026-55068 · published 6 days ago
Summary

Versions of free5GC up to 4.2.2 let anyone with access to the internal API add false network function records without proper validation. These bogus entries are stored and later returned to other components, potentially redirecting traffic to attacker‑controlled endpoints and exposing sensitive communications. Upgrade to version 4.2.3 or later to enforce proper checks and protect the network core.

What to do
  • Update free5gc github.com/free5gc/free5gc to version 4.2.2.
Affected software
Ecosystem VendorProductAffected versions
Go free5gc github.com/free5gc/free5gc < 4.2.2
Fix: upgrade to 4.2.2
Original advisory text
free5GC: NRF nnrf-nfm lacks NF Profile input validation — enables NF Registration Poisoning with arbitrary service endpoints
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.
Severity
9.9 Critical
CVSS 4.0: 9.9 (OSV)
Exploitation
EPSS <1%
Type
CWE-20Improper Input Validation
Timeline
Published28 Aug 2026
Updated3 Sep 2026
First seen28 Aug 2026
Monitor software like this
Free during beta