CVE-2026-22697 identifies a heap-based buffer overflow vulnerability 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 KMC crypto service integration prior to version 1.4.3, specifically during the decoding of Base64-encoded ciphertext or cleartext fields returned by the KMC service. The decode destination buffer is allocated based on an expected output length (len_data_out), but the Base64 decoder writes output according to the actual Base64 input length without enforcing the destination buffer size limit. If an attacker supplies an oversized Base64 string in the KMC JSON response, this leads to out-of-bounds writes on the heap. Such heap corruption can cause the process to crash, resulting in denial of service, and under certain conditions, may allow an attacker to execute arbitrary code remotely. The vulnerability requires no authentication or user interaction, increasing its risk profile. Although no exploits are currently known in the wild, the vulnerability's CVSS score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) reflects its high impact on availability and ease of exploitation. The issue has been addressed in CryptoLib version 1.4.3 by properly bounding the Base64 decode output to the allocated buffer size.

For European organizations, particularly those involved in aerospace, satellite communications, and space research, this vulnerability poses a significant risk. Exploitation can lead to denial of service through process crashes, disrupting critical communication links between spacecraft and ground stations. In worst-case scenarios, it may allow remote code execution, potentially compromising the confidentiality and integrity of sensitive space mission data and control systems. Such disruptions could impact satellite operations, scientific missions, and national security-related space assets. Given the specialized nature of CryptoLib and its use in space communication protocols, the affected organizations are likely niche but critical. The impact extends to any European aerospace contractors, research institutions, and governmental agencies relying on this software for secure spacecraft communications. The absence of required authentication or user interaction lowers the barrier for exploitation, increasing the threat level.

European organizations should immediately verify if they use CryptoLib versions prior to 1.4.3 in their space communication infrastructure. The primary mitigation is to upgrade to CryptoLib version 1.4.3 or later, where the vulnerability is patched. Additionally, organizations should implement strict validation of Base64 input lengths before decoding to prevent buffer overflows. Employ runtime protections such as heap integrity checks and address space layout randomization (ASLR) to mitigate exploitation impact. Network-level filtering to restrict unexpected or malformed KMC service responses can reduce exposure. Conduct thorough code audits and fuzz testing on cryptographic service integrations to identify similar vulnerabilities. Finally, establish monitoring for anomalous process crashes or unusual KMC service responses that may indicate exploitation attempts.