free5GC SMF versions up to 1.4.6 have a vulnerability where resources are not properly released after failed PDU session establishments, causing orphaned charging sessions on the CHF. This can degrade the availability of the CHF by accumulating unused sessions.
free5GC SMF through 1.4.6 contains a resource exhaustion vulnerability because sendPDUSessionEstablishmentAccept returns early without calling RemoveSMContextFromAllNF on failures. Authenticated UEs repeatedly establishing PDU sessions during NRF or AMF failures leak SM contexts, UE IP addresses and TEIDs, exhausting the DNN IP pool.
free5GC SMF through 1.4.6 contains a resource leak vulnerability in HandlePDUSessionSMContextCreate that leaves SM contexts unreleased when UDM access token retrieval fails. Attackers can trigger repeated PDU session establishment attempts while the NRF is unreachable, causing empty 200 responses and persistent SMF memory growth.
free5GC SMF through 1.4.6 contains a resource exhaustion vulnerability in HandlePDUSessionSMContextLocalRelease that orphans SM contexts and UE IP addresses when PFCP session deletion fails. Attackers can send repeated PDU session establishment requests reusing an existing SUPI and PDU Session ID during PFCP deletion failures to exhaust the DNN's UE IP pool.
CVE-2026-133702 is a medium-severity vulnerability in free5GC PCF versions up to 1.4.6. It involves a resource leak in the postAppSessCtxProcedure function, where PCC rules and QoS data remain in the SM policy decision after rejected Npcf_PolicyAuthorization create requests. Authenticated application functions (AFs) with knowledge of an active PDU session's UE address can exploit this by sending repeated failing requests with different AF application identifiers, causing memory growth and policy pollution in the SMF.
free5GC WebConsole through 1.4.6 contains an authorization flaw in the ChangePasswordInfo handler that allows authenticated tenant users to change other members' passwords. Attackers can send POST /api/change-password with another tenant member's email and a new password, without the current password, to take over that account.
CVE-2026-41136 is a medium severity vulnerability in free5GC AMF versions prior to 1.4.3. The issue arises because the HTTPUEContextTransfer handler lacks a default case for unsupported Content-Type headers, causing deserialization to be skipped silently and the processor to receive an uninitialized request object. This behavior violates expected processing logic and may lead to unexpected application behavior. A fix was introduced in version 1.4.3.
CVE-2026-41135 is a memory leak vulnerability in free5GC's Policy Control Function (PCF) affecting versions prior to 1.4.3. An unauthenticated attacker with network access to the PCF SBI interface can cause uncontrolled memory growth by repeatedly sending HTTP requests to the OAM endpoint. This occurs because a new CORS middleware is registered on every incoming request, causing the Gin router's handler chain to grow indefinitely. The resulting memory exhaustion leads to denial of service, preventing user equipment from obtaining necessary policies and blocking 5G session establishment. Version 1.4.3 includes a patch to fix this issue.
CVE-2026-40343 is a medium severity vulnerability in free5GC's user data repository (UDR) component up to version 1.4.2. The flaw involves improper handling of errors in the POST handler for the /nudr-dr/v2/policy-data/subs-to-notify endpoint, where the service continues processing requests despite failures in request body retrieval or deserialization. This can lead to unintended creation of policy data notification subscriptions with invalid or incomplete input. No patch or official remediation is available at the time of publication.
CVE-2026-33063 is a high-severity vulnerability in free5GC AUSF versions prior to 1.4.2, caused by improper null pointer handling in the UE authentication service. A remote attacker can send a crafted UE authentication request to the `/nausf-auth/v1/ue-authentications` endpoint, triggering a nil interface conversion in the `GetSupiFromSuciSupiMap` function. This causes the AUSF service to panic and crash, resulting in a denial of service (DoS). The root cause is the lack of a nil check before converting an interface{} to a pointer type, leading to a runtime panic. There is no direct application-level workaround, so patching to version 1.4.2 or later is essential. Restricting access to the AUSF API to trusted sources can mitigate exposure.
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.
CVE-2026-32937 is a high-severity vulnerability in free5GC's CHF component prior to version 1.2.2, caused by improper validation of array indexes leading to out-of-bounds slice access. An authenticated attacker can trigger a server-side panic via a crafted PUT request to the recharge endpoint, causing service disruption. While some deployments convert this panic into HTTP 500 errors, others may experience more severe outages. The vulnerability can be exploited repeatedly to degrade recharge functionality and flood logs, impacting availability. Mitigations include restricting access to trusted network functions, applying rate limiting, disabling the recharge API if unused, and ensuring panic recovery and monitoring are in place. This vulnerability affects 5G core network deployments using free5GC CHF, particularly in countries with active 5G infrastructure adopting open-source core solutions. The CVSS 4.0 score is 7.
free5GC UDR is the user data repository (UDR) for free5GC, an an open-source project for 5th generation (5G) mobile core networks. In versions up to and including 1.4.1, the NEF component reliably leaks internal parsing error details (e.g., invalid character 'n' after top-level value) to remote clients, which can aid attackers in service fingerprinting. All deployments of free5GC using the Nnef_PfdManagement service may be affected.free5gc/udr pull request 56 contains a patch for the issue. There is no direct workaround at the application level. The recommendation is to apply the provided patch.
free5gc UDM provides Unified Data Management (UDM) for free5GC, an open-source project for 5th generation (5G) mobile core networks. In versions up to and including 1.4.1, remote attackers can inject control characters (e.g., %00) into the supi parameter, triggering internal URL parsing errors (net/url: invalid control character). This exposes system-level error details and can be used for service fingerprinting. All deployments of free5GC using the UDM Nudm_UEAU service may be affected.free5gc/udm pull request 75 contains a fix for the issue. No direct workaround is available at the application level. Applying the official patch is recommended.
free5GC SMF provides Session Management Function for free5GC, an open-source project for 5th generation (5G) mobile core networks. In versions up to and including 1.4.1, SMF panics and terminates when processing a malformed PFCP SessionReportRequest on the PFCP (UDP/8805) interface. No known upstream fix is available, but some workarounds are available. ACL/firewall the PFCP interface so only trusted UPF IPs can reach SMF (reduce spoofing/abuse surface); drop/inspect malformed PFCP SessionReportRequest messages at the network edge where feasible, and/or add recover() around PFCP handler dispatch to avoid whole-process termination (mitigation only).
free5GC SMF provides Session Management Function for free5GC, an open-source project for 5th generation (5G) mobile core networks. In versions up to and including 1.4.1, SMF panics and terminates when processing a malformed PFCP SessionReportRequest on the PFCP (UDP/8805) interface. No known upstream fix is available, but some workarounds are available. ACL/firewall the PFCP interface so only trusted UPF IPs can reach SMF (reduce spoofing/abuse surface); drop/inspect malformed PFCP SessionReportRequest messages at the network edge where feasible, and/or add recover() around PFCP handler dispatch to avoid whole-process termination (mitigation only).
free5GC SMF provides Session Management Function for free5GC, an open-source project for 5th generation (5G) mobile core networks. In versions up to and including 1.4.1, SMF panics due to nil pointer dereference and the SMF process terminates. This is triggered by a malformed PFCP SessionReportRequest on the SMF PFCP (UDP/8805) interface. No known upstream fix is available, but some workarounds are available. ACL/firewall the PFCP interface so only trusted UPF IPs can reach SMF (reduce spoofing/abuse surface); drop/inspect malformed PFCP SessionReportRequest messages at the network edge where feasible, and/or add recover() around PFCP handler dispatch to avoid whole-process termination (mitigation only).
free5GC is an open-source project for 5th generation (5G) mobile core networks. Versions up to and including 1.4.1 of the User Data Repository are affected by Improper Error Handling with Information Exposure. The NEF component reliably leaks internal parsing error details (e.g., invalid character 'n' after top-level value) to remote clients, which can aid attackers in service fingerprinting. All deployments of free5GC using the Nnef_PfdManagement service may be vulnerable.free5gc/udr pull request 56 contains a patch. No direct workaround is available at the application level. Applying the official patch is recommended.
free5gc UDM provides Unified Data Management (UDM) for free5GC, an open-source project for 5th generation (5G) mobile core networks. Versions up to and including 1.4.1 have a NULL Pointer Dereference vulnerability. Remote unauthenticated attackers can trigger a service panic (Denial of Service) by sending a crafted PUT request with an unexpected ueId, crashing the UDM service. All deployments of free5GC using the UDM component may be affected.free5gc/udm pull request 76 contains a fix for the issue. No direct workaround is available at the application level. Applying the official patch is recommended.
free5gc UDM provides Unified Data Management (UDM) for free5GC, an open-source project for 5th generation (5G) mobile core networks. In versions up to and including 1.4.1, remote attackers can inject control characters (e.g., %00) into the ueId parameter, triggering internal URL parsing errors (net/url: invalid control character). This exposes system implementation details and can aid in service fingerprinting. All deployments of free5GC using the UDM Nudm_UECM service may be affected.free5gc/udm pull request 76 contains a fix for the issue. No direct workaround is available at the application level. Applying the official patch is recommended.