CVE-2026-44315
- Source
- https://cve.org/CVERecord?id=CVE-2026-44315
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-44315.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-44315
- Aliases
- Published
- 2026-05-27T15:52:51.027Z
- Modified
- 2026-07-08T08:13:30.027440059Z
- 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-pfd-management API is unauthenticated; forged bearer tokens can create, read, and delete PFD transactions
- Details
-
free5GC is an open-source implementation of the 5G core network. Prior to 4.2.2, free5GC's NEF mounts the 3gpp-pfd-management API without inbound OAuth2/bearer-token authorization. A network attacker who can reach NEF on the SBI can create, read, and delete PFD-management transaction state with a forged or arbitrary bearer token (e.g. Authorization: Bearer not-a-real-token). 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
{ "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/44xxx/CVE-2026-44315.json", "cna_assigner": "GitHub_M", "cwe_ids": [ "CWE-862" ] }- 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
{ "source": [ "AFFECTED_FIELD", "CPE_RANGE" ], "cpe": "cpe:2.3:a:free5gc:free5gc:*:*:*:*:*:*:*:*", "extracted_events": [ { "introduced": "0" }, { "fixed": "4.2.2" } ] }