# CVE-2025-65568: Denial of service in n/a

> An attacker can crash the UPF by sending malformed PFCP requests, disrupting user-plane services in 5G core networks.

- **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:** 5 Jul 2026
- **Also known as:** GHSA-hg6h-53hm-4646

## What is CVE-2025-65568?

CVE-2025-65568 is a high-severity denial of service vulnerability in n/a, published on 18 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A denial-of-service vulnerability exists in the omec-project UPF (pfcpiface component) in version upf-epc-pfcpiface:2.1.3-dev. After PFCP association, a PFCP Session Establishment Request that includes a CreateFAR with an empty or truncated IPv4 address field is not properly validated. During parsing, parseFAR() calls ip2int(), which performs an out-of-bounds read on the IPv4 address buffer and triggers an index-out-of-range panic. An attacker who can send PFCP Session Establishment Request messages to the UPF's N4/PFCP endpoint can exploit this issue to repeatedly crash the UPF and disrupt user-plane services.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Opennetworking Upf.

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

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

## Is CVE-2025-65568 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-65563](https://insights.sbomify.com/CVE-2025-65563/): Null dereference in n/a (high 7.5)
- [CVE-2025-65564](https://insights.sbomify.com/CVE-2025-65564/): Null dereference in n/a (high 7.5)
- [CVE-2025-65565](https://insights.sbomify.com/CVE-2025-65565/): Null dereference in n/a (high 7.5)
- [CVE-2025-65567](https://insights.sbomify.com/CVE-2025-65567/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-65568 is a high-severity denial of service vulnerability in n/a, 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-65568 exists.

Affected product: n/a. 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-65568/ (Markdown: https://insights.sbomify.com/CVE-2025-65568/index.md)
```

## Sources

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

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