Quick answers
- Is CVE-2026-37225 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-37225 being exploited in the wild.
- How severe is CVE-2026-37225?
- 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-37225?
- 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-37225 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-37225?
- 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 FlexRIC v2.0.0 due to a cross-layer validation mismatch between the E42 and E2AP protocols. The E42 layer decoder (src/lib/e2ap/v3_01/dec/e2ap_msg_dec_asn.c) accepts an E42_RIC_SUBSCRIPTION_REQUEST even if the ricEventTriggerDefinition field is empty. However, when the iApp attempts to forward this request, the E2AP encoder (src/lib/e2ap/v3_01/enc/e2ap_msg_enc_asn.c) triggers a SIGABRT via a non-empty constraint assertion. A remote, unauthenticated attacker can exploit this by sending a malformed SCTP packet to port 36422, causing the iApp process to terminate.
Affected products
- EURECOM FlexRIC v2.0.0 through commit 6a595d8b
Timeline
- 2025-11-12: other: Vulnerability confirmed present in commit 6a595d8b
- 2026-06-01: disclosed: CVE published and advisory released by researcher