CVE-2026-55068
NRF input-validation flaw lets attacker register malicious NF profiles and redirect control-plane signaling.
Is CVE-2026-55068 being exploited?
Not confirmed. CVE-2026-55068 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.44% probability of exploitation in the next 30 days.
How severe is CVE-2026-55068?
CVE-2026-55068 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-55068?
Yes. A fix has been recorded for CVE-2026-55068. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-55068 affect?
CVE-2026-55068 affects free5GC <= 4.2.2, nrf component (PUT /nnrf-nfm/v1/nf-instances/{nfInstanceID}), MongoDB NfProfile collection, SBI-exposed 5G core deployments. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-55068?
Upgrade to free5GC v4.2.3; restrict/segregate SBI access, validate NF registrations, rotate exposed credentials.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker with SBI access can register attacker-controlled NF endpoints, redirect control-plane signaling, expose credentials, tamper service discovery, and cause service disruption.
Immediate action required
- affected< 4.2.3
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.