free5GC up to 4.2.2 SBI API Data Repository api_datarepository.go ueId input validation

Summaryinfo

A vulnerability classified as critical was found in free5GC up to 4.2.2. Affected by this vulnerability is the function HandleCreateEeSubscriptions/HandleQueryeesubscriptions of the file internal/sbi/api_datarepository.go of the component SBI API Data Repository. The manipulation of the argument ueId results in input validation. This vulnerability is known as CVE-2026-47780. It is possible to launch the attack remotely. No exploit is available.

Detailsinfo

A vulnerability was found in free5GC up to 4.2.2. It has been classified as critical. Affected is the function HandleCreateEeSubscriptions/HandleQueryeesubscriptions of the file internal/sbi/api_datarepository.go of the component SBI API Data Repository. The manipulation of the argument ueId with an unknown input leads to a input validation vulnerability. CWE is classifying the issue as CWE-20. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

free5GC is an open-source implementation of the 5G core network. In 4.2.3 and earlier, HandleCreateEeSubscriptions and HandleQueryeesubscriptions in free5gc/udr internal/sbi/api_datarepository.go validate the ueId path value with a regular expression whose final .+ alternative accepts every non-empty string instead of restricting identifiers to supported SUPI and GPSI formats. An actor with network reachability to the UDR SBI can submit a non-3GPP identifier to /nudr-dr/v2/subscription-data/{ueId}/context-data/ee-subscriptions, causing the identifier to pass validation and enter the normal create or query flow. The advisory does not independently establish whether authentication is required. Invalid identifiers can be persisted and retrieved as subscription records, enabling unauthorized data creation, UDR namespace pollution, persistent subscriber-metadata corruption, and interference with downstream components that trust stored identifiers to use valid 3GPP formats. The exposure is most relevant in lab, test, or loosely segmented service-based-interface deployments where direct UDR access is possible.

The advisory is available at github.com. This vulnerability is traded as CVE-2026-47780 since 05/20/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 09/15/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Name

• free5GC

Version

• 4.2.0
• 4.2.1
• 4.2.2

Website

• Product: https://github.com/free5gc/free5gc/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion