PatchSiren cyber security CVE debrief
CVE-2026-8267 Open5GS CVE debrief
A denial of service vulnerability was found in Open5GS up to 2.7.7 in the SMF component. The vulnerability affects the function smf_nsmf_handle_created_data_in_vsmf. The attack may be initiated remotely. The project was informed of the problem early through an issue report but has not responded yet. Users should review their installations and consider compensating controls. This vulnerability has been publicly disclosed and may be used by attackers.
- Vendor
- Open5GS
- Product
- Open5GS
- CVSS
- LOW 2.1
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-05-11
- Original CVE updated
- 2026-07-23
- Advisory published
- 2026-05-11
- Advisory updated
- 2026-07-23
Who should care
Users of Open5GS up to version 2.7.7 should be aware of this denial of service vulnerability and take necessary precautions. This includes reviewing their installations, applying patches when available, and monitoring for unusual activity in the SMF component. Affected operator, platform, vulnerability-management, and security-team impact should be reviewed.
Technical summary
The vulnerability is caused by a flaw in the smf_nsmf_handle_created_data_in_vsmf function of the SMF component in Open5GS up to 2.7.7. This manipulation causes denial of service. The attack may be initiated remotely. The vulnerability has been publicly disclosed and may be used by attackers. Affected product deployments should be reviewed for potential exposure, and defenders should verify the SMF component's configuration and monitor for unusual activity.
Defensive priority
Low priority due to CVSS score of 2.1 and lack of known exploit usage. However, defenders should still review and verify affected scope and severity, and consider compensating controls.
Recommended defensive actions
- Inventory and verify Open5GS installations up to version 2.7.7
- Apply vendor patches or updates when available
- Monitor for unusual activity in SMF component
- Consider compensating controls such as network segmentation
- Review and verify affected scope and severity
- Track exceptions and retest remediated assets
- Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
Evidence notes
The CVE record was published on 2026-05-11T04:16:20.233Z and was last modified on 2026-07-23T20:10:00.130Z. The NVD entry is currently Analyzed. The vulnerability affects Open5GS up to version 2.7.7. The attack may be initiated remotely. The project was informed of the problem early through an issue report but has not responded yet. Evidence limits suggest that defenders should verify the SMF component's configuration and monitor for unusual activity.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-8267 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-8267
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-8267 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-8267
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/open5gs/open5gs/
[email protected] - Product
-
Source reference
Unverified legacy reference
URL: https://github.com/open5gs/open5gs/issues/4448
[email protected] - Exploit, Issue Tracking
-
Mitigation or vendor reference
Unverified legacy reference
URL: https://vuldb.com/submit/808484
[email protected] - Third Party Advisory, VDB Entry
-
Mitigation or vendor reference
Unverified legacy reference
URL: https://vuldb.com/vuln/362564
[email protected] - Third Party Advisory, VDB Entry
-
Source reference
Unverified legacy reference
URL: https://vuldb.com/vuln/362564/cti
[email protected] - Permissions Required, VDB Entry
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.