CVE-2026-44328 json
free5GC: SMF UPI DELETE /upi/v1/upNodesLinks/{ref} panics on AN-node deletion via nil UPF dereference; unauthenticated, state-mutating
published 2026-05-08 6 mo ago modified 2026-10-14 25 d ago also EUVD-2026-32570 , GHSA-p9mg-74mg-cwwr , GO-2026-5537
- cvss
- 8.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 25%
- public exploits
- 0
- none known
Summary
free5GC is an open-source implementation of the 5G core network. Prior to 4.2.2, free5GC's SMF mounts the UPI management route group without inbound OAuth2 middleware. On top of that, the DELETE /upi/v1/upNodesLinks/{upNodeRef} handler unconditionally dereferences upNode.UPF after the type-guarded async release, even though AN-typed nodes are constructed without a UPF object. As a result, a single unauthenticated DELETE /upi/v1/upNodesLinks/gNB1 request crashes the handler with a nil-pointer panic AND mutates the in-memory user-plane topology before panicking (the UpNodeDelete(upNodeRef) line runs first). This is an unauthenticated, state-mutating panic-DoS sink that an off-path network attacker can trigger by name against any AN entry. This vulnerability is fixed in 4.2.2.
Patch / fix
- go github.com/free5gc/smf 1.4.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/smf@b57bc48 commit
- github.com/free5gc/smf#199 pull request
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 5 mo ago
Exploit prediction
0.32% chance of exploitation in the next 30 days, higher than 25% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/free5gc/free5gc/security/advisories/GHSA-p9mg-74mg-cwwr referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/free5gc/free5gc/issues/905 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H |
| GitHub | 3.1 | 8.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/free5gc/smf | <1.4.3 |
1.4.3 |
Affected products
- free5gc free5gc
Classification
References
-
github.com
/free5gc/smf/pull/199
web, issue-tracking, patch
-
github.com
/free5gc/smf/commit/b57bc48081c3d3a2f333d02eb78e4fd31a120deb
web, patch
-
github.com
/free5gc/free5gc/security/advisories/GHSA-p9mg-74mg-cwwr
exploit, web, vendor-advisory, advisory
-
github.com
/free5gc/free5gc/issues/905
exploit, web, issue-tracking
-
nvd.nist.gov
/vuln/detail/CVE-2026-44328
advisory
-
github.com
/free5gc/free5gc
package
Sources
- CVE List CVE-2026-44328
- GitHub Advisory GHSA-p9mg-74mg-cwwr
- NVD CVE-2026-44328
- OSV GO-2026-5537
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.