CVE-2026-44327
published 2026-05-27CVE-2026-44327: 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…
PriorityP359critical10CVSS 3.1
AVNACLPRNUINSCCLIHAH
EPSS
0.31%
24.2th percentile
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.
Affected
2 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| free5gc | free5gc | < 4.2.2 | 4.2.2 |
| github.com | free5gc_nef | 0 – 1.2.3 | — |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
VulDB
Free5GC up to 4.2.1 OAM missing authentication
vuldb·2026-05-27·CVSS 10.0
CVE-2026-44327 [CRITICAL] Free5GC up to 4.2.1 OAM missing authentication
A vulnerability was found in Free5GC up to 4.2.1. It has been rated as critical. Affected by this vulnerability is an unknown functionality of the component OAM Handler. The manipulation leads to missing authentication.
This vulnerability is listed as CVE-2026-44327. The attack may be initiated remotely. There is no available exploit.
Upgrading the affected component is advised.
GHSA
free5GC's NEF nnef-oam route group is unauthenticated; no-token requests reach the OAM handler
ghsa·2026-05-08
CVE-2026-44327 [CRITICAL] CWE-306 free5GC's NEF nnef-oam route group is unauthenticated; no-token requests reach the OAM handler
free5GC's NEF nnef-oam route group is unauthenticated; no-token requests reach the OAM handler
### Summary
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. Same root cause as the NEF traffic-influence and PFD-management findings.
### Details
Validated against the NEF container in the official Docker compose lab.
- Source repo tag: `v4.2.1`
- Ru
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2026-05-27
Published