CVE-2026-5475 | NASA cFS up to 7.0.0 CCSDS Header Size cfe_sb_priv.c CFE_SB_TransmitMsg memory corruption (Issue 953)
VulDBArchived Apr 03, 2026✓ Full text saved
A vulnerability labeled as critical has been found in NASA cFS up to 7.0.0 . This impacts the function CFE_SB_TransmitMsg of the file cfe_sb_priv.c of the component CCSDS Header Size Handler . Executing a manipulation can lead to memory corruption. This vulnerability appears as CVE-2026-5475 . The attacker needs to be present on the local network. There is no available exploit. The project was informed of the problem early through an issue report but has not responded yet.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-355079 · CVE-2026-5475 · ISSUE 953
NASA CFS UP TO 7.0.0 CCSDS HEADER SIZE CFE_SB_PRIV.C CFE_SB_TRANSMITMSG MEMORY CORRUPTION
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
5.3 $0-$5k 0.85+
Summaryinfo
A vulnerability marked as critical has been reported in NASA cFS up to 7.0.0. Affected is the function CFE_SB_TransmitMsg of the file cfe_sb_priv.c of the component CCSDS Header Size Handler. The manipulation leads to memory corruption. This vulnerability is traded as CVE-2026-5475. There is no exploit available. The project was informed of the problem early through an issue report but has not responded yet.
Detailsinfo
A vulnerability, which was classified as critical, has been found in NASA cFS up to 7.0.0. This issue affects the function CFE_SB_TransmitMsg of the file cfe_sb_priv.c of the component CCSDS Header Size Handler. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is confidentiality, integrity, and availability.
It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2026-5475. The exploitation is known to be easy. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 04/03/2026).
The project was informed of the problem early through an issue report but has not responded yet.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Productinfo
Vendor
NASA
Name
cFS
Version
7.0
Website
Product: https://github.com/nasa/cFS/
CPE 2.3info
🔒
CPE 2.2info
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv3info
VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Memory corruption
CWE: CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Partially
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: no mitigation known
Status: 🔍
0-Day Time: 🔒
Timelineinfo
04/03/2026 Advisory disclosed
04/03/2026 +0 days VulDB entry created
04/03/2026 +0 days VulDB entry last update
Sourcesinfo
Product: github.com
Advisory: 953
Status: Not defined
CVE: CVE-2026-5475 (🔒)
GCVE (CVE): GCVE-0-2026-5475
GCVE (VulDB): GCVE-100-355079
Entryinfo
Created: 04/03/2026 09:56
Changes: 04/03/2026 09:56 (55)
Complete: 🔍
Submitter: 0rbitingZer0
Cache ID: 99:EF9:101
Submitinfo
Accepted
Submit #781951: NASA cFS 7.0.0 CFE_SB_TransmitMsg memcpy trusts CCSDS header size without sourc (by 0rbitingZer0)
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸