Memory corruption via unchecked SBN message length
Published Aug 30, 2026 · Updated Aug 30, 2026
Buffer overflow in the SBN TCP Module in NASA cFS 7.0.0 and 7.0.1 allows adjacent-network attackers to corrupt process memory. The Recv function derives ToRead from the peer-controlled MsgSz header and passes that count to OS_read at an offset into a fixed-size RecvBufs entry without checking the remaining capacity. No authentication or user interaction is required, but the attacker must reach the SBN TCP service from the local network; execution or crash behavior has not been demonstrated.
Summary
What happened
Buffer overflow in the SBN TCP Module in NASA cFS 7.0.0 and 7.0.1 allows adjacent-network attackers to corrupt process memory. The Recv function derives ToRead from the peer-controlled MsgSz header and passes that count to OS_read at an offset into a fixed-size RecvBufs entry without checking the remaining capacity. No authentication or user interaction is required, but the attacker must reach the SBN TCP service from the local network; execution or crash behavior has not been demonstrated.
The record
- CVE
- CVE-2026-82479
- Published
- Aug 30, 2026
- Updated
- Aug 30, 2026
- Vendor
- NASA
- Product
- Core Flight System (cFS)
- Classifications
- CWE-119, CWE-120, T1210
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 30, 2026CVE publishedPublication date reported by the CVE source.
- Aug 30, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=7.0.0
- Affected versionversion=7.0.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo