Is CVE-2026-44322 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-44322 being exploited in the wild.

How severe is CVE-2026-44322?

High severity, with a CVSS score of 7.5, published 27 May 2026.

Which products and versions are affected?

free5GC NEF < 1.2.3, <= 4.2.1; github.com/free5gc/nef (Go) < 1.2.3, SEMVER:introduced=0,fixed=1.2.3.

Is there a fix for CVE-2026-44322?

Yes. github.com/free5gc/nef (Go): upgrade to 1.2.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-44322 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-44322?

Check whether you run free5GC NEF or github.com/free5gc/nef (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.

CVE-2026-44322: free5GC NEF NULL pointer dereference in PFD management handler

Q: Which products and versions are affected?

free5GC NEF < 1.2.3, <= 4.2.1; github.com/free5gc/nef (Go) < 1.2.3, SEMVER:introduced=0,fixed=1.2.3.

Q: Is there a fix for CVE-2026-44322?

Yes. github.com/free5gc/nef (Go): upgrade to 1.2.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-44322 attacked?

It is attacked over the network, in a hosted service.

Q: Am I affected by CVE-2026-44322?

Check whether you run free5GC NEF or github.com/free5gc/nef (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.

CVE-2026-44322 · Severity: high · CVSS 7.5 · Published 2026-05-27

A vulnerability in the free5GC Network Exposure Function (NEF) can cause the service to crash internally when processing specific update requests. This occurs when the system attempts to handle a failure from an upstream database component but incorrectly references missing data. While the service automatically recovers from the crash, it results in a failed request (HTTP 500 error) and could be used to disrupt specific management operations.

Technologies: free5GC NEF, github.com/free5gc/nef (Go). Vendors: free5GC, Go.

Quick answers

Is CVE-2026-44322 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-44322 being exploited in the wild.
How severe is CVE-2026-44322?: High severity, with a CVSS score of 7.5, published 27 May 2026.
Which products and versions are affected?: free5GC NEF < 1.2.3, <= 4.2.1; github.com/free5gc/nef (Go) < 1.2.3, SEMVER:introduced=0,fixed=1.2.3.
Is there a fix for CVE-2026-44322?: Yes. github.com/free5gc/nef (Go): upgrade to 1.2.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-44322 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-44322?: Check whether you run free5GC NEF or github.com/free5gc/nef (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/nef (Go): upgrade to 1.2.3 or later
```
go get github.com/free5gc/nef@v1.2.3
```

Technical details

A NULL pointer dereference (CWE-476) exists in the free5GC NEF 'PatchIndividualApplicationPFDManagement' handler. When an upstream Unified Data Repository (UDR) call fails, the error handling branch incorrectly attempts to access a field ('Cause') from a nil 'problemDetails' object instead of the locally initialized error object. This vulnerability is reachable via unauthenticated PATCH requests to the 3gpp-pfd-management API because the route group lacks mandatory authorization middleware in affected versions. While the Gin web framework's recovery middleware prevents a full process exit by converting the panic into an HTTP 500 response, an attacker can reliably trigger this state whenever upstream UDR connectivity is unstable or failing. The issue is fixed in NEF version 1.2.3.

Affected products

free5GC NEF < 1.2.3

Identifiers

CVE-2026-44322
GHSA-j59f-x285-69jx
GO-2026-5447

Timeline

2026-03-21: other: Vulnerability validated in lab environment
2026-05-08: disclosed
2026-05-08: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.