CVE-2026-44317
This vulnerability is fixed in 4.2.2.
Does this matter?
Lower severity and a low EPSS score (0.35%). Track it; it rarely justifies an emergency change on its own.
Description
free5GC is an open-source implementation of the 5G core network. Prior to 4.2.2, free5GC's PCF POST /npcf-policyauthorization/v1/app-sessions handler panics on a single authenticated request whose ascReqData.suppFeat == "1" (enabling traffic-routing feature negotiation) and whose medComponents entries supply an afAppId but NO AfRoutReq. The create path then calls provisioningOfTrafficRoutingInfo(smPolicy, appID, routeReq, ...) with routeReq == nil and dereferences routeReq.RouteToLocs (and other fields) without a nil check, causing runtime error: invalid memory address or nil pointer dereference. Gin recovery converts the panic into HTTP 500. This vulnerability is fixed in 4.2.2.
- CVSS 3.1
- 6.5 MEDIUMCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- EPSS
- 0.35% probability · 28th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-476, CWE-754
- Affected
- free5gc/free5gc
- Source
- security-advisories@github.com
References
- https://github.com/free5gc/free5gc/issues/879Exploit, Issue Tracking
- https://github.com/free5gc/free5gc/security/advisories/GHSA-wwqh-7jm5-gj7wExploit, Vendor Advisory
- https://github.com/free5gc/pcf/commit/508d70b8527a6c8c923179dad450ea01e16b6aebPatch
- https://github.com/free5gc/pcf/pull/65Issue Tracking, Patch
- https://github.com/free5gc/free5gc/security/advisories/GHSA-wwqh-7jm5-gj7wExploit, Vendor Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.