dbcve.org
Open5gsApplication

CVE-2025-41067

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. 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.

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

Reachable assertion vulnerability in Open5GS NRF (Network Repository Function) up to v2.7.6 where an attacker with NRF connectivity can send a malicious SBI request that deletes the NRF's own registry. This triggers an assertion check failure that crashes the NRF process, rendering the 5G core discovery service unavailable.

MitigationUpgrade Open5GS to version 2.7.7 or later. Until patched, restrict network access to the NRF SBI interface to trusted entities only.

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 installation
    Locate the Open5GS installation and determine the version of the NRF component. Common methods include checking package metadata, binary version flags, or the NRF service banner if exposed.
    Affected if The installed version is prior to 2.7.5 (versions 2.7.6 and below are affected; the fix is in 2.7.7)
  2. Verify NRF service is running
    Confirm the NRF process is active in the environment. Check process lists, service status, or container orchestration status depending on deployment method.
    Affected if The NRF component is currently deployed and operational in the 5G core environment
  3. Assess NRF SBI interface exposure
    Determine if the NRF SBI (Service-Based Interface) is network-accessible from untrusted sources. Review firewall rules, network policies, or exposed endpoints that allow inbound connections to the NRF service.
    Affected if The NRF SBI interface is reachable from network segments that contain untrusted or attacker-controlled entities
  4. Check NRF configuration for SBI bindings
    Inspect the NRF configuration files or runtime settings to identify the binding addresses and ports used for SBI communication.
    Affected if The NRF is configured to accept SBI requests on accessible network interfaces

The environment is affected if Open5GS NRF version is below 2.7.7 and the NRF SBI interface is network-accessible to untrusted parties, as the assertion failure requires a malicious SBI request to reach the NRF.

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 Open5GS to version 2.7.7 or later. Until patched, restrict network access to the NRF SBI interface to trusted entities only.

Recommended fix Moderate confidence

Open5gs 2.7.5 or later

  1. 1. Identify all Open5gs NRF (Network Repository Function) instances in your deployment
  2. 2. Download or obtain Open5gs version 2.7.5 or later from the official source (open5gs.org)
  3. 3. Before upgrading, backup your current Open5gs configuration files
  4. 4. Stop the Open5gs services running the NRF component
  5. 5. Upgrade the Open5gs package to version 2.7.5 or later
  6. 6. Verify the NRF component starts successfully after upgrade
  7. 7. Test that the NRF service is responsive and can handle SBI requests normally
  8. 8. Monitor the NRF process to ensure it remains stable and does not crash
Caveat Review release notes for any configuration or API changes between your current version and 2.7.5+

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

Fix this in Open5gs Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-41067 — 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-41067 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