CVE-2026-44326
- Source
- https://cve.org/CVERecord?id=CVE-2026-44326
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-44326.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-44326
- Aliases
- Published
- 2026-05-27T15:41:38.820Z
- Modified
- 2026-07-08T08:13:30.031013688Z
- Severity
-
- 9.4 (Critical) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H CVSS Calculator
- Summary
- free5GC: NEF 3gpp-traffic-influence API is unauthenticated; missing or forged bearer tokens can create, read, patch, and delete subscriptions
- Details
-
free5GC is an open-source implementation of the 5G core network. Prior to 4.2.2, free5GC's NEF mounts the 3gpp-traffic-influence API without inbound OAuth2/bearer-token authorization. A network attacker who can reach NEF on the SBI can create, read, patch, and delete traffic-influence subscriptions either with no Authorization header at all, or with a forged bearer token (e.g. Authorization: Bearer not-a-real-token). This includes creating AnyUeInd=true subscriptions intended to affect group / any-UE traffic steering. The route group is also reachable even when the running config's ServiceList does not declare it, so operators who think they disabled the service via config are still exposed. This vulnerability is fixed in 4.2.2.
- Database specific
{ "cna_assigner": "GitHub_M", "cwe_ids": [ "CWE-862" ], "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/44xxx/CVE-2026-44326.json" }- References
Affected packages
Git / github.com/free5gc/free5gc
Affected ranges
- Type
- GIT
- Repo
- https://github.com/free5gc/free5gc
- Events
-
Introduced0 Unknown introduced commit / All previous commits are affectedFixed
- Database specific
{ "extracted_events": [ { "introduced": "0" }, { "fixed": "4.2.2" } ], "cpe": "cpe:2.3:a:free5gc:free5gc:*:*:*:*:*:*:*:*", "source": [ "AFFECTED_FIELD", "CPE_RANGE" ] }