CVE 10 CRITICAL

free5GC: NEF nnef-pfdmanagement API is unauthenticated; forged bearer tokens can read PFD data and create/delete PFD subscriptions_CVE-2026-44330

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-pfdmanagement route group without inbound OAuth2/bearer-token authorization. A network attacker who can reach NEF on the SBI can use a forged or arbitrary bearer token (e.g. Authorization: Bearer not-a-real-token) to read PFD application data via GET /applications and GET /applications/{appID}, and to create or delete PFD change-notification subscriptions via POST /subscriptions and DELETE /subscriptions/{subID}. Same root cause as the other NEF SBI findings: the route group is mounted without any inbound auth middleware. Unlike the OAM and traffic-influence groups, nnef-pfdmanagement IS declared in the runtime ServiceList, so this is the production-intended path that operators expect to be protected by OAuth2 setting receive from NRF: true -- and it is not. This vulnerability is fixed in 4.2.2.

AI Analysis

Unauthenticated access to NEF nnef-pfdmanagement API allows reading PFD data and creating/deleting PFD subscriptions

Basic Information

ID CVE-2026-44330
Source GitHub_M
Published May 27, 2026 at 15:36

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.