# 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.

- **Severity:** Critical 9.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** GHSA-x8mj-6p3q-g5pp, GO-2026-6316

## 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 (Improper Input Validation)

## Which versions are affected by CVE-2026-55068?

3 open source packages ship an affected version, including github.com/free5gc/free5gc.


| Package | Ecosystem | 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.

## Is CVE-2026-55068 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55068 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-55068 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55068 exists.

Affected packages and fixed versions:
- github.com/free5gc/free5gc (Go): affected all versions; fixed in 4.2.2
- github.com/free5gc/free5gc (Go): affected all versions; fixed in 4.2.2
- github.com/free5gc/free5gc (Go): affected all versions; fixed in 4.2.2+incompatible

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-55068/ (Markdown: https://insights.sbomify.com/CVE-2026-55068/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-55068
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-55068
- OSV: https://osv.dev/vulnerability/CVE-2026-55068

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-55068/
Summaries are generated and may contain mistakes; the official description above is the record.