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-22026: CWE-789: Memory Allocation with Excessive Size Value in nasa CryptoLib

0
High
VulnerabilityCVE-2026-22026cvecve-2026-22026cwe-789
Published: Sat Jan 10 2026 (01/10/2026, 00:22:35 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 libcurl write_callback function in the KMC crypto service client allows unbounded memory growth by reallocating response buffers without any size limit or overflow check. A malicious KMC server can return arbitrarily large HTTP responses, forcing the client to allocate excessive memory until the process is terminated by the OS. This issue has been patched in version 1.4.3.

AI-Powered Analysis

AILast updated: 01/10/2026, 01:03:33 UTC

Technical Analysis

CVE-2026-22026 is a vulnerability identified in NASA's CryptoLib, a software library implementing the CCSDS Space Data Link Security Protocol - Extended Procedures (SDLS-EP) to secure communications between spacecraft running the core Flight System (cFS) and ground stations. The flaw exists in versions prior to 1.4.3 within the libcurl write_callback function used by the Key Management Client (KMC) crypto service. Specifically, the client reallocates response buffers without imposing any size limits or performing overflow checks. This allows a malicious KMC server to send arbitrarily large HTTP responses, forcing the client to allocate excessive amounts of memory. The uncontrolled memory growth can exhaust system resources, causing the process to be terminated by the operating system, resulting in a denial of service (DoS). The vulnerability does not require authentication or user interaction and can be exploited remotely over the network. Although no known exploits are currently in the wild, the issue has been addressed in CryptoLib version 1.4.3 by adding appropriate limits and checks on buffer sizes during reallocation. The vulnerability is classified under CWE-789 (Memory Allocation with Excessive Size Value) and has a CVSS 4.0 base score of 8.2, indicating high severity due to its potential to disrupt availability and ease of exploitation.

Potential Impact

For European organizations, particularly those involved in aerospace, satellite communications, and space research, this vulnerability poses a significant risk of denial of service. Exploitation could disrupt critical communication links between spacecraft and ground stations, potentially impacting mission operations, data integrity, and command/control capabilities. The unbounded memory allocation can lead to system crashes or forced process termination, causing service outages. Given the specialized nature of CryptoLib and its use in space-related applications, affected organizations may face operational delays, increased recovery costs, and potential safety risks if spacecraft communications are interrupted. Additionally, organizations relying on this library for secure communications may experience degraded trust in their security posture. The lack of known exploits currently reduces immediate risk, but the vulnerability’s ease of exploitation and high impact warrant urgent remediation to prevent future attacks.

Mitigation Recommendations

The primary mitigation is to upgrade all instances of NASA CryptoLib to version 1.4.3 or later, where the vulnerability has been patched. Organizations should audit their environments to identify any deployments of CryptoLib versions prior to 1.4.3, especially within KMC crypto service clients. Implement strict input validation and size limits on HTTP response buffers to prevent unbounded memory allocation. Network-level controls such as firewall rules and intrusion detection systems should monitor and restrict communications with untrusted or unknown KMC servers. Employ runtime memory monitoring and process watchdogs to detect and recover from abnormal memory usage patterns. Additionally, organizations should engage with NASA or relevant vendors for any further security advisories or patches. Regularly updating and testing incident response plans to handle potential denial of service scenarios related to this vulnerability is also recommended.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-01-05T22:30:38.718Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6961a1f6ed32c7f018d59bf3

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

Last enriched: 1/10/2026, 1:03:33 AM

Last updated: 1/10/2026, 10:38:26 AM

Views: 7

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