CVE-2026-92151

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (41st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

F´ (F Prime) is a framework that enables development and deployment of spaceflight and other embedded software applications. Prior to 4.2.0, Svc::Ccsds::SpacePacketDeframer dataIn_handler is vulnerable because the handler treats the minimum packet-length condition as FW_ASSERT rather than rejecting and returning the buffer. When a CCSDS telecommand frame leaves a payload of six bytes or fewer after TcDeframer removes its header and trailer, the assertion aborts or resets the flight-software process, causing denial of service. This issue is fixed in version 4.2.0.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
41st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 14, 2026

Last Modified

October 15, 2026

Advisory Details (4)

Auto-updated Oct 14, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github_release, github.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

SpacePacketDeframer Small Packet Assertion DoS · Advisory · nasa/fprime · GitHub

https://github.com/nasa/fprime/security/advisories/GHSA-4rjh-jqvx-r8j5
GitHub release Patch Available

v4.2.0

Patch available: nasa/fprime v4.2.0

https://github.com/nasa/fprime/releases/tag/v4.2.0
GitHub pull request

Omega

Fix merged in nasa/fprime PR #4919 on 2026-03-31 — awaiting tagged release

https://github.com/nasa/fprime/pull/4919
GitHub commit

commit cacdd555456b (nasa/fprime)

Fix landed in nasa/fprime commit cacdd555456b — awaiting tagged release

https://github.com/nasa/fprime/commit/cacdd555456bd83ab395b521d56c0330470ea798

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 7× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  2. 2026-10-15 19:27 UTCEG score recompute
  3. 2026-10-15 19:05 UTCEG score recompute
  4. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  5. 2026-10-14 17:30 UTCEG score recompute
  6. 2026-10-14 16:44 UTCEG score recomputeFirst assessed: 7.5 HIGH
  7. 2026-10-14 16:40 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-92151?
CVE-2026-92151 is a high-severity vulnerability; its CVE record was published on October 14, 2026. F´ (F Prime) is a framework that enables development and deployment of spaceflight and other embedded software applications. Prior to 4.2.0, Svc::Ccsds::SpacePacketDeframer dataInhandler is vulnerable because the handler treats the minimum packet-length condition as FWASSERT rather than rejecting…
When was the CVE record for CVE-2026-92151 published?
The CVE record for CVE-2026-92151 was published on October 14, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 15, 2026; the record at its source may have been updated since.
Is CVE-2026-92151 actively exploited?
CVE-2026-92151 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-92151?
CVE-2026-92151 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-92151?
A fix for CVE-2026-92151 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-92151

Explore →

Is Your Infrastructure Affected by CVE-2026-92151?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.