Quick answers
- Is CVE-2026-37223 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-37223 being exploited in the wild.
- How severe is CVE-2026-37223?
- Informational severity, with a CVSS score of 7.5, published 1 June 2026.
- Which products and versions are affected?
- EURECOM FlexRIC v2.0.0 through commit 6a595d8b (2025-11-12).
- Is there a fix for CVE-2026-37223?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-37223 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-37223?
- Check whether you run EURECOM FlexRIC at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A Reachable Assertion (CWE-617) exists in the FlexRIC iApp message dispatcher within 'src/ric/iApp/msg_handler_iapp.c'. The 'e2ap_msg_handle_iapp' function validates incoming E2AP message types against a 9-entry whitelist using the 'assert()' macro. A remote, unauthenticated attacker can send a decodable E2AP Protocol Data Unit (PDU) with a message type not present in the whitelist to SCTP port 36422. This triggers a SIGABRT, crashing the iApp process. Because the iApp and the near-RT RIC typically share a single process, this terminates the entire RIC service and disconnects all E2 Nodes and xApps. No patch was available at the time of disclosure; mitigation involves restricting access to port 36422.
Affected products
- EURECOM FlexRIC v2.0.0 through commit 6a595d8b (2025-11-12)
Timeline
- 2026-06-01: advisory: NVD and researcher advisory published