dbcve.org
Open5gsApplication

CVE-2025-41068

HIGH · 7.5 CVSS v3.1 Published 2025-10-27
Fix available
A fix is available. Upgrade to 2.7.5 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Reachable Assertion vulnerability in Open5GS up to version 2.7.6 allows attackers with connectivity to the NRF to cause a denial of service. This is achieved by sending the creation of an NF with an invalid type via SBI and then requesting its data. The NRF executes a check that crashes the process, leaving the discovery service unresponsive.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Open5GS NRF (Network Repository Function) contains a reachable assertion vulnerability in versions up to 2.7.6. An attacker with network access to the NRF's SBI interface can register a Network Function (NF) with an invalid type, then trigger a crash by requesting that NF's data. The NRF performs an assertion check that fails, terminating the process and rendering the discovery service unavailable.

MitigationUpgrade to Open5GS version 2.7.7 or later. If immediate patching is not feasible, restrict access to the NRF SBI interface using network segmentation or firewall rules to prevent unauthorized NF registration.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Open5gsApplication
Affected:< 2.7.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Open5GS NRF version
    Check the installed Open5GS package version using your system's package manager (dpkg, rpm, or the binary version flag such as 'nrf --version'). Compare the version number to the affected range.
    Affected if The installed version is less than 2.7.5 (or within versions up to 2.7.6 if your deployment tracks that range).
  2. Confirm NRF SBI interface is listening
    Identify which network interfaces and ports the NRF service is listening on. Inspect the NRF configuration file (typically /etc/open5gs/nrf.yaml or similar) for the 'sbi' binding configuration. Use netstat or ss to verify the listening port (usually 8080 or 7777 for SBI).
    Affected if The NRF SBI interface is bound to an IP address reachable from untrusted networks, not just localhost or secured management networks.
  3. Verify NF registration access controls
    Review the NRF configuration for NF registration authorization settings. Check if 'nf_registration' or 'authorization' settings permit registration from any NF without authentication or from untrusted network sources.
    Affected if NF registration is allowed without proper authentication or from untrusted sources, allowing an attacker to register a malicious NF.
  4. Determine network exposure of NRF service
    Assess network topology to determine if the NRF SBI port is accessible to attackers. Check firewall rules, ACLs, or network segmentation that may restrict access to the NRF service.
    Affected if The NRF SBI interface is accessible to attackers with network access, enabling them to send malicious NF registration requests.

You are affected if the Open5GS NRF version is below 2.7.5 (or within the 2.7.5-2.7.6 range) AND the NRF SBI interface is reachable from untrusted network locations where an attacker could register a malformed NF and trigger the assertion failure.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.7.5 or later
Fixed in 2.7.5
Interim mitigation

Upgrade to Open5GS version 2.7.7 or later. If immediate patching is not feasible, restrict access to the NRF SBI interface using network segmentation or firewall rules to prevent unauthorized NF registration.

Recommended fix High confidence

Open5GS 2.7.5 or later (verify latest stable release on open5gs.org)

  1. 1. Identify the current Open5GS version installed by checking the package manager or running 'open5gs --version'
  2. 2. Ensure you have a backup of the current configuration files in /etc/open5gs/ before proceeding
  3. 3. Update the package repository to fetch the latest packages
  4. 4. Upgrade Open5GS to version 2.7.5 or later using the appropriate package manager (e.g., 'apt update && apt upgrade open5gs' or 'dnf update open5gs')
  5. 5. Restart the Open5GS NRF service to apply the updated package: 'systemctl restart open5gs-nrf'
  6. 6. Verify the upgrade was successful by checking the NRF service status: 'systemctl status open5gs-nrf'
  7. 7. Confirm the new version is running: 'open5gs --version'
Caveat Minor: Review release notes for any configuration changes or NF registration behavior updates in version 2.7.5+

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Open5gs Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-41068 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-41068 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data