Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.3amended

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

CVE-2026-55068GHSA-x8mj-6p3q-g5pp

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/free5gc/free5gc 4.2.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
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 · score source
EPSS
  • CVE-2026-55068: 0.59% estimated exploitation activity in the next 30 days; percentile 48.25 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary free5GC NRF (Docker image free5gc-fuzz:latest) accepts NF registration requests without validating any field constraints against 3GPP TS 29.510, allowing unauthenticated attackers to inject fake NF profiles with arbitrary service endpoint IP addresses. All 17 constraint violations tested (UUID format, enum values, numeric ranges, mandatory fields, IP endpoint integrity) were accepted with HTTP 200/201. Legitimate NFs discover these fake profiles via NFDiscover and route control-plane traffic to attacker-controlled endpoints, an attacker with SBI network access can intercept control-plane signaling, harvest OAuth2 credentials, and deny service to subscribers. --- Details free5GC NRF's RegisterNFInstance handler (PUT /nnrf-nfm/v1/nf-instances/{nfInstanceID}) accepts the full NF profile body without field-level validation. The following 3GPP TS 29.510 constraints are violated: Format validation: nfInstanceId accepts non-UUID strings (e.g., "not-a-uuid",…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-x8mj-6p3q-g5pp

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GO-2026-6316

  4. Revision 1 · created ·

    Published from osv record GHSA-x8mj-6p3q-g5pp

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-55068

Advisory: free5GC NRF nnrf-nfm lacks NF Profile input validation — enables NF Registration Poisoning with arbitrary service endpoints
IDs: CVE-2026-55068, GHSA-x8mj-6p3q-g5pp
Record: https://patchnext.com/advisories/cve-2026-55068 (revision 4, source checked 26 Oct 2026, 15:28 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/free5gc/free5gc 4.2.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/free5gc/free5gc: affected < 4.2.2; fixed in 4.2.2

## Suggested inspection (read-only)
- Go github.com/free5gc/free5gc: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/free5gc/free5gc.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-x8mj-6p3q-g5pp (OSV record GHSA-x8mj-6p3q-g5pp lists affected ranges: Go github.com/free5gc/free5gc >=0 <4.2.2 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6316 (OSV record GO-2026-6316 lists affected ranges: Go github.com/free5gc/free5gc >=0 <4.2.2+incompatible (fixed))
- Verified: https://github.com/advisories/GHSA-x8mj-6p3q-g5pp (GitHub-reviewed advisory GHSA-x8mj-6p3q-g5pp lists affected ranges: Go github.com/free5gc/free5gc >=0 <4.2.2)

Commands are suggestions: review each one before running it.

Loading voting…