CVE-2026-33064: free5GC UDM DataChangeNotification Procedure Panic Due to Nil Pointer Dereference

Published Mar 18, 2026
·
Updated

Impact This is a NULL Pointer Dereference vulnerability leading to Denial of Service. - Security Impact: A remote attacker can cause the UDM service to panic and crash by sending a crafted POST request to the /sdm-subscriptions endpoint with a malformed URL path containing path traversal sequences (../) and a large JSON payload. The DataChangeNotificationProcedure function in notifier.go attempts to access a nil pointer without proper validation, causing a complete service crash with "runtime error: invalid memory address or nil pointer dereference". - Functional Impact: The service crashes completely, requiring manual restart. All UDM functionality is disrupted until recovery. - Affected Parties: All deployments of free5GC v4.0.1 using the UDM HTTP callback functionality.

Patches Yes, the issue has been patched. The fix is implemented in PR free5gc/udm#78. Users should upgrade to the next release of free5GC that includes this commit.

Workarounds There is no direct workaround at the application level. The recommendation is to apply the provided patch or implement API gateway-level filtering to block requests containing path traversal sequences.

Other sources

Free5GC is an open-source Linux Foundation project for 5th generation (5G) mobile core networks. Versions prior to 1.4.2 are vulnerable to procedure panic caused by Nil Pointer Dereference in the /sdm-subscriptions endpoint. A remote attacker can cause the UDM service to panic and crash by sending a crafted POST request to the /sdm-subscriptions endpoint with a malformed URL path containing path traversal sequences (../) and a large JSON payload. The DataChangeNotificationProcedure function in notifier.go attempts to access a nil pointer without proper validation, causing a complete service crash with "runtime error: invalid memory address or nil pointer dereference". Exploitation would result in UDM functionality disruption until recovery by restart. This issue has been fixed in version 1.4.2.

MITRE

Affected Software

2 affected componentsFixes available
go/github.com/free5gc/udm<1.4.2
1.4.2
free5gc Udm Go<1.4.2

Event History

Mar 18, 2026
Advisory Published
via GitHub·08:06 PM
Data Sourced
via GitHub·08:06 PM
DescriptionWeaknessAffected Software
Mar 20, 2026
CVE Published
via MITRE·08:00 AM
Data Sourced
via MITRE·08:00 AM
DescriptionWeakness
Data Sourced
via NVD·08:16 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:16 AM
RemedyAffected Software
Mar 31, 58197
Event
via FIRST·04:47 AM

Frequently Asked Questions

1

What is the severity of CVE-2026-33064?

The severity of CVE-2026-33064 is high as it leads to Denial of Service due to a NULL Pointer Dereference.

2

How do I fix CVE-2026-33064?

To fix CVE-2026-33064, upgrade to free5GC UDM version 1.4.2 or later.

3

What vulnerability is associated with CVE-2026-33064?

CVE-2026-33064 is a NULL Pointer Dereference vulnerability in the free5GC UDM DataChangeNotification Procedure.

4

What impact does CVE-2026-33064 have on services?

CVE-2026-33064 can cause the UDM service to panic and crash, leading to service disruption.

5

Who can exploit CVE-2026-33064?

CVE-2026-33064 can be exploited by remote attackers by sending a crafted POST request.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203