CVE-2026-85745
Description
A flaw was found in MariaDB. An authenticated database user can exploit an out-of-bounds read vulnerability by supplying a specially crafted spatial geometry to the ST_Area function. This issue allows reading beyond allocated memory buffers, leading to unauthorized information disclosure of internal process memory. An attacker could use this disclosed data to facilitate further attacks, such as bypassing security protections like Address Space Layout Randomization (ASLR).
Statement
This vulnerability is rated as Moderate because successful exploitation requires valid database credentials and only leaks memory contents without directly altering state or causing a service crash. In standard Red Hat Enterprise Linux deployments, the issue is constrained to authenticated database sessions executing spatial geometry operations on MariaDB instances. While the disclosed memory could assist an attacker in bypassing binary protections such as ASLR, arbitrary code execution is not achievable through this flaw alone and would require chaining with a separate memory corruption vulnerability. Consequently, the isolated impact is limited to unauthorized information disclosure within the database process memory space.
Mitigation
Restrict network access to the MariaDB service so that only trusted client systems or the local host can connect.
1. If the database is only accessed locally, configure MariaDB to listen exclusively on localhost by editing `/etc/my.cnf.d/mariadb-server.cnf` under the `[mysqld]` section:
bind-address = 127.0.0.1Then restart the MariaDB service:
systemctl restart mariadb
2. If remote access is necessary, use firewalld to block untrusted networks and permit access only from designated IP addresses or subnets:
firewall-cmd --permanent --remove-service=mariadb
firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="192.168.1.0/24" service name="mariadb" accept'
firewall-cmd --reload
Caveats: Restricting network reachability limits exposure to authorized networks and prevents untrusted network users from connecting, but it does not protect against malicious queries executed by already authenticated database accounts on permitted networks.
Warning: Modifying firewall rules or binding addresses requires reloading firewall configurations or restarting the MariaDB service, which will terminate existing database connections and disrupt active services.
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).
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 4.3 | N/A | 4.3 |
| 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 | None | N/A | None |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
cve.org: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Red Hat CVSS v3 Score Explanation
Aligned with upstream GHSA-p7v9-24h4-mch8 (CVE-2026-85745). Standalone OOB heap read in Gis_multi_polygon::area() via crafted MULTIPOLYGON; discloses partial heap contents to authenticated SQL user. No integrity or availability impact on its own.
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.
