CVE-2026-22027·MariaDB vulnerability
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.
- Severity
- medium
- Software
- MariaDB
- Fixed in
- 1.4.3
- Published
- 2026-01-10
Affected versions
Until: 1.4.3
Fixed in: 1.4.3
How to fix this CVE
Update MariaDB to version 1.4.3 or later to patch a buffer overflow vulnerability in the hex string conversion function used when loading security parameters from the database. This flaw could allow authenticated users with database write access to corrupt heap memory by inserting malformed hex strings into SA fields. Promptly apply the security update and restart the MariaDB service to mitigate the risk.
sudo dnf update mariadb-serverDefensia detects this vulnerability
How to check if you are affected
- Run `mariadb --version` or `mysql --version` to check the installed MariaDB version; confirm it is 1.4.3 or later
- Query the MariaDB error log for signs of memory corruption: `grep -i 'segmentation\|fault\|core dumped' /var/log/mysql/error.log`
- Check for unexpected database crashes or restarts around the time frame when untrusted hex strings may have been inserted: `journalctl -u mariadb -n 100 --no-pager`
- Verify the patch was applied by checking the file modification times: `stat /usr/sbin/mariadbd | grep Modify` and confirm it matches the update timestamp
FAQ
What is CVE-2026-22027?
CVE-2026-22027 is a buffer overflow vulnerability in MariaDB's hex string conversion function that processes security parameters (IV, ARSN, ABM) loaded from the database. An attacker with database write privileges can craft oversized hex strings to overflow a fixed-size buffer and corrupt adjacent heap memory.
Is CVE-2026-22027 being actively exploited?
No, CVE-2026-22027 is not currently listed on CISA's KEV catalog and no public exploits are available. However, the vulnerability should still be patched promptly since it requires only database access to trigger.
What versions of MariaDB are affected by CVE-2026-22027?
All versions of MariaDB prior to 1.4.3 are vulnerable. The exact earliest affected version is not specified in the advisory, so it is safest to assume all versions before 1.4.3 contain the flaw.
How do I check if my server is vulnerable to CVE-2026-22027?
Run `mariadb --version` and verify the output shows version 1.4.3 or later. If the version is below 1.4.3, your installation is vulnerable and requires immediate patching.
Does Defensia detect CVE-2026-22027?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If MariaDB is installed on a monitored server, CVE-2026-22027 will appear in your dashboard with remediation steps.
Related MariaDB CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-22027. Free for 1 server.
Get started free