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

> Remote unauthenticated attackers can crash the FlexRIC iApp process by sending duplicate E2 setup requests, causing a denial of service.

- **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-9rvg-45qw-fjjr

## What is CVE-2026-37224?

CVE-2026-37224 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 crashes when receiving a duplicate E2_SETUP_REQUEST from the same or spoofed E2 Node. The iApp registry enforces node ID uniqueness via assert() rather than graceful rejection. A remote unauthenticated attacker can crash the iApp process (port 36421) by sending two E2_SETUP_REQUESTs with the same E2 node configuration, triggering SIGABRT.

Weakness: CWE-617 (Reachable Assertion)

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


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

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

## Is CVE-2026-37224 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-37224 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-37224 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-37224/ (Markdown: https://insights.sbomify.com/CVE-2026-37224/index.md)
```

## Sources

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

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