Quick answers
- Is CVE-2026-37230 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-37230 being exploited in the wild.
- How severe is CVE-2026-37230?
- 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.
- Is there a fix for CVE-2026-37230?
- 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-37230 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-37230?
- 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 NULL pointer dereference exists in FlexRIC v2.0.0 (specifically in src/ric/plugin_ric.c) within the sm_plugin_ric() function. When the near-RT RIC receives a RIC_INDICATION message containing a ran_func_id that is not present in its registry, the lookup function returns NULL. In debug builds, this triggers an assertion failure (SIGABRT); in release builds where assertions are disabled, the subsequent dereference of the NULL pointer leads to a segmentation fault (SIGSEGV). A remote, unauthenticated attacker can exploit this by sending a crafted SCTP packet to port 36421, causing the RIC to crash.
Affected products
- EURECOM FlexRIC v2.0.0 through commit 6a595d8b
Timeline
- 2026-06-01: advisory: NVD and researcher advisory published