free5GC: UDR Improper ueId validation in free5GC EE subscription handlers allows arbitrary identifier persistence

Summary

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.

Timeline

1. Sep 15, 2026, 2:43 PM UTCCVE published
2. Sep 15, 2026, 3:25 PM UTCCISA SSVC assessment

   Exploitation: poc · Automatable: yes · Technical impact: partial

3. Sep 15, 2026, 3:25 PM UTCRecord last updated

Affected versions

• free5gc free5gc

  through 4.2.2

• github.com/free5gc/udrGo

  All versions

• github.com/free5gc/udrGo

  through 1.4.3

References 1