CVE-2026-44329
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:H
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.
Affected Software
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| free5gc | free5gc | < 4.2.2 | affected |
Weaknesses
- CWE-306: CWE-306: Missing Authentication for Critical Function
- CWE-862: CWE-862: Missing Authorization
ADP Enrichment
CISA ADP Vulnrichment
- SSVC:
- Exploitation: poc
- Automatable: yes
- Technical Impact: total
Additional References
- https://github.com/free5gc/free5gc/security/advisories/GHSA-3258-qmv8-frp3
- https://github.com/free5gc/free5gc/issues/887
References
- https://github.com/free5gc/free5gc/security/advisories/GHSA-3258-qmv8-frp3
- https://github.com/free5gc/free5gc/issues/887
- https://github.com/free5gc/smf/pull/197
- https://github.com/free5gc/smf/commit/e23ce97565f285eb99eed153743c62bf4c767c6e
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.