Loading vulnerability…
CVE-2025-41067 is a reachable assertion vulnerability in Open5GS affecting versions up to 2.7.6. An attacker with connectivity to the Network Repository Function (NRF) can send a Service Based Interface (SBI) request that deletes the NRF's own registry entry. This triggers an internal check/assertion condition that causes the NRF process to crash. The result is loss of the NRF discovery service.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository provides two Python proof-of-concept (PoC) exploit scripts targeting two vulnerabilities (CVE-2025-41067 and CVE-2025-41068) in the Open5GS Network Repository Function (NRF) prior to version 2.7.6. The vulnerabilities allow a remote attacker with network access to the NRF's HTTP/2 interface (port 7777) to crash the NRF process, resulting in a denial of service for the 5G network's discovery service. The repository contains: - Two exploit scripts (CVE-2025-41067.py and CVE-2025-41068.py), each targeting a different vulnerability. - A README.md with detailed usage instructions, vulnerability background, and references to advisories and upstream issues. - A requirements.txt specifying the httpx library with HTTP/2 support. CVE-2025-41067.py works by querying the NRF for all registered network functions, identifying those of type 'NRF', and sending DELETE requests to remove them. This self-referential deletion triggers a crash in the NRF process. CVE-2025-41068.py registers a new network function with an invalid type ('EMF') and then queries the list of network functions, which causes the NRF to crash when processing the malformed entry. Both scripts require the attacker to supply the target NRF's IP address and use HTTP/2 for communication. The main endpoints targeted are '/nnrf-nfm/v1/nf-instances' and '/nnrf-nfm/v1/nf-instances/<nfInstanceId>'. The exploits are functional PoCs, not weaponized, and are intended for authorized testing and research.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.