# CVE-2026-105164: NASA cFS cfe_fs_api.c CFE_FS_ParseInputFileNameEx out-of-bounds

> Remote attackers can trigger an out-of-bounds read in NASA cFS, potentially causing denial of service or information disclosure.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Oct 2026
- **Updated:** 25 Oct 2026
- **Also known as:** GHSA-v57f-4hqc-phxq

## What is CVE-2026-105164?

CVE-2026-105164 is a medium-severity memory corruption vulnerability in NASA cFS, published on 4 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A flaw has been found in NASA cFS up to 7.0.1. This issue affects the function CFE_FS_ParseInputFileNameEx of the file cfe/modules/fs/fsw/src/cfe_fs_api.c. This manipulation causes out-of-bounds read. Remote exploitation of the attack is possible. The pull request to fix this issue awaits acceptance.

Weakness: CWE-125 (Out-of-bounds Read), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

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

## Is CVE-2026-105164 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-105164 is a medium-severity memory corruption vulnerability in NASA cFS, published on 4 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-105164 in the wild and no public exploit code.

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

## Sources

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

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