# CVE-2025-65562: Integer overflow in n/a

> An unauthenticated remote attacker can crash the free5GC UPF by sending a PFCP request with a large SEID, causing an integer underflow and 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:** No
- **Published:** 18 Dec 2025
- **Updated:** 19 Dec 2025
- **Also known as:** GHSA-7jcm-x89q-2vg2

## What is CVE-2025-65562?

CVE-2025-65562 is a high-severity vulnerability in Free5gc Free5gc, published on 18 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The free5GC UPF suffers from a lack of bounds checking on the SEID when processing PFCP Session Deletion Requests. An unauthenticated remote attacker can send a request with a very large SEID (e.g., 0xFFFFFFFFFFFFFFFF) that causes an integer conversion/underflow in LocalNode.DeleteSess() / LocalNode.Sess() when a uint64 SEID is converted to int and used in index arithmetic. This leads to a negative index into n.sess and a Go runtime panic, resulting in a denial of service (UPF crash). The issue has been reproduced on free5GC v4.1.0 with crashes observed in the session lookup/deletion path in internal/pfcp/node.go; other versions may also be affected. No authentication is required.

Weakness: CWE-129 (Improper Validation of Array Index)

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

It affects 1 product.


Products: Free5gc Free5gc.

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

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

## Is CVE-2025-65562 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-65562 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-2025-65562 and fix it if it is affected.

What it is: CVE-2025-65562 is a high-severity vulnerability in Free5gc Free5gc, published on 18 Dec 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-65562 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-65562/ (Markdown: https://insights.sbomify.com/CVE-2025-65562/index.md)
```

## Sources

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

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