Skip to main content
VulnerabilityPublished Updated

CVE-2026-33062: free5gc nrf · Improper Access Control

Affects free5gc nrfSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.7 High : upgrade to 1.4.2 soon.

Data as of 1 Nov 2026, 08:20 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.4.2
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 31 Oct 2026.

What to do

Upgrade nrf and free5gc/nrf to 1.4.2.

Affected software

ProductAffectedFixed in
free5gcnrfAffected
  • <1.4.2
Fixed in
  • 1.4.2
GitHubfree5gc/nrfpkg:github/free5gc/nrfOther threatsAffected
  • <1.4.2
Fixed in
  • 1.4.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2026-33062, organizations should immediately upgrade free5GC NRF to version 1.4.2 or later, where the input validation flaw has been corrected. In environments where immediate patching is not feasible, network administrators should implement strict access controls to limit NRF API exposure only to trusted and authenticated sources, such as internal network segments or VPNs. Deploying Web Application Firewalls (WAFs) or API gateways with input validation rules to detect and block malformed group-id-list parameters can provide additional protection. Monitoring NRF service logs and network traffic for unusual or malformed requests targeting the group-id-list parameter can help detect attempted exploitation. Network segmentation and zero-trust principles should be applied to isolate the NRF service from untrusted networks. Finally, organizations should incorporate this vulnerability into their incident response and vulnerability management processes to ensure timely remediation and awareness.

Description

free5GC is an open source 5G core network.free5GC NRF prior to version 1.4.2 has an Improper Input Validation vulnerability leading to Denial of Service. All deployments of free5GC using the NRF discovery service are affected. The `EncodeGroupId` function attempts to access array indices [0], [1], [2] without validating the length of the split data. When the parameter contains insufficient separator characters, the code panics with "index out of range". A remote attacker can cause the NRF service to panic and crash by sending a crafted HTTP GET request with a malformed `group-id-list` parameter. This results in complete denial of service for the NRF discovery service.free5GC NRF version 1.4.2 fixes the issue. There is no direct workaround at the application level. The recommendation is to apply the provided patch or restrict access to the NRF API to trusted sources only.

References

Community reviews

Loading reviews…