# CVE-2026-44325: free5GC: NRF POST /oauth2/token structured-form parser type-confusion panic family (Reflect.Set on incompatible types)

> An unauthenticated attacker can crash the free5GC NRF service by sending a malformed form-encoded request to the token endpoint, causing a panic.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 May 2026
- **Updated:** 27 May 2026
- **Also known as:** GHSA-f8qv-7x5w-qr48, GO-2026-5349

## What is CVE-2026-44325?

CVE-2026-44325 is a high-severity denial of service vulnerability in Free5gc Free5gc, published on 27 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

free5GC is an open-source implementation of the 5G core network. Prior to 4.2.2, free5GC's NRF root SBI endpoint POST /oauth2/token contains a parser-level type-confusion bug family. The handler in NFs/nrf/internal/sbi/api_accesstoken.go reflects over models.NrfAccessTokenAccessTokenReq, special-cases only plain string and NrfNfManagementNfType fields, and treats every other field as if it were a single models.PlmnId. The parsed *models.PlmnId is then assigned with reflect.Value.Set() to whichever field name the attacker put in the form body, which panics whenever the destination field's real type is incompatible (slice, different struct, primitive). Gin recovery converts each panic into HTTP 500, but the endpoint remains remotely panicable from a single unauthenticated form-encoded request and is repeatedly triggerable. This vulnerability is fixed in 4.2.2.

Weakness: CWE-843 (Access of Resource Using Incompatible Type), CWE-755 (Improper Handling of Exceptional Conditions), CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2026-44325?

3 open source packages ship an affected version, including github.com/free5gc/nrf. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/free5gc/nrf` | Go | All versions | 1.4.3 |
| `github.com/free5gc/nrf` | Go | All versions | 1.4.3 |
| `github.com/free5gc/nrf` | Go | All versions | 1.4.3 |

Products: Free5gc Free5gc.

## How do I fix CVE-2026-44325?

Upgrade github.com/free5gc/nrf to 1.4.3 or later.

## Is CVE-2026-44325 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44325 exists.

## Other vulnerabilities in Free5gc Free5gc

- [CVE-2026-44327](https://insights.sbomify.com/CVE-2026-44327/): free5GC: NEF nnef-oam route group is unauthenticated; no-token requests reach the OAM handler (critical 10.0)
- [CVE-2026-44329](https://insights.sbomify.com/CVE-2026-44329/): free5GC's SMF UPI management interface lacks auth middleware; unauthenticated topology read/write requests reach handlers (critical 10.0)
- [CVE-2026-44330](https://insights.sbomify.com/CVE-2026-44330/): free5GC's NEF nnef-pfdmanagement API is unauthenticated; forged bearer tokens can read PFD data and create/delete PFD subscriptions (critical 10.0)
- [CVE-2025-63679](https://insights.sbomify.com/CVE-2025-63679/): Memory corruption in n/a (critical 9.8)
- [CVE-2026-44315](https://insights.sbomify.com/CVE-2026-44315/): free5GC's NEF 3gpp-pfd-management API is unauthenticated; forged bearer tokens can create, read, and delete PFD transactions (critical 9.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44325 and fix it if it is affected.

What it is: CVE-2026-44325 is a high-severity denial of service vulnerability in Free5gc Free5gc, published on 27 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44325 exists.

Affected packages and fixed versions:
- github.com/free5gc/nrf (Go): affected all versions; fixed in 1.4.3
- github.com/free5gc/nrf (Go): affected all versions; fixed in 1.4.3
- github.com/free5gc/nrf (Go): affected all versions; fixed in 1.4.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-44325/ (Markdown: https://insights.sbomify.com/CVE-2026-44325/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44325
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44325
- OSV: https://osv.dev/vulnerability/CVE-2026-44325

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-44325/
Summaries are generated and may contain mistakes; the official description above is the record.