Quick answers
- Is CVE-2026-37229 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-37229 being exploited in the wild.
- How severe is CVE-2026-37229?
- 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-37229?
- 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-37229 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-37229?
- 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 e2ap_create_pdu() function within FlexRIC's E2AP message decoding logic. The vulnerability is located in the ASN.1 PER decoding helper, which incorrectly uses an assertion to verify that decoding was successful (RC_OK). Because this assertion is reached before any protocol-level validation, a remote, unauthenticated attacker can trigger a process crash (SIGABRT) by sending a malformed SCTP payload (such as a single 0x00 byte) to ports 36421 or 36422. All E2AP protocol versions (v1.01, v2.03, and v3.01) are affected. As of publication, no official patch is available, and users are advised to restrict SCTP access to trusted peers.
Affected products
- EURECOM FlexRIC v2.0.0 through commit 6a595d8b
Timeline
- 2026-06-01: disclosed
- 2026-06-01: advisory