CVE-2026-22027·MariaDB vulnerability

How likely is exploitation

FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.21% — higher than 11% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.

Affected versions

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-server

How to check if you are affected

1. Run `mariadb --version` or `mysql --version` to check the installed MariaDB version; confirm it is 1.4.3 or later
2. Query the MariaDB error log for signs of memory corruption: `grep -i 'segmentation\|fault\|core dumped' /var/log/mysql/error.log`
3. 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`
4. 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

Related MariaDB CVEs

References

• https://github.com/nasa/CryptoLib/commit/2372efd3da1ccb226b4297222e25f41ecc84821d
• https://github.com/nasa/CryptoLib/releases/tag/v1.4.3
• https://github.com/nasa/CryptoLib/security/advisories/GHSA-3m35-m689-h29x
• https://github.com/nasa/CryptoLib/security/advisories/GHSA-3m35-m689-h29x