CVE-2026-127428
Description
A flaw was found in the MySQL Geographic Information System (GIS) component. A remote attacker with low privileges can exploit this vulnerability over network protocols to cause the database server to hang or crash repeatedly, resulting in a Denial of Service (DoS). Additionally, successful exploitation may allow unauthorized read access to a subset of accessible database data.
Statement
This vulnerability is rated as Important because authenticated remote users with minimal access rights can cause complete service disruptions and read unauthorized database records. In standard Red Hat deployments, access to the MySQL service is typically restricted to trusted applications and internal networks. However, because valid credentials with basic query execution capabilities are sufficient to compromise availability and data confidentiality across the instance, the overall risk remains elevated for multi-tenant environments.
Mitigation
Restrict network exposure of the MySQL service to trusted clients and internal networks only.
1. Using firewalld, restrict general network access to MySQL and permit only trusted IP addresses:
firewall-cmd --permanent --zone=public --remove-service=mysql
firewall-cmd --permanent --zone=trusted --add-source=<trusted_network_or_IP>
firewall-cmd --reload
2. Alternatively, bind the MySQL service to localhost if remote database connections are not required by setting the following in `/etc/my.cnf.d/mysql-server.cnf`:
[mysqld]Then apply changes by restarting the service:
bind-address = 127.0.0.1
systemctl restart mysqld
Caveats:
Restricting network access will prevent any client outside the trusted network or localhost from connecting to the database server.
Warning: Reloading firewall rules or restarting the mysqld service will temporarily drop active database connections and disrupt ongoing operations.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 7.1 | N/A | 7.1 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | Low | N/A | Low |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | Low | N/A | Low |
| Integrity Impact | None | N/A | None |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:H
cve.org: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:H
Understanding the Weakness (CWE)
Confidentiality
Technical Impact: Read Memory
An attacker could get secret values such as cryptographic keys, PII, memory addresses, or other information that could be used in additional attacks.
Confidentiality
Technical Impact: Bypass Protection Mechanism
Out-of-bounds memory could contain memory addresses or other information that can be used to bypass ASLR and other protection mechanisms in order to improve the reliability of exploiting a separate weakness for code execution.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
An attacker could cause a segmentation fault or crash by causing memory to be read outside of the bounds of the buffer. This is especially likely when the code reads a variable amount of data and assumes that a sentinel exists to stop the read operation, such as a NUL in a string.
Other
Technical Impact: Varies by Context
The read operation could produce other undefined or unexpected results.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.