# CVE-2026-92152: F´: Unvalidated Port Index in GenericHub

> Remote attackers can trigger out-of-bounds memory access in F Prime GenericHub via unvalidated port indices, potentially achieving code execution or causing denial of service.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-vv4x-5pmf-m59g

## What is CVE-2026-92152?

CVE-2026-92152 is a critical memory corruption vulnerability in nasa fprime, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

F´ (F Prime) is a framework that enables development and deployment of spaceflight and other embedded software applications. From 4.1.0 until 4.2.0, Svc::GenericHub output-port dispatch is vulnerable because the deserialized port field is passed to serialOut_out, bufferOut_out, eventOut_out, or tlmOut_out without an explicit range check. When a remote hub packet supplies a port index outside the configured output-port array, assert-enabled builds abort, while builds without assertions can access an output-port array out of bounds, corrupt heap memory, and potentially allow remote code execution. This issue is fixed in version 4.2.0.

Weakness: CWE-129 (Improper Validation of Array Index)

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


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

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

## Is CVE-2026-92152 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92152 is a critical memory corruption vulnerability in nasa fprime, published on 14 Oct 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-92152 in the wild and no public exploit code.

Affected product: nasa fprime. 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-92152/ (Markdown: https://insights.sbomify.com/CVE-2026-92152/index.md)
```

## Sources

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

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