free5GC NRF Discovery EncodeGroupId Function Panics on Malformed group-id-list Parameter

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.7 · 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 · score source

EPSS

• CVE-2026-33062: 0.69% estimated exploitation activity in the next 30 days; percentile 52.92 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact This is an Improper Input Validation vulnerability leading to Denial of Service. - Security Impact: 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. - Functional Impact: 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". - Affected Parties: All deployments of free5GC v4.0.1 using the NRF discovery service. Patches Yes, the issue has been patched. The fix is implemented in PR free5gc/nrf#80 (commit: [add fix reference here]). Users should upgrade to the next release of free5GC that includes this commit. Workarounds There is no direct workaround at the application level. The recommendation is to apply the provided patch or restrict access…

Published by the source

18 Mar 2026, 20:05 UTC

Last modified by the source

20 Mar 2026, 21:20 UTC

Source last checked

26 Oct 2026, 15:18 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-7c47-xr7q-p6hg

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

# Patch Next advisory brief: CVE-2026-33062

Advisory: free5GC NRF Discovery EncodeGroupId Function Panics on Malformed group-id-list Parameter
IDs: CVE-2026-33062, GHSA-7c47-xr7q-p6hg
Record: https://patchnext.com/advisories/cve-2026-33062 (revision 1, source checked 26 Oct 2026, 15:18 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
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/nrf 1.4.2. A vendor fix does not mean a deployment is fixed.

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

## Suggested inspection (read-only)
- Go github.com/free5gc/nrf: 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/nrf.
- 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://github.com/advisories/GHSA-7c47-xr7q-p6hg (GitHub-reviewed advisory GHSA-7c47-xr7q-p6hg lists affected ranges: Go github.com/free5gc/nrf >=0 <1.4.2)

Commands are suggestions: review each one before running it.