CVE Catalog

CVE-2026-44317

MediumCVSS 6.5
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.58%

47th percentile - higher than 47% of all known CVEs

Summary

In free5GC prior to 4.2.2, the PCF POST /npcf-policyauthorization/v1/app-sessions handler panics on a single authenticated request where ascReqData.suppFeat == "1" and medComponents entries supply an afAppId but no AfRoutReq. It causes a nil pointer dereference and HTTP 500.

Risk Assessment

An authenticated attacker can trigger a panic, leading to denial of service. This may disrupt 5G network operations.

Recommendation

Upgrade free5GC to version 4.2.2, which fixes this vulnerability. Restrict access to PCF endpoints to trusted entities.

Other vulnerabilities in free5GC

See all
Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS