LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22697: CryptoLib Has Heap Buffer Overflow Vulnerability in KMC Base64 Decode Handling (KMC JSON base64ciphertext/base64cleartext)

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, CryptoLib’s KMC crypto service integration is vulnerable to a heap buffer overflow when decoding Base64-encoded ciphertext/cleartext fields returned by the KMC service. The decode destination buffer is sized using an expected output length (len_data_out), but the Base64 decoder writes output based on the actual Base64 input length and does not enforce any destination size limit. An oversized Base64 string in the KMC JSON response can cause out-of-bounds writes on the heap, resulting in process crash and potentially code execution under certain conditions. This issue has been patched in version 1.4.3.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CryptoLib before 1.4.3 can crash when processing an oversized Base64 value returned by its KMC service integration. In mission or ground-system contexts using CryptoLib for SDLS-EP communications, this could disrupt availability and may allow code execution under certain conditions. The issue is fixed in CryptoLib 1.4.3.

Executive priority

Treat as high priority for any spacecraft, ground-station, or test environment relying on affected CryptoLib KMC integration. The main business risk is service disruption in security-critical communications, with possible code execution noted by the advisory. Patch affected deployments promptly.

Technical view

CVE-2026-22697 is a heap buffer overflow in NASA CryptoLib’s KMC JSON Base64 decode handling for base64ciphertext/base64cleartext fields. The destination buffer is sized from an expected output length, while decoding uses actual Base64 input length without enforcing the destination size. A malicious oversized KMC JSON response can write out of bounds. CVSS is 7.5 high.

Likely exposure

Exposure is likely limited to organizations using NASA CryptoLib before 1.4.3 with KMC crypto service integration. Systems not using CryptoLib, not using KMC integration, or already on 1.4.3 are not indicated as affected by the provided sources.

Exploitation context

The sources describe network-reachable, unauthenticated conditions with low attack complexity and no user interaction. They do not state active exploitation, and the CVE is not marked KEV in the provided bundle. Practical risk depends on whether an attacker can influence or impersonate the KMC JSON response path.

Researcher notes

Key review area is KMC service response parsing and Base64 decode buffer sizing before 1.4.3. The provided data supports CWE-122 heap overflow and availability impact. Code execution is described as possible under certain conditions, but no public exploit or active exploitation evidence is provided.

Mitigation direction

  • Upgrade NASA CryptoLib to version 1.4.3 or later.
  • Prioritize systems using KMC crypto service integration.
  • Restrict and monitor trust paths to KMC service responses.
  • If upgrade timing is unclear, check NASA CryptoLib advisory and release notes.

Validation and detection

  • Inventory applications and mission systems embedding NASA CryptoLib.
  • Confirm deployed CryptoLib versions are 1.4.3 or later.
  • Identify whether KMC JSON base64ciphertext or base64cleartext handling is enabled.
  • Review change management records for CryptoLib 1.4.3 deployment.
  • Monitor logs for unexpected KMC response parsing failures or crashes.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-122: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-22697 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2026-22697Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
nasaCryptoLib< 1.4.3Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-122 · source CWE mapping

Heap-based Buffer Overflow

Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.