Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-21897: CWE-787: Out-of-bounds Write in nasa CryptoLib

0
High
VulnerabilityCVE-2026-21897cvecve-2026-21897cwe-787
Published: Sat Jan 10 2026 (01/10/2026, 00:07:16 UTC)
Source: CVE Database V5
Vendor/Project: nasa
Product: CryptoLib

Description

CryptoLib provides a software-only solution using the CCSDS Space Data Link Security Protocol - Extended Procedures (SDLS-EP) to secure communications between a spacecraft running the core Flight System (cFS) and a ground station. Prior to version 1.4.3, the Crypto_Config_Add_Gvcid_Managed_Parameters function only checks whether gvcid_counter > GVCID_MAN_PARAM_SIZE. As a result, it allows up to the 251st entry, which causes a write past the end of the array, overwriting gvcid_counter located immediately after gvcid_managed_parameters_array[250]. This leads to an out-of-bounds write, and the overwritten gvcid_counter may become an arbitrary value, potentially affecting the parameter lookup/registration logic that relies on it. This issue has been patched in version 1.4.3.

AI-Powered Analysis

AILast updated: 01/10/2026, 01:04:38 UTC

Technical Analysis

CVE-2026-21897 is an out-of-bounds write vulnerability classified under CWE-787 found in NASA's CryptoLib, a software-only implementation of the CCSDS Space Data Link Security Protocol - Extended Procedures (SDLS-EP). This library secures communications between spacecraft running the core Flight System (cFS) and ground stations. The vulnerability exists in the Crypto_Config_Add_Gvcid_Managed_Parameters function, which manages an array of GVCID managed parameters. The function only checks if the gvcid_counter exceeds GVCID_MAN_PARAM_SIZE, allowing up to the 251st entry to be written, which is beyond the array boundary of 250 elements. This results in an out-of-bounds write that overwrites the adjacent gvcid_counter variable. The corrupted gvcid_counter can take arbitrary values, potentially causing incorrect parameter lookup or registration behavior. This flaw can be triggered remotely without requiring authentication or user interaction, making it a network-exploitable vulnerability. The impact includes potential degradation or manipulation of secure communications between spacecraft and ground stations, affecting confidentiality, integrity, and availability. The vulnerability was patched in CryptoLib version 1.4.3, and no known exploits have been reported in the wild as of the publication date. The CVSS v3.1 base score is 7.3, indicating high severity due to the ease of exploitation and the critical nature of the affected systems.

Potential Impact

For European organizations, particularly those involved in aerospace, satellite communications, and space research, this vulnerability poses a significant risk. Compromise of CryptoLib could lead to unauthorized manipulation or disruption of spacecraft-to-ground communications, potentially resulting in loss of sensitive telemetry data, command injection, or denial of service. This could affect mission-critical operations, data integrity, and confidentiality of space missions. The impact extends to national space agencies, aerospace contractors, and research institutions using or integrating the affected CryptoLib versions. Disruption or compromise of space communication links could have cascading effects on satellite operations, scientific data collection, and national security interests. Given the specialized nature of the software, the scope is limited to organizations using the cFS and CryptoLib, but the criticality of these systems amplifies the impact severity.

Mitigation Recommendations

1. Immediate upgrade to CryptoLib version 1.4.3 or later, where the vulnerability is patched. 2. Conduct an inventory of all systems and software components using CryptoLib, especially those involved in spacecraft communication and ground station operations. 3. Implement strict input validation and boundary checks in any custom code interfacing with CryptoLib to prevent out-of-bounds conditions. 4. Monitor network traffic for anomalous patterns that could indicate exploitation attempts targeting spacecraft communication protocols. 5. Employ defense-in-depth strategies including network segmentation to isolate critical space communication infrastructure. 6. Collaborate with space agencies and vendors to ensure timely dissemination of patches and security advisories. 7. Perform security audits and penetration testing focused on space communication systems to identify residual vulnerabilities. 8. Establish incident response plans tailored to aerospace communication disruptions.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-01-05T17:24:36.930Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6961a1f5ed32c7f018d59bd3

Added to database: 1/10/2026, 12:48:53 AM

Last enriched: 1/10/2026, 1:04:38 AM

Last updated: 1/10/2026, 9:25:22 PM

Views: 5

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats