CVE 10 CRITICAL

free5GC: NEF nnef-oam route group is unauthenticated; no-token requests reach the OAM handler_CVE-2026-44327

10 / 10
CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:H

Description

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.

AI Analysis

Unauthenticated access to the NEF nnef-oam route group due to missing OAuth2/bearer-token authorization

Basic Information

ID CVE-2026-44327
Source GitHub_M
Published May 27, 2026 at 15:40

Affected Product

Vendor free5gc
Product free5gc
Version < 4.2.2
Affected Versions free5gc free5gc < 4.2.2

CWE Classification

AI Assessment

AI Score 10 / 10
AI Severity Critical
Vendor free5gc
Product free5GC
Version < 4.2.2

References

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.