PatchSiren cyber security CVE debrief
CVE-2026-8226 Vuldb CVE debrief
CVE-2026-8226 describes a remotely reachable denial-of-service issue in Open5GS affecting versions up to 2.7.7. The vulnerable function named in the record is ogs_pcc_rule_install_flow_from_media in /lib/proto/types.c. The supplied CVE description says the flaw can be manipulated remotely to cause service disruption and that public exploit code has already been released. Based on the available corpus, the immediate security concern is availability impact for Open5GS deployments, especially those exposed to untrusted networks.
- Vendor
- Vuldb
- Product
- Unknown
- CVSS
- MEDIUM 5.5
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-05-10
- Original CVE updated
- 2026-05-10
- Advisory published
- 2026-05-10
- Advisory updated
- 2026-05-10
Who should care
Operators and maintainers of Open5GS deployments, especially production or internet-facing 5G core environments, should care most. Security teams responsible for service availability, edge network exposure, and patch management should also prioritize this record.
Technical summary
The source corpus states that Open5GS versions up to 2.7.7 contain a flaw in ogs_pcc_rule_install_flow_from_media within /lib/proto/types.c that can lead to denial of service through remote manipulation. NVD metadata classifies the issue as CWE-404 and the supplied CVSS vector reflects a network-reachable, low-complexity, no-authentication availability-impacting weakness. The record also says public exploit code exists, but the corpus does not include root-cause analysis, packet details, or a vendor fix announcement.
Defensive priority
Medium overall, but elevated for any exposed Open5GS deployment because the issue is remotely reachable and the record says exploit code is public.
Recommended defensive actions
- Inventory Open5GS instances and confirm whether any run version 2.7.7 or earlier.
- Treat exposed or production 5G core deployments as highest priority for review.
- Watch the Open5GS repository, issue tracker, and NVD record for a fixed release or maintainer guidance.
- Reduce unnecessary network exposure to Open5GS services where practical until remediation is available.
- Add or validate availability monitoring and alerting for Open5GS components to detect service disruption quickly.
Evidence notes
This debrief is based only on the supplied NVD/CVE metadata and the listed references. The NVD feed entry shows vulnStatus as Received and includes references to the Open5GS repository, issue #4441, and VulDB pages. The corpus does not provide the contents of those linked pages, so no additional root-cause or remediation claims are made here.
Official resources
According to the supplied CVE description and NVD metadata, the issue was publicly disclosed on 2026-05-10. The description also says the project was informed earlier through an issue report and that exploit code has been released publicly.