# CVE-2025-63679: Memory corruption in n/a

> A buffer overflow in free5gc AMF allows remote attackers to crash the service via a malicious NGAP message, causing denial of service.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Nov 2025
- **Updated:** 13 Nov 2025
- **Also known as:** GHSA-7mr7-hhp3-f6qg

## What is CVE-2025-63679?

CVE-2025-63679 is a critical memory corruption vulnerability in Free5gc Free5gc, published on 12 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

free5gc v4.1.0 and before is vulnerable to Buffer Overflow. When AMF receives an UplinkRANConfigurationTransfer NGAP message from a gNB, the AMF process crashes.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 1 product.


Products: Free5gc Free5gc.

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

No fix has been published for CVE-2025-63679 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-63679 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63679 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-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)
- [CVE-2026-44326](https://insights.sbomify.com/CVE-2026-44326/): free5GC's NEF 3gpp-traffic-influence API is unauthenticated; missing or forged bearer tokens can create, read, patch, and delete subscriptions (critical 9.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-63679 is a critical memory corruption vulnerability in Free5gc Free5gc, published on 12 Nov 2025. 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-63679 exists.

Affected product: Free5gc Free5gc. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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