dbcve.org
Reachable AssertionWeakness · CWE-617

CVE-2026-37220

HIGH · 7.5 CVSS v3.1 Published 2026-06-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
FlexRIC v2.0.0 crashes when an SCTP association is closed before an E2_SETUP_REQUEST is sent. The near-RT RIC assumes a mapping between SCTP association and E2 node always exists in the cleanup path and enforces this via assert(). A remote unauthenticated attacker can crash the near-RT RIC (port 36421) by simply completing an SCTP handshake and immediately disconnecting, without sending any E2AP message.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

FlexRIC v2.0.0 near-RT RIC crashes when an SCTP association is closed before an E2_SETUP_REQUEST message is received. The code asserts that a mapping between SCTP association and E2 node exists in cleanup paths, but this mapping is only created upon receiving E2_SETUP_REQUEST. Remote attackers can trigger the assert() failure by completing the SCTP handshake on port 36421 and immediately disconnecting without sending any E2AP message.

MitigationFix the cleanup path to handle missing SCTP-to-E2-node mappings gracefully (null check or conditional cleanup) rather than asserting. Consider creating the association tracking earlier in the SCTP connection lifecycle, before expecting E2_SETUP_REQUEST.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify FlexRIC installation and version
    Search for FlexRIC installation directories or check if the near-RT RIC binary is present. Look for version files or check the binary version using 'file' or 'strings' commands if found.
    Affected if FlexRIC version is 2.0.0 exactly or the specific commit that contains the vulnerable assert() in the SCTP cleanup path.
  2. Verify near-RT RIC service is running
    Check for running processes related to FlexRIC near-RT RIC. Look for processes named 'near-rt-ric', 'flexric', or similar. Use 'ps aux | grep -i flexric' or 'systemctl list-units | grep -i ric'.
    Affected if The near-RT RIC component of FlexRIC v2.0.0 is actively running.
  3. Confirm SCTP port 36421 is exposed
    Check if port 36421 is listening. Use 'ss -ln | grep 36421', 'netstat -ln | grep 36421', or 'lsof -i :36421'. Verify SCTP is enabled if the service uses SCTP for transport.
    Affected if Port 36421 is open and accepting SCTP connections, exposing the E2 interface to untrusted networks.
  4. Inspect for crash logs or assertion failures
    Search system logs (/var/log/syslog, /var/log/messages) and application logs for recent crashes. Look for patterns like 'assert', 'assertion failure', 'SIGABRT', or 'near-rt-ric' crash dumps.
    Affected if Recent crashes involving assertion failures in SCTP association cleanup are logged, indicating the vulnerability may have been triggered.
  5. Check for E2 node registrations
    If accessible, inspect the near-RT RIC runtime state to see if any E2 nodes have successfully registered. The vulnerability triggers when no E2 node mapping exists for an SCTP association.
    Affected if The system has accepted SCTP associations without corresponding E2_SETUP_REQUEST processing, creating the vulnerable state.

If running FlexRIC v2.0.0 with the near-RT RIC active and SCTP port 36421 exposed, the environment is vulnerable to remote crash via immediate SCTP disconnection before E2_SETUP_REQUEST.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Fix the cleanup path to handle missing SCTP-to-E2-node mappings gracefully (null check or conditional cleanup) rather than asserting. Consider creating the association tracking earlier in the SCTP connection lifecycle, before expecting E2_SETUP_REQUEST.

Recommended fix Moderate confidence

Latest stable release after v2.0.0 (check upstream repos for fixed version)

  1. 1. Obtain the latest release of FlexRIC from the upstream repository (github.com/eurecom-flexric or gitlab.eurecom.fr)
  2. 2. Review release notes or commit history for CVE-2026-37220 to identify the specific fix
  3. 3. Ensure the near-RT RIC service is stopped before upgrading
  4. 4. Backup current FlexRIC configuration files
  5. 5. Install the fixed version following standard build/install procedures
  6. 6. Restart the near-RT RIC service on port 36421
  7. 7. Verify the service is running and test SCTP connection handling
Caveat Minor - the fix modifies assertion behavior to handle edge cases gracefully rather than crashing

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-37220 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-37220 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data