# CVE-2026-37227: Denial of service in n/a

> A remote unauthenticated attacker can crash the near-RT RIC process by sending specific E2AP messages that trigger assertion failures.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Jun 2026
- **Updated:** 1 Jun 2026
- **Also known as:** GHSA-2m6w-7qwv-3jcx

## What is CVE-2026-37227?

CVE-2026-37227 is a high-severity denial of service vulnerability in n/a, published on 1 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

FlexRIC v2.0.0 contains reachable assert(0) calls in stub message handlers for whitelisted but unimplemented E2AP message types in the near-RT RIC. A remote unauthenticated attacker can send a decodable E2AP PDU of such a type (e.g., E2nodeConfigurationUpdate) to crash the near-RT RIC process (port 36421) via SIGABRT. The message passes whitelist validation but triggers an unconditional assertion in the handler.

Weakness: CWE-617 (Reachable Assertion)

## Which versions are affected by CVE-2026-37227?


## How do I fix CVE-2026-37227?

No fix has been published for CVE-2026-37227 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-37227 being exploited?

There is no known exploitation of CVE-2026-37227 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-37227 and fix it if it is affected.

What it is: CVE-2026-37227 is a high-severity denial of service vulnerability in n/a, published on 1 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-37227 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-37227/ (Markdown: https://insights.sbomify.com/CVE-2026-37227/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-37227
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-37227
- OSV: https://osv.dev/vulnerability/CVE-2026-37227

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-37227/
Summaries are generated and may contain mistakes; the official description above is the record.