F´ (F Prime) is a framework that enables development and deployment of spaceflight and other embedded software applications. Prior to 4.2.0, Fw::FilePacket deserialization used by Svc::FileUplink is vulnerable because Header deserialization casts the byte to the Type enum without validating its range and FilePacket::fromSerialBuffer reaches a default FW_ASSERT. When a network file packet contains an unknown file-packet type byte, the assertion aborts or resets the default Ref application process, causing denial of service. This issue is fixed in version 4.2.0.
CVE-2026-92155
HIGHPre-NVD 7.57.5Trending — 3 sources updated this week
EchelonGraph scoreLOW confidence
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (28th 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: a secondary CVSS source
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).
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.5Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5HIGHlow confidence
- EG Risk
- 49EG Risk 49/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.Exploitation0% × 40%No KEV listing, EG-KEV tier or EPSS when EchelonGraph scored this CVE.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 none (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.4%
- EPSS %ILE
- 28th
- 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 none (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_pr, github_commit, github_release, github.
GitHub release Patch Available
v4.2.0
Patch available: nasa/fprime v4.2.0
https://github.com/nasa/fprime/releases/tag/v4.2.0GitHub commit
commit cacdd555456b (nasa/fprime)
Fix landed in nasa/fprime commit cacdd555456b — awaiting tagged release
https://github.com/nasa/fprime/commit/cacdd555456bd83ab395b521d56c0330470ea798GitHub pull request
Omega
Fix merged in nasa/fprime PR #4919 on 2026-03-31 — awaiting tagged release
https://github.com/nasa/fprime/pull/4919GitHub advisoryMentions a patch (unverified)🟡 PoC Available
FileUplink Unknown Packet Type Assertion DoS · Advisory · nasa/fprime · GitHub
https://github.com/nasa/fprime/security/advisories/GHSA-3534-8qg7-6cf5Weakness 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.
- 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.4% · 28th percentile
- 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.4% · 28th percentile
- 2026-10-15 16:31 UTCEG score recompute
- 2026-10-15 15:24 UTCEG score recompute
- 2026-10-14 18:26 UTCEG score recompute
- 2026-10-14 17:25 UTCEG score recomputeFirst assessed: 7.5 HIGH
- 2026-10-14 17:24 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-92155?
CVE-2026-92155 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, Fw::FilePacket deserialization used by Svc::FileUplink is vulnerable because Header deserialization casts the byte to the Type enum without validating its…
When was the CVE record for CVE-2026-92155 published?
The CVE record for CVE-2026-92155 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-92155 actively exploited?
CVE-2026-92155 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (28th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-92155?
CVE-2026-92155 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-92155?
A fix for CVE-2026-92155 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-92155
Is Your Infrastructure Affected by CVE-2026-92155?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.