CVE-2026-44317
free5GC is an open-source implementation of the 5G core network. …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/free5gc/free5gc/security/advisories/GHSA-wwqh-7jm5-gj7w
- github.com/free5gc/free5gc/issues/879
- github.com/free5gc/pcf/pull/65
- github.com/free5gc/pcf/commit/508d70b8527a6c8c923179dad450ea01e16b6aeb
- github.com/advisories/GHSA-wwqh-7jm5-gj7w
- nvd.nist.gov/vuln/detail/CVE-2026-44317
- nvd.nist.gov/vuln/detail/CVE-2026-44317
- cve.org/CVERecord?id=CVE-2026-44317
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.