# CVE-2025-66719: Free5gc NRF is vulnerable to scope validation bypass via maliciously crafted targetNF value

> Attackers can bypass scope validation in Free5gc NRF to obtain access tokens with arbitrary scopes, leading to privilege escalation.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Jan 2026
- **Updated:** 23 Jan 2026
- **Also known as:** GHSA-q7c8-gfjh-8v4p, GO-2026-5570

## What is CVE-2025-66719?

CVE-2025-66719 is a critical authentication bypass vulnerability in n/a, published on 23 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Free5gc NRF 1.4.0. In the access-token generation logic of free5GC, the AccessTokenScopeCheck() function in file internal/sbi/processor/access_token.go bypasses all scope validation when the attacker uses a crafted targetNF value. This allows attackers to obtain an access token with any arbitrary scope.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2025-66719?

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.1 |
| `github.com/free5gc/nrf` | Go | All versions | 1.4.1 |
| `github.com/free5gc/nrf` | Go | All versions | 1.4.1 |

Products: Free5gc Nrf.

## How do I fix CVE-2025-66719?

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

## Is CVE-2025-66719 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-66719 and fix it if it is affected.

What it is: CVE-2025-66719 is a critical authentication bypass vulnerability in n/a, published on 23 Jan 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-2025-66719 exists.

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

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-2025-66719/ (Markdown: https://insights.sbomify.com/CVE-2025-66719/index.md)
```

## Sources

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

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