CVE-2026-92157 json
F´: FileDownlink SendPartial integer overflow lets legal startOffset/length values reach a reachable assertion
published 2mo ago modified 23d ago also EUVD-2026-101407 , GHSA-hcmw-g425-8h9g
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository nasa/fprime. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 48%
- public exploits
- 0
- none known
Summary
F´ (F Prime) is a framework that enables development and deployment of spaceflight and other embedded software applications. Prior to 4.3.0, Svc::FileDownlink SendPartial range validation is vulnerable because unchecked startOffset plus length arithmetic bypasses the range check and stores a wrapped m_endOffset that is inconsistent with m_byteOffset. When an existing source file is larger than a valid startOffset and a SendPartial command supplies a length whose U32 sum with that offset wraps below the file size, under standard F Prime assertion handling, the first data-packet transition reaches FW_ASSERT and aborts or resets the process, causing denial of service. This issue is fixed in version 4.3.0.
Patch / fix
- nasa fprime 4.3.0
- github.com/nasa/fprime@33fe2a4 commit
- github.com/nasa/fprime@95eeb5c commit
- github.com/nasa/fprime#5565 pull request
- github.com/nasa/fprime/releases/tag/v4.3.0 release
Is CVE-2026-92157 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 23d ago
Exploit prediction
0.58% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- github.com https://github.com/nasa/fprime/security/advisories/GHSA-hcmw-g425-8h9g referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Inferred packages
No advisory lists a package for this vulnerability yet. The CVE names these as products and links their GitHub repository, and the package registry names the same repository, so they are probably the affected packages. Low confidence: the versions are the CVE’s own for the product, and a stack check reports the package as unchecked when there are none.
| ecosystem | package | repository | affected |
|---|---|---|---|
| pypi | fprime | nasa/fprime | no versions given |
Affected products
- nasa fprime
Classification
References
- github.com /nasa/fprime/pull/5565
- github.com /nasa/fprime/commit/33fe2a4fe3fd5ff1b14985669fbad09f070e9914
- github.com /nasa/fprime/commit/95eeb5cfb44e5609eff0887f0e11e640cdacef6b
-
github.com
/nasa/fprime/security/advisories/GHSA-hcmw-g425-8h9g
exploit, advisory
- github.com /nasa/fprime/releases/tag/v4.3.0
Sources
- CVE List CVE-2026-92157
- NVD CVE-2026-92157
- Maintainer advisory GHSA-hcmw-g425-8h9g
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of nasa/fprime published their own advisory on GitHub. Reviewed sources take precedence over it.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.