CVE-2026-44319: Free5gc vulnerability (CVSS 7.5)

Description

free5GC is an open-source implementation of the 5G core network. Prior to 4.2.2, free5GC's NEF terminates the entire process when a stored PFD-subscription notifyUri cannot be reached. In PfdChangeNotifier.FlushNotifications(), the notifier calls NnefPFDmanagementNotify(...) and on any delivery error invokes logger.PFDManageLog.Fatal(err), which is os.Exit(1)-equivalent in Go. An attacker who can create a PFD subscription with an attacker-chosen notifyUri and then trigger a PFD change can deterministically kill NEF on the asynchronous delivery attempt -- the process exits with status 1, dropping NEF's entire SBI surface until restart. This vulnerability is fixed in 4.2.2.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityNone

IntegrityNone

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected products

Free5gc< 4.2.2

Remediation

Fixed in

Free5gc≥ 4.2.2

Patch & vendor advisories

References

https://github.com/free5gc/free5gc/issues/924ExploitIssue Tracking
https://github.com/free5gc/free5gc/security/advisories/GHSA-rxrq-fv76-26prExploitVendor Advisory
https://github.com/free5gc/nef/commit/f110517b1189801950b50668a593398687049074Patch
https://github.com/free5gc/nef/pull/25Issue TrackingPatch

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2026-44319 being actively exploited?

CVE-2026-44319 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.66%.

How severe is CVE-2026-44319?

CVE-2026-44319 has a CVSS 3.1 base score of 7.5, rated high. EPSS estimates a 0.66% probability of exploitation.

Which products are affected by CVE-2026-44319?

Affected products include Free5gc.

How do I fix CVE-2026-44319?

Upgrade affected software to a fixed version, for example Free5gc 4.2.2 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-44319 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo