Quick answers
- Is CVE-2026-44324 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44324 being exploited in the wild.
- How severe is CVE-2026-44324?
- Medium severity, with a CVSS score of 6.5, published 27 May 2026.
- Which products and versions are affected?
- free5GC Udr < 1.4.3, <= 4.2.1; github.com/free5gc/udr (Go) < 1.4.3, SEMVER:introduced=0,fixed=1.4.3.
- Is there a fix for CVE-2026-44324?
- Yes. github.com/free5gc/udr (Go): upgrade to 1.4.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-44324 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-44324?
- Check whether you run free5GC Udr or github.com/free5gc/udr (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- github.com/free5gc/udr (Go): upgrade to 1.4.3 or later
go get github.com/free5gc/udr@v1.4.3
Technical details
The vulnerability is a Go nil interface type assertion (CWE-704) in the RemoveAmfSubscriptionsInfoProcedure of the UDR component. When a DELETE request is made to the amf-subscriptions endpoint with a non-existent ueId, the code correctly identifies the missing user but fails to return early. It subsequently attempts a type assertion on a nil interface returned by sync.Map.Load, causing a panic. While the Gin framework recovers from the panic to prevent a full process crash, the endpoint remains susceptible to repeated authenticated DoS attacks. The issue is fixed in version 1.4.3.
Affected products
- free5GC udr < 1.4.3
Identifiers
- CVE-2026-44324
- GHSA-jqfc-gwj5-3w63
- GO-2026-5478
Timeline
- 2026-03-22: other: Vulnerability validated in lab environment
- 2026-05-07: disclosed
- 2026-05-08: advisory
- 2026-05-27: other: NVD published date