CVE-2026-55068 free5GC NRF nnrf-nfm lacks NF Profile input validation — enables NF Registration Poisoning with arbitrary service endpoints
Attackers can register malicious network functions in free5GC NRF to redirect signaling, exposing credentials and causing service disruption.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-55068?
CVE-2026-55068 is a critical missing authorization vulnerability in free5gc, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official 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.
Weakness: CWE-20
Which versions are affected by CVE-2026-55068?
3 open source packages ship an affected version, including github.com/free5gc/free5gc.
| Package | Affected | Fixed in |
|---|---|---|
github.com/free5gc/free5gc Go | All versions | 4.2.2 |
github.com/free5gc/free5gc Go | All versions | 4.2.2 |
github.com/free5gc/free5gc Go | All versions | 4.2.2+incompatible |
How do I fix CVE-2026-55068?
Upgrade github.com/free5gc/free5gc to a fixed version for your release line: 4.2.2 or 4.2.2+incompatible.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2026-55068 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55068 exists.
Sources
Also known as GHSA-x8mj-6p3q-g5pp, GO-2026-6316.