Vulnerabilities in pkg:golang/github.com/free5gc/nef

PACKAGE
Advisory Identifier: GHSA-cmpj-2x3g-m7g3
Advisory Summary

CVE-2026-44327 is a CRITICAL (CVSS 10.0) free5gc's nef nnef-oam route group vulnerability (CWE-306: Missing Authentication for Critical Function) affecting Github.com/free5gc/nef libraries in the Go ecosystem. The issue involves free5gc's nef nnef-oam route group is unauthenticated; no-token requests reach the oam handler. Remediation is available in the latest vendor maintenance releases.

7 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:golang/github.com/free5gc/nef

7 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:golang/github.com/free5gc/nef. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-cmpj-2x3g-m7g3 CVE-2026-44327 CRITICAL free5GC's NEF nnef-oam route group is unauthenticated; no-token requests reach the OAM handler
GHSA-rwww-x45w-p52w CVE-2026-44330 CRITICAL free5GC's NEF nnef-pfdmanagement API is unauthenticated; forged bearer tokens can read PFD data and create/delete PFD subscriptions
GHSA-3p28-73q7-45xp CVE-2026-44326 CRITICAL free5GC's NEF 3gpp-traffic-influence API is unauthenticated; missing or forged bearer tokens can create, read, patch, and delete subscriptions
GHSA-5f62-53r8-qrqf CVE-2026-44315 CRITICAL free5GC's NEF 3gpp-pfd-management API is unauthenticated; forged bearer tokens can create, read, and delete PFD transactions
GHSA-j59f-x285-69jx CVE-2026-44322 HIGH free5GC's NEF 3gpp-pfd-management PATCH applications/{appId} panics on UDR access failure due to nil ProblemDetails dereference
GHSA-wqfh-gq79-j8mf CVE-2026-44320 HIGH free5GC's NEF nnef-callback route group is unauthenticated; forged callback requests are accepted into the processing path
GHSA-rxrq-fv76-26pr CVE-2026-44319 HIGH free5GC's NEF crashes via logger.Fatal on PFD notification delivery failure (attacker-controlled notifyUri)

CVE-2026-44327 at a Glance

CVE Identifier CVE-2026-44327
GHSA Identifier GHSA-cmpj-2x3g-m7g3
Severity CRITICAL
CVSS v3.1 Base Score 10.0
CWE Classification CWE-306: Missing Authentication for Critical Function
Affected Product Github.com/free5gc/nef
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 10.0

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality Low (C:L)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-44327

To remediate this vulnerability, upgrade all affected Github.com/free5gc/nef dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/free5gc/nef fixed: Latest secure release
Upgrade github.com/free5gc/nef to Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/free5gc/nef

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-44327, inspect your project dependencies for Github.com/free5gc/nef:

inspect dependencies for github.com/free5gc/nef

Analyze the terminal output to locate any version of Github.com/free5gc/nef in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-306: Missing Authentication for Critical Function, where the product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources. In Github.com/free5gc/nef, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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` - Running Docker image: `free5gc/nef:v4.2.0` - Runtime NEF commit: `5ce35eab` - Docker validation date: 2026-03-11 NEF advertises `OAuth2 setting receive from NRF: true`, yet the OAM route group is mounted without any inbound auth middleware and answers unauthenticated `GET`s with `200 OK`. Code evidence (paths in `free5gc/nef`): - OAM route group mounted without auth middleware: `NFs/nef/internal/sbi/server.go:60` - OAM route exposed at `/`: `NFs/nef/internal/sbi/api_oam.go:9` - OAM processor returns `200 OK` directly: `NFs/nef/internal/sbi/processor/oam.go:9` - NEF context only exposes outbound token acquisition (`GetTokenCtx`); there is no inbound authorization path: `NFs/nef/internal/context/nef_context.go:153` ### PoC Reproduced against the running NEF at `http://10.100.200.19:8000` with no `Authorization` header: ``` curl -i http://10.100.200.19:8000/nnef-oam/v1/ ``` Observed output: ``` HTTP/1.1 200 OK null ``` NEF container logs (`docker logs nef`) show the request being served while OAuth is enabled: ``` [INFO][NEF][GIN] | 200 | GET | /nnef-oam/v1/ ``` ### Impact Missing inbound authentication (CWE-306) and authorization (CWE-862) on the NEF OAM SBI route group. Severity is scored against the OAM route group's intended capability surface (Operations / Administration / Maintenance), NOT against the current stub handler. The current handler is a stub that returns `null`, but the defect is route-group-scoped: there is no auth middleware on the group at all, so every future OAM operation added behind this group inherits the missing inbound auth boundary by default. Any party that can reach NEF on the SBI can: - Probe and enumerate the OAM route surface anonymously today. - Hit any future OAM-group endpoint (read, modify, restart-style operations) anonymously, because the auth boundary does not exist for this group. Operators who assume `OAuth2 setting receive from NRF: true` enforces inbound auth on NEF are wrong for this route group. Affected: free5gc v4.2.1. Upstream issue: https://github.com/free5gc/free5gc/issues/861 Upstream fix: https://github.com/free5gc/nef/pull/23

CVE-2026-44327 Affected Github.com/free5gc/nef Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
github.com/free5gc/nef
Go
≤ 1.2.3

References

Frequently Asked Questions

What is CVE-2026-44327?
CVE-2026-44327 is a security vulnerability in Github.com/free5gc/nef involving free5GC's NEF nnef-oam route group is unauthenticated; no-token requests reach the OAM handler under CWE-306: Missing Authentication for Critical Function.
Which Github.com/free5gc/nef versions are affected?
Affected versions include releases prior to current release patches across affected packages: github.com/free5gc/nef.
What version fixes CVE-2026-44327?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/free5gc/nef affected?
Yes, github.com/free5gc/nef is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What is the CVSS score of CVE-2026-44327?
CVE-2026-44327 has a CVSS v3.1 base score of 10.0 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:H.
What CWE is associated with CVE-2026-44327?
CVE-2026-44327 is classified under CWE-306: Missing Authentication for Critical Function (The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.).
How can I check Go dependencies for CVE-2026-44327?
Run the dependency tree command: 'inspect dependencies for github.com/free5gc/nef'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-cmpj-2x3g-m7g3",
  "modified" : "2026-07-21T13:57:54Z",
  "published" : "2026-05-08T22:59:22Z",
  "aliases" : [ "CVE-2026-44327" ],
  "summary" : "free5GC's NEF nnef-oam route group is unauthenticated; no-token requests reach the OAM handler",
  "details" : "### Summary\nfree5GC'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.\n\n### Details\nValidated against the NEF container in the official Docker compose lab.\n- Source repo tag: `v4.2.1`\n- Running Docker image: `free5gc/nef:v4.2.0`\n- Runtime NEF commit: `5ce35eab`\n- Docker validation date: 2026-03-11\n\nNEF advertises `OAuth2 setting receive from NRF: true`, yet the OAM route group is mounted without any inbound auth middleware and answers unauthenticated `GET`s with `200 OK`.\n\nCode evidence (paths in `free5gc/nef`):\n- OAM route group mounted without auth middleware: `NFs/nef/internal/sbi/server.go:60`\n- OAM route exposed at `/`: `NFs/nef/internal/sbi/api_oam.go:9`\n- OAM processor returns `200 OK` directly: `NFs/nef/internal/sbi/processor/oam.go:9`\n- NEF context only exposes outbound token acquisition (`GetTokenCtx`); there is no inbound authorization path: `NFs/nef/internal/context/nef_context.go:153`\n\n### PoC\nReproduced against the running NEF at `http://10.100.200.19:8000` with no `Authorization` header:\n\n```\ncurl -i http://10.100.200.19:8000/nnef-oam/v1/\n```\n\nObserved output:\n```\nHTTP/1.1 200 OK\nnull\n```\n\nNEF container logs (`docker logs nef`) show the request being served while OAuth is enabled:\n```\n[INFO][NEF][GIN] | 200 | GET | /nnef-oam/v1/\n```\n\n### Impact\nMissing inbound authentication (CWE-306) and authorization (CWE-862) on the NEF OAM SBI route group. Severity is scored against the OAM route group's intended capability surface (Operations / Administration / Maintenance), NOT against the current stub handler. The current handler is a stub that returns `null`, but the defect is route-group-scoped: there is no auth middleware on the group at all, so every future OAM operation added behind this group inherits the missing inbound auth boundary by default.\n\nAny party that can reach NEF on the SBI can:\n- Probe and enumerate the OAM route surface anonymously today.\n- Hit any future OAM-group endpoint (read, modify, restart-style operations) anonymously, because the auth boundary does not exist for this group.\n\nOperators who assume `OAuth2 setting receive from NRF: true` enforces inbound auth on NEF are wrong for this route group.\n\nAffected: free5gc v4.2.1.\n\nUpstream issue: https://github.com/free5gc/free5gc/issues/861\nUpstream fix: https://github.com/free5gc/nef/pull/23",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/free5gc/nef"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "1.2.3"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/free5gc/free5gc/security/advisories/GHSA-cmpj-2x3g-m7g3"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-44327"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/free5gc/free5gc/issues/861"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/free5gc/nef/pull/23"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/free5gc/free5gc"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-306", "CWE-862" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-08T22:59:22Z",
    "nvd_published_at" : "2026-05-27T17:16:38Z"
  }
}