# CVE-2025-41067: Reachable Assertion vulnerability in Open5GS

> Attackers can crash the Open5GS NRF process by sending a specific SBI request, causing a denial of service for the discovery service.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Oct 2025
- **Updated:** 29 Oct 2025
- **Also known as:** GHSA-m3r7-hp4v-q24g

## What is CVE-2025-41067?

CVE-2025-41067 is a high-severity denial of service vulnerability in Open5gs Open5gs, published on 27 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Reachable Assertion vulnerability in Open5GS up to version 2.7.6 allows attackers with connectivity to the NRF to cause a denial of service. An SBI request that deletes the NRF's own registry causes a check that ends up crashing the NRF process and renders the discovery service unavailable.

Weakness: CWE-617 (Reachable Assertion)

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

It affects 1 product.


Products: Open5gs Open5gs.

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

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

## Is CVE-2025-41067 being exploited?

There is no known exploitation of CVE-2025-41067 in the wild and no public exploit code.

Public exploit code:

- This repository contains the Proof-of-Concept (PoC) exploit scripts for two vulnerabilities, CVE-2025-41067 and CVE-2025-41068. These vulnerabilities affect the NRF (Network Repository Function) component of Open5GS in versions prior to 2.7.6 and can be triggered by an attacker to cause a Denial of Service (DoS). (github_poc): https://github.com/xvk1t1/Open5GS-CVE-2025-41067-CVE-2025-41068-PoC

## Other vulnerabilities in Open5gs Open5gs

- [CVE-2024-40130](https://insights.sbomify.com/CVE-2024-40130/): Memory corruption in n/a (critical 9.8)
- [CVE-2021-28122](https://insights.sbomify.com/CVE-2021-28122/): Missing authorization in n/a (critical 9.8)
- [CVE-2021-25863](https://insights.sbomify.com/CVE-2021-25863/): Hardcoded credentials in n/a (high 8.8)
- [CVE-2025-41068](https://insights.sbomify.com/CVE-2025-41068/): Reachable Assertion vulnerability in Open5GS (high 8.7)
- [CVE-2023-37015](https://insights.sbomify.com/CVE-2023-37015/): Denial of service in n/a (high 8.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-41067 is a high-severity denial of service vulnerability in Open5gs Open5gs, published on 27 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-41067 in the wild and no public exploit code.

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

## Sources

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

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