CVE-2026-44329 json
free5GC: SMF UPI management interface lacks auth middleware; unauthenticated topology read/write requests reach handlers
published 2026-05-08 6 mo ago modified 2026-10-14 25 d ago also EUVD-2026-32569 , GHSA-3258-qmv8-frp3 , GO-2026-4995
- cvss
- 10.0
- 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 26%
- 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 OAuth2/bearer-token authorization middleware. A network attacker who can reach SMF on the SBI can hit UPI endpoints with no Authorization header at all, and the requests reach the SMF business handlers. In the running Docker lab this was directly demonstrated for read (GET /upi/v1/upNodesLinks), write (POST /upi/v1/upNodesLinks with attacker-controlled UP-node and link payload), and delete (DELETE /upi/v1/upNodesLinks/{nodeID}) operations. 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@e23ce97 commit
- github.com/free5gc/smf#197 pull request
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- total
- Assessed
- 5 mo ago
Exploit prediction
0.33% chance of exploitation in the next 30 days, higher than 26% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/free5gc/free5gc/security/advisories/GHSA-3258-qmv8-frp3 referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/free5gc/free5gc/issues/887 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 10.0 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:H |
| GitHub | 3.1 | 10.0 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/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/197
web, issue-tracking, patch
-
github.com
/free5gc/smf/commit/e23ce97565f285eb99eed153743c62bf4c767c6e
web, patch
-
github.com
/free5gc/free5gc/security/advisories/GHSA-3258-qmv8-frp3
exploit, web, vendor-advisory, advisory
-
github.com
/free5gc/free5gc/issues/887
exploit, web, issue-tracking
-
nvd.nist.gov
/vuln/detail/CVE-2026-44329
advisory
-
github.com
/free5gc/free5gc
package
Sources
- CVE List CVE-2026-44329
- GitHub Advisory GHSA-3258-qmv8-frp3
- NVD CVE-2026-44329
- OSV GO-2026-4995
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.