CVE-2026-85745

Vendor product assessments

Showing 32 of 255 vendor product statements; 223 omitted. Read the full vendor advisory.

• mariadb10.11-0:10.11.18-4.1.1.hum1@aarch64 as a component of Red Hat Hardened Images · fixed

  Vendor assessment for this product only.

  pkg:rpm/redhat/[email protected]?arch=aarch64&distro=hummingbird-20251124&repository_id=public-hummingbird-aarch64-rpms

  • vendor fix: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ Vendor guidance
  • workaround: 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.1 ``` Then 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.

  Red Hat · CVE-2026-85745 · Updated 2026-10-19T17:26:05+00:00
• mariadb10.11-common-0:10.11.18-4.1.1.hum1@noarch@public-hummingbird-x86_64-rpms as a component of Red Hat Hardened Images · fixed

  Vendor assessment for this product only.

  pkg:rpm/redhat/[email protected]?arch=noarch&distro=hummingbird-20251124&repository_id=public-hummingbird-x86_64-rpms

  • vendor fix: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ Vendor guidance
  • workaround: 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.1 ``` Then 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.

  Red Hat · CVE-2026-85745 · Updated 2026-10-19T17:26:05+00:00
• mariadb10.11-embedded-0:10.11.18-4.1.1.hum1@x86_64 as a component of Red Hat Hardened Images · fixed

  Vendor assessment for this product only.

  pkg:rpm/redhat/[email protected]?arch=x86_64&distro=hummingbird-20251124&repository_id=public-hummingbird-x86_64-rpms

  • vendor fix: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ Vendor guidance
  • workaround: 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.1 ``` Then 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.

  Red Hat · CVE-2026-85745 · Updated 2026-10-19T17:26:05+00:00
• mariadb10.11-oqgraph-engine-0:10.11.18-4.1.1.hum1@x86_64 as a component of Red Hat Hardened Images · fixed

  Vendor assessment for this product only.

  pkg:rpm/redhat/[email protected]?arch=x86_64&distro=hummingbird-20251124&repository_id=public-hummingbird-x86_64-rpms

  • vendor fix: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ Vendor guidance
  • workaround: 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.1 ``` Then 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.

  Red Hat · CVE-2026-85745 · Updated 2026-10-19T17:26:05+00:00
• mariadb10.11-server-galera-0:10.11.18-4.1.1.hum1@s390x as a component of Red Hat Hardened Images · fixed

  Vendor assessment for this product only.

  pkg:rpm/redhat/[email protected]?arch=s390x&distro=hummingbird-20251124&repository_id=public-hummingbird-s390x-rpms

  • vendor fix: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ Vendor guidance
  • workaround: 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.1 ``` Then 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.

  Red Hat · CVE-2026-85745 · Updated 2026-10-19T17:26:05+00:00
• mariadb11.8-0:11.8.9-0.1.hum1@s390x as a component of Red Hat Hardened Images · fixed

  Vendor assessment for this product only.

  pkg:rpm/redhat/[email protected]?arch=s390x&distro=hummingbird-20251124&repository_id=public-hummingbird-s390x-rpms

  • vendor fix: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ Vendor guidance
  • workaround: 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.1 ``` Then 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.

  Red Hat · CVE-2026-85745 · Updated 2026-10-19T17:26:05+00:00
• mariadb11.8-common-0:11.8.9-0.1.hum1@noarch@public-hummingbird-x86_64-rpms as a component of Red Hat Hardened Images · fixed

  Vendor assessment for this product only.

  pkg:rpm/redhat/[email protected]?arch=noarch&distro=hummingbird-20251124&repository_id=public-hummingbird-x86_64-rpms

  • vendor fix: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ Vendor guidance
  • workaround: 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.1 ``` Then 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.

  Red Hat · CVE-2026-85745 · Updated 2026-10-19T17:26:05+00:00
• mariadb11.8-embedded-0:11.8.9-0.1.hum1@aarch64 as a component of Red Hat Hardened Images · fixed

  Vendor assessment for this product only.

  pkg:rpm/redhat/[email protected]?arch=aarch64&distro=hummingbird-20251124&repository_id=public-hummingbird-aarch64-rpms

  • vendor fix: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ Vendor guidance
  • workaround: 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.1 ``` Then 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.

  Red Hat · CVE-2026-85745 · Updated 2026-10-19T17:26:05+00:00
• mariadb11.8-oqgraph-engine-0:11.8.9-0.1.hum1@aarch64 as a component of Red Hat Hardened Images · fixed

  Vendor assessment for this product only.

  pkg:rpm/redhat/[email protected]?arch=aarch64&distro=hummingbird-20251124&repository_id=public-hummingbird-aarch64-rpms

  • vendor fix: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ Vendor guidance
  • workaround: 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.1 ``` Then 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.

  Red Hat · CVE-2026-85745 · Updated 2026-10-19T17:26:05+00:00
• mariadb11.8-server-0:11.8.9-0.1.hum1@x86_64 as a component of Red Hat Hardened Images · fixed

  Vendor assessment for this product only.

  pkg:rpm/redhat/[email protected]?arch=x86_64&distro=hummingbird-20251124&repository_id=public-hummingbird-x86_64-rpms

  • vendor fix: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ Vendor guidance
  • workaround: 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.1 ``` Then 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.

  Red Hat · CVE-2026-85745 · Updated 2026-10-19T17:26:05+00:00
• mariadb11.8-test-0:11.8.9-0.1.hum1@x86_64 as a component of Red Hat Hardened Images · fixed

  Vendor assessment for this product only.

  pkg:rpm/redhat/[email protected]?arch=x86_64&distro=hummingbird-20251124&repository_id=public-hummingbird-x86_64-rpms

  • vendor fix: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ Vendor guidance
  • workaround: 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.1 ``` Then 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.

  Red Hat · CVE-2026-85745 · Updated 2026-10-19T17:26:05+00:00
• mariadb as a component of Red Hat Enterprise Linux 10 · known affected

  Vendor assessment for this product only.

  pkg:rpm/redhat/mariadb

  • workaround: 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.1 ``` Then 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.
  • none available: Fix deferred

  Red Hat · CVE-2026-85745 · Updated 2026-10-19T17:26:05+00:00
• mariadb-gssapi-server as a component of Red Hat Enterprise Linux 10 · known affected

  Vendor assessment for this product only.

  pkg:rpm/redhat/mariadb-gssapi-server

  • workaround: 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.1 ``` Then 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.
  • none available: Fix deferred

  Red Hat · CVE-2026-85745 · Updated 2026-10-19T17:26:05+00:00
• mariadb11.8 as a component of Red Hat Enterprise Linux 10 · known affected

  Vendor assessment for this product only.

  pkg:rpm/redhat/mariadb11.8

  • workaround: 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.1 ``` Then 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.
  • none available: Fix deferred

  Red Hat · CVE-2026-85745 · Updated 2026-10-19T17:26:05+00:00
• mariadb11.8-gssapi-server as a component of Red Hat Enterprise Linux 10 · known affected

  Vendor assessment for this product only.

  pkg:rpm/redhat/mariadb11.8-gssapi-server

  • workaround: 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.1 ``` Then 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.
  • none available: Fix deferred

  Red Hat · CVE-2026-85745 · Updated 2026-10-19T17:26:05+00:00
• Judy.src (mariadb:10.11) as a component of Red Hat Enterprise Linux 8 · known affected

  Vendor assessment for this product only.

  pkg:rpm/redhat/Judy?arch=src&rpmmod=mariadb:10.11

  • workaround: 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.1 ``` Then 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.
  • none available: Fix deferred

  Red Hat · CVE-2026-85745 · Updated 2026-10-19T17:26:05+00:00
• mariadb-embedded (mariadb:10.11) as a component of Red Hat Enterprise Linux 8 · known affected

  Vendor assessment for this product only.

  pkg:rpm/redhat/mariadb-embedded?rpmmod=mariadb:10.11

  • workaround: 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.1 ``` Then 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.
  • none available: Fix deferred

  Red Hat · CVE-2026-85745 · Updated 2026-10-19T17:26:05+00:00
• mariadb-test (mariadb:10.11) as a component of Red Hat Enterprise Linux 8 · known affected

  Vendor assessment for this product only.

  pkg:rpm/redhat/mariadb-test?rpmmod=mariadb:10.11

  • workaround: 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.1 ``` Then 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.
  • none available: Fix deferred

  Red Hat · CVE-2026-85745 · Updated 2026-10-19T17:26:05+00:00
• mariadb-devel (mariadb:11.8) as a component of Red Hat Enterprise Linux 9 · known affected

  Vendor assessment for this product only.

  pkg:rpm/redhat/mariadb-devel?rpmmod=mariadb:11.8

  • workaround: 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.1 ``` Then 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.
  • none available: Fix deferred

  Red Hat · CVE-2026-85745 · Updated 2026-10-19T17:26:05+00:00
• mariadb-gssapi-server (mariadb:11.8) as a component of Red Hat Enterprise Linux 9 · known affected

  Vendor assessment for this product only.

  pkg:rpm/redhat/mariadb-gssapi-server?rpmmod=mariadb:11.8

  • workaround: 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.1 ``` Then 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.
  • none available: Fix deferred

  Red Hat · CVE-2026-85745 · Updated 2026-10-19T17:26:05+00:00
• mariadb-server-utils (mariadb:11.8) as a component of Red Hat Enterprise Linux 9 · known affected

  Vendor assessment for this product only.

  pkg:rpm/redhat/mariadb-server-utils?rpmmod=mariadb:11.8

  • workaround: 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.1 ``` Then 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.
  • none available: Fix deferred

  Red Hat · CVE-2026-85745 · Updated 2026-10-19T17:26:05+00:00
• mariadb (mariadb:11.8) as a component of Red Hat Enterprise Linux 9 · known affected

  Vendor assessment for this product only.

  pkg:rpm/redhat/mariadb?rpmmod=mariadb:11.8

  • workaround: 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.1 ``` Then 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.
  • none available: Fix deferred

  Red Hat · CVE-2026-85745 · Updated 2026-10-19T17:26:05+00:00
• mariadb as a component of Red Hat Enterprise Linux 7 · known not affected

  Vendor assessment for this product only.

  Reason: vulnerable code not present

  pkg:rpm/redhat/mariadb

  Red Hat · CVE-2026-85745 · Updated 2026-10-19T17:26:05+00:00
• mariadb-server as a component of Red Hat Enterprise Linux 7 · known not affected

  Vendor assessment for this product only.

  Reason: vulnerable code not present

  pkg:rpm/redhat/mariadb-server

  Red Hat · CVE-2026-85745 · Updated 2026-10-19T17:26:05+00:00
• galera (mariadb:10.3) as a component of Red Hat Enterprise Linux 8 · known not affected

  Vendor assessment for this product only.

  Reason: vulnerable code not present

  pkg:rpm/redhat/galera?rpmmod=mariadb:10.3

  Red Hat · CVE-2026-85745 · Updated 2026-10-19T17:26:05+00:00
• mariadb-errmsg (mariadb:10.3) as a component of Red Hat Enterprise Linux 8 · known not affected

  Vendor assessment for this product only.

  Reason: vulnerable code not present

  pkg:rpm/redhat/mariadb-errmsg?rpmmod=mariadb:10.3

  Red Hat · CVE-2026-85745 · Updated 2026-10-19T17:26:05+00:00
• mariadb-server (mariadb:10.3) as a component of Red Hat Enterprise Linux 8 · known not affected

  Vendor assessment for this product only.

  Reason: vulnerable code not present

  pkg:rpm/redhat/mariadb-server?rpmmod=mariadb:10.3

  Red Hat · CVE-2026-85745 · Updated 2026-10-19T17:26:05+00:00
• mariadb-backup as a component of Red Hat Enterprise Linux 9 · known not affected

  Vendor assessment for this product only.

  Reason: vulnerable code not present

  pkg:rpm/redhat/mariadb-backup

  Red Hat · CVE-2026-85745 · Updated 2026-10-19T17:26:05+00:00
• mariadb-gssapi-server as a component of Red Hat Enterprise Linux 9 · known not affected

  Vendor assessment for this product only.

  Reason: vulnerable code not present

  pkg:rpm/redhat/mariadb-gssapi-server

  Red Hat · CVE-2026-85745 · Updated 2026-10-19T17:26:05+00:00
• mariadb-test as a component of Red Hat Enterprise Linux 9 · known not affected

  Vendor assessment for this product only.

  Reason: vulnerable code not present

  pkg:rpm/redhat/mariadb-test

  Red Hat · CVE-2026-85745 · Updated 2026-10-19T17:26:05+00:00
• mariadb-connect-engine as a component of Red Hat OpenStack Platform 13 (Queens) · known not affected

  Vendor assessment for this product only.

  Reason: vulnerable code not present

  pkg:rpm/redhat/mariadb-connect-engine

  Red Hat · CVE-2026-85745 · Updated 2026-10-19T17:26:05+00:00
• mariadb.src as a component of Red Hat OpenStack Platform 13 (Queens) · known not affected

  Vendor assessment for this product only.

  Reason: vulnerable code not present

  pkg:rpm/redhat/mariadb?arch=src

  Red Hat · CVE-2026-85745 · Updated 2026-10-19T17:26:05+00:00