# CVE-2026-15352: NASA Core Flight System (cFS) Health & Safety (HS) Application NULL Pointer Dereference

> A null pointer dereference in the NASA cFS Health & Safety application causes a crash during telemetry processing, resulting in denial of service.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/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:** 16 Jul 2026
- **Updated:** 17 Jul 2026
- **Also known as:** GHSA-8472-2q4c-5q85

## What is CVE-2026-15352?

CVE-2026-15352 is a high-severity vulnerability in NASA Core Flight System (cFS) Health & Safety (HS) Application, published on 16 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability exists in the Health & Safety (HS) application of NASA's Core Flight System (cFS). The flaw allows the application to crash via segmentation fault when processing a routine Housekeeping Telemetry request, leading to denial of service.

Weakness: CWE-476 (NULL Pointer Dereference)

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


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

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

## Is CVE-2026-15352 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15352 is a high-severity vulnerability in NASA Core Flight System (cFS) Health & Safety (HS) Application, published on 16 Jul 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-15352 in the wild and no public exploit code.

Affected product: NASA Core Flight System (cFS) Health & Safety (HS) Application. 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-15352/ (Markdown: https://insights.sbomify.com/CVE-2026-15352/index.md)
```

## Sources

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

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