# CVE-2026-37221: Null dereference in n/a

> A remote unauthenticated attacker can crash the FlexRIC near-RT RIC by sending a forged subscription response with an unknown ID, 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-46rx-wmhr-cj2m

## What is CVE-2026-37221?

CVE-2026-37221 is a high-severity 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 RIC_SUBSCRIPTION_RESPONSE with an unknown ric_id that has no corresponding pending event. The near-RT RIC uses assert() to enforce the existence of a pending event during response processing. A remote unauthenticated attacker can send a forged RIC_SUBSCRIPTION_RESPONSE to the near-RT RIC (port 36421) to cause SIGABRT in Debug builds or NULL pointer dereference (SIGSEGV) in Release builds.

Weakness: CWE-617 (Reachable Assertion)

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


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

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

## Is CVE-2026-37221 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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