Moderate Security Update for MySQL: Addressing Multiple Vulnerabilities
Summary
ALSA-2026:5580: Moderate: mysql:8.0 security update. Affects mecab across 2 version ranges.
< 0.996-2.module_el8.6.0+3340+d764b636
< 0.996-2.module_el8.10.0+3965+b415b607
Fixed in 0.996-2.module_el8.6.0+3340+d764b636 or 0.996-2.module_el8.10.0+3965+b415b607, depending on the release line you run. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
MySQL is a widely-used multi-user, multi-threaded SQL database server that includes the MySQL server daemon (mysqld) along with various client programs and libraries. It is known for its reliability, performance, and ease of use, making it a popular choice for web applications and data management. However, like any software, it is susceptible to vulnerabilities that can compromise its security and functionality.
Vulnerability Detail
The vulnerabilities identified in MySQL include unspecified issues related to the optimizer, InnoDB, DDL, and thread pooling. These vulnerabilities can potentially allow unauthorized access or manipulation of data, leading to severe security risks. The vulnerabilities were disclosed in the January 2026 CPU and are tracked under multiple CVEs, including CVE-2026-21936, CVE-2026-21937, CVE-2026-21941, CVE-2026-21948, CVE-2026-21964, and CVE-2026-21968.
How To Fix
Fixed versions by release line
The minimum fixed version depends on the release line you run.
sudo dnf update mecab-
< 0.996-2.module_el8.6.0+3340+d764b6360.996-2.module_el8.6.0+3340+d764b636 -
< 0.996-2.module_el8.10.0+3965+b415b6070.996-2.module_el8.10.0+3965+b415b607
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
As a temporary measure, consider restricting access to the MySQL server and implementing additional security measures such as firewalls and access controls until the update can be applied.
Conclusion
The recent security update for MySQL addresses multiple vulnerabilities that could compromise the integrity and security of the database server. It is crucial for users to update their installations to the patched versions to mitigate these risks and ensure the continued security of their applications.
See every vulnerability recorded for mecab →
FAQ
The vulnerabilities are unspecified issues related to the optimizer, InnoDB, DDL, and thread pooling that can lead to unauthorized access or data manipulation.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.
The vulnerabilities are tracked under CVE-2026-21936, CVE-2026-21937, CVE-2026-21941, CVE-2026-21948, CVE-2026-21964, and CVE-2026-21968.
Yes, if exploited, these vulnerabilities could lead to unauthorized data access or manipulation, potentially resulting in data loss.
Implement temporary security measures such as restricting access to the MySQL server and using firewalls until you can apply the necessary updates.
Related vulnerabilities
Recent vulnerabilities recorded for mecab.
