Skip to main content
VulnerabilityPublished

CVE-2026-37227: flexric · Reachable Assertion

Affects flexricSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubmosaic5g/flexricpkg:github/mosaic5g/flexricOther threatsAffected
  • =2.0.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is available, consider restricting network access to the near-RT RIC process port (36421) to trusted sources only to reduce exposure. Monitor for unusual crashes or restarts of the near-RT RIC process.

Description

FlexRIC v2.0.0 has a vulnerability where certain whitelisted but unimplemented E2AP message types cause the near-RT RIC process to crash due to reachable assert(0) calls. A remote unauthenticated attacker can exploit this by sending a specially crafted E2AP PDU, such as E2nodeConfigurationUpdate, to trigger a SIGABRT and cause a denial of service. The vulnerability does not impact confidentiality or integrity but results in high availability impact. No patch or official remediation guidance is currently available.

References

Community reviews

Loading reviews…