Unauthorized record creation via catch-all ueId validation
Published Sep 15, 2026 · Updated Sep 15, 2026
Improper input validation in free5GC UDR 4.2.2 and earlier allows remote attackers to persist arbitrary EE subscription identifiers. HandleCreateEeSubscriptions and HandleQueryeesubscriptions use a ueId regular expression whose final .+ alternative accepts every nonempty value instead of only supported SUPI and GPSI formats. Network access to the UDR SBI is sufficient; accepted identifiers enter the normal create or query flow and can pollute stored subscriber metadata.
Summary
What happened
Improper input validation in free5GC UDR 4.2.2 and earlier allows remote attackers to persist arbitrary EE subscription identifiers. HandleCreateEeSubscriptions and HandleQueryeesubscriptions use a ueId regular expression whose final .+ alternative accepts every nonempty value instead of only supported SUPI and GPSI formats. Network access to the UDR SBI is sufficient; accepted identifiers enter the normal create or query flow and can pollute stored subscriber metadata.
The record
- CVE
- CVE-2026-47780
- Published
- Sep 15, 2026
- Updated
- Sep 15, 2026
- Vendor
- free5GC
- Product
- free5GC
- Classifications
- CWE-20, T1565.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 15, 2026CVE publishedPublication date reported by the CVE source.
- Sep 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=<= 4.2.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- GitHub advisory HTTP proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo