CVE-2026-44327
- Source
- https://cve.org/CVERecord?id=CVE-2026-44327
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-44327.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-44327
- Aliases
- Published
- 2026-05-27T15:40:41.569Z
- Modified
- 2026-07-08T08:13:28.115075965Z
- Severity
-
- 10.0 (Critical) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:H CVSS Calculator
- Summary
- free5GC: NEF nnef-oam route group is unauthenticated; no-token requests reach the OAM handler
- Details
-
free5GC is an open-source implementation of the 5G core network. Prior to 4.2.2, free5GC's NEF mounts the nnef-oam route group without inbound OAuth2/bearer-token authorization. A network attacker who can reach NEF on the SBI can hit the OAM route with no Authorization header at all and the handler returns 200 OK. The current OAM handler is a stub that returns null, but the structural defect is route-group-scoped: the entire OAM route group has no inbound auth middleware, so every future OAM operation added to this group inherits the missing auth boundary by default. 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-44327.json", "cna_assigner": "GitHub_M", "cwe_ids": [ "CWE-306", "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" } ] }