F´ (F Prime) is a framework that enables development and deployment of spaceflight and other embedded software applications. Prior to 4.3.0, Svc::FileUplink handling of Fw::FilePacket::StartPacket destination paths FileUplink copies the packet-controlled destinationPath and opens it for writing without canonicalization or confinement to an upload directory. When a peer able to send file-uplink packets supplies an absolute, traversing, or otherwise attacker-selected writable destination path, files can be created or overwritten at attacker-selected writable filesystem locations, affecting integrity and potentially availability. This issue is fixed in version 4.3.0.
CVE-2026-92153
HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence
“—” beside the score: it is equal to the CVSS score beside it.
This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (37th 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
Also known asEUVD-2026-101468 (ENISA EUVD)Source: ENISA EUVD
7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.1Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 7.1
- EG Score
- 7.1HIGHmedium confidence
- EG Risk
- 32EG Risk 32/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity71% × 45%Impact severity (EG Severity): CVSS 7.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.4% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.Exploitation none (CISA Vulnrichment) · Automatable no (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. - EPSS PROB
- 0.4%
- EPSS %ILE
- 37th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (7.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
- EG Likelihood
- 0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (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 15, 2026Patch available. Sources: github_commit, github_pr, github_release, github.
GitHub advisoryMentions a patch (unverified)
Arbitrary File Write in Svc::FileUplink via attacker-controlled StartPacket.destinationPath · Advisory · nasa/fprime · GitHub
https://github.com/nasa/fprime/security/advisories/GHSA-5rfj-hw2g-vwmvGitHub release Patch Available
v4.3.0
Patch available: nasa/fprime v4.3.0
https://github.com/nasa/fprime/releases/tag/v4.3.0GitHub pull request
Add Os::SandboxedFile and Os::FilePathUtils for directory-sandboxed file access
Fix merged in nasa/fprime PR #5320 on 2026-07-09 — awaiting tagged release
https://github.com/nasa/fprime/pull/5320GitHub commit
commit 4c8b9c0b8692 (nasa/fprime)
Fix landed in nasa/fprime commit 4c8b9c0b8692 — awaiting tagged release
https://github.com/nasa/fprime/commit/4c8b9c0b8692b0d47cbd5f2ccec61c74aa02b893Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 21× 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-27 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.4% · 37th percentile
- 2026-10-25 13:50 UTCEG score recompute
- 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-22 15:07 UTCEG score recompute
- 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-18 03:00 UTCEG score recompute
- 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-15 16:31 UTCEG score recompute
- 2026-10-15 15:24 UTCEG score recompute
- 2026-10-14 17:30 UTCEG score recompute
- 2026-10-14 16:44 UTCEG score recomputeFirst assessed: 7.1 HIGH
- 2026-10-14 16:40 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-92153?
CVE-2026-92153 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.3.0, Svc::FileUplink handling of Fw::FilePacket::StartPacket destination paths FileUplink copies the packet-controlled destinationPath and opens it for writing…
When was the CVE record for CVE-2026-92153 published?
The CVE record for CVE-2026-92153 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-92153 actively exploited?
CVE-2026-92153 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (37th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-92153?
CVE-2026-92153 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-92153?
A fix for CVE-2026-92153 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-92153
Is Your Infrastructure Affected by CVE-2026-92153?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.