LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22027: CryptoLib Vulnerable to Heap Buffer Overflow in MariaDB SA Hexstring Conversion

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 convert_hexstring_to_byte_array() function in the MariaDB SA interface writes decoded bytes into a caller-provided buffer without any capacity check. When importing SA fields from the database (e.g., IV, ARSN, ABM), a malformed or oversized hex string in the database can overflow the destination buffer, corrupting adjacent heap memory. This issue has been patched in version 1.4.3.

MediumCVSS 5.7Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-22027 affects NASA CryptoLib before 1.4.3. A malformed or oversized hex string in MariaDB security association data can cause a heap buffer overflow during import. This could corrupt memory and affect integrity or availability, but the CVSS vector indicates high privileges and local access are required.

Executive priority

Treat as a targeted remediation item for spacecraft or ground-station environments using CryptoLib with MariaDB-backed security associations. It is not described as remotely exploitable or actively exploited, but affected mission systems should be updated promptly because memory corruption can impact availability and integrity.

Technical view

The vulnerable function is convert_hexstring_to_byte_array() in the MariaDB SA interface. Before 1.4.3, it writes decoded bytes into a caller-provided buffer without checking capacity. Oversized SA fields such as IV, ARSN, or ABM can overflow heap memory. The issue is classified as CWE-122 and has a CVSS 4.0 score of 5.7.

Likely exposure

Exposure is limited to deployments using NASA CryptoLib versions before 1.4.3 with the MariaDB SA interface. The attacker must be able to influence relevant database-backed SA hex fields and has high privilege requirements per the CVSS vector.

Exploitation context

No active exploitation is stated in the provided sources, and the CVE is not listed as KEV. Practical exploitation appears constrained by local access, high privileges, and the need for malformed database content, but successful abuse may corrupt heap memory and affect availability or integrity.

Researcher notes

Evidence comes from the CVE record and NASA GitHub advisory, commit, and v1.4.3 release. The public description names the vulnerable function and database fields but does not provide broader product exposure details. Avoid assuming impact beyond CryptoLib before 1.4.3 and the MariaDB SA import path.

Mitigation direction

  • Upgrade NASA CryptoLib to version 1.4.3 or later.
  • Review vendor advisory and release notes before deploying the update.
  • Restrict write access to MariaDB SA fields to trusted administrators only.
  • Monitor vendor guidance for any additional hardening recommendations.

Validation and detection

  • Inventory systems using NASA CryptoLib and identify installed versions.
  • Confirm whether the MariaDB SA interface is enabled or used.
  • Verify affected deployments are upgraded to CryptoLib 1.4.3 or later.
  • Review database permissions around SA fields such as IV, ARSN, and ABM.
Prepared
Confidence
high
Sources
5

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

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. 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-22027 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
Medium
CVSS
5.7 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N

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
4Source 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
5.7CVSS 4.0MediumCVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

5.7Medium
CVSS 4.0 vector shape for CVE-2026-22027Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone
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.