Internal error exposure via empty subscriber identifier
Published Mar 20, 2026 · Updated Mar 20, 2026
Improper error handling in free5GC UDM before 1.4.2 allows remote attackers to expose internal error behavior via a malformed DELETE request. The HandleUnsubscribe path accepts an empty ueId, forwards it to UDR, and converts UDR's 400 response into a 500 SYSTEM_FAILURE response. The UDM service-based interface must be network-reachable; the observable consequence is limited to error classification and internal handling disclosure, with no reported data access or service interruption.
Summary
What happened
Improper error handling in free5GC UDM before 1.4.2 allows remote attackers to expose internal error behavior via a malformed DELETE request. The HandleUnsubscribe path accepts an empty ueId, forwards it to UDR, and converts UDR's 400 response into a 500 SYSTEM_FAILURE response. The UDM service-based interface must be network-reachable; the observable consequence is limited to error classification and internal handling disclosure, with no reported data access or service interruption.
The record
- CVE
- CVE-2026-33065
- Published
- Mar 20, 2026
- Updated
- Mar 20, 2026
- Vendor
- free5GC
- Product
- free5GC
- Classifications
- CWE-209
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 20, 2026CVE publishedPublication date reported by the CVE source.
- Mar 20, 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=< 1.4.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.
Weakness, pattern, technique
Public exploit references
- GitHub issue 783 reproduction requestproof 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