# CVE-2025-15156: Null dereference in UPF

> Remote attackers can cause a denial of service in the omec-project UPF via a null pointer dereference in PFCP session handling.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Dec 2025
- **Updated:** 29 Dec 2025
- **Also known as:** GHSA-4x7j-66xr-jfqf

## What is CVE-2025-15156?

CVE-2025-15156 is a medium-severity vulnerability in omec-project UPF, published on 28 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw has been found in omec-project UPF up to 2.1.3-dev. This affects the function handleSessionEstablishmentRequest of the file /pfcpiface/pfcpiface/messages_session.go of the component PFCP Session Establishment Request Handler. This manipulation causes null pointer dereference. The attack may be initiated remotely. The exploit has been published and may be used. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-476 (NULL Pointer Dereference), CWE-404 (Improper Resource Shutdown or Release)

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


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

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

## Is CVE-2025-15156 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-15156 is a medium-severity vulnerability in omec-project UPF, published on 28 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15156 exists.

Affected product: omec-project UPF. 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-15156/ (Markdown: https://insights.sbomify.com/CVE-2025-15156/index.md)
```

## Sources

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

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