CVE-2026-44319 json
free5GC: NEF crashes via logger.Fatal on PFD notification delivery failure (attacker-controlled notifyUri)
published 2026-05-08 6 mo ago modified 2026-10-14 25 d ago also EUVD-2026-32579 , GHSA-rxrq-fv76-26pr , GO-2026-5647
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 34%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go github.com/free5gc/nef 1.2.3
- free5gc free5gc 4.2.2
- free5gc smf 4.2.2
- free5gc upf 4.2.2
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
opensuse advisories openSUSE-SU-2026:21483-1
- github.com/free5gc/nef@f110517 commit
- github.com/free5gc/nef#25 pull request
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 5 mo ago
Exploit prediction
0.40% chance of exploitation in the next 30 days, higher than 34% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/free5gc/free5gc/security/advisories/GHSA-rxrq-fv76-26pr referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/free5gc/free5gc/issues/924 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/free5gc/nef | <1.2.3 |
1.2.3 |
Affected products
- free5gc free5gc
Classification
References
-
github.com
/free5gc/nef/pull/25
web, issue-tracking, patch
-
github.com
/free5gc/nef/commit/f110517b1189801950b50668a593398687049074
web, patch
-
github.com
/free5gc/free5gc/security/advisories/GHSA-rxrq-fv76-26pr
exploit, web, vendor-advisory, advisory
-
github.com
/free5gc/free5gc/issues/924
exploit, web, issue-tracking
-
nvd.nist.gov
/vuln/detail/CVE-2026-44319
advisory
-
github.com
/free5gc/free5gc
package
Sources
- CVE List CVE-2026-44319
- GitHub Advisory GHSA-rxrq-fv76-26pr
- NVD CVE-2026-44319
- OSV GO-2026-5647
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.