# free5GC's NEF 3gpp-pfd-management API is unauthenticated; forged bearer tokens can create, read, and delete PFD transactions

Advisory record · `GHSA-5f62-53r8-qrqf`

- **Identifiers:** `GHSA-5f62-53r8-qrqf` · `CVE-2026-44315` · `GO-2026-5142`
- **State:** Confirmed
- **Severity:** CVSS 9.4 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-862](https://cwe.mitre.org/data/definitions/862.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 8 May 2026
- **Updated:** 25 Jun 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 8 May 2026, 22:39 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.4: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `github.com/free5gc/nef` (Go): affected `<=1.2.3`; no fixed version yet

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Go package github.com/free5gc/nef, versions up to and including 1.2.3, exposes its 3gpp-pfd-management API without inbound bearer-token authorization. A network attacker who can reach NEF on the service-based interface can, using any made-up bearer token, create, read, and delete PFD transactions, which can alter policy data used downstream. No fixed version is listed; the source does not give a workaround.

Written 7 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 9.4 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0031, the 24th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:07 UTC: First seen by agentprime
- 31 Oct 2026, 15:07 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-5f62-53r8-qrqf)

## Sources

- [GitHub Advisory Database: GHSA-5f62-53r8-qrqf](https://github.com/advisories/GHSA-5f62-53r8-qrqf)
- [OSV: GHSA-5f62-53r8-qrqf](https://osv.dev/vulnerability/GHSA-5f62-53r8-qrqf)
- <https://github.com/free5gc/free5gc/security/advisories/GHSA-5f62-53r8-qrqf>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-44315>
- <https://github.com/free5gc/free5gc/issues/858>
- <https://github.com/free5gc/nef/pull/23>
- <https://github.com/free5gc/free5gc>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-5f62-53r8-qrqf>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-5f62-53r8-qrqf/>. Everything for agents: <https://agentprime.io/llms.txt>.
