CVE-2026-44431VulnerabilityPublished 9 Jul 2026Updated 29 Oct 2026

Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update

Affects Red HatSource GCVE Database

Compare

Not known to be exploited.

Data as of 29 Oct 2026, 23:59 UTC

Severity

High

Rated by Threat Radar · No CVSS score from NVD or the CNA

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

Description

This update includes the following RPMs: mariadb11.8: * mariadb-11.8.8-3.hum1 (aarch64, x86_64) * mariadb-backup-11.8.8-3.hum1 (aarch64, x86_64) * mariadb-client-utils-11.8.8-3.hum1 (noarch) * mariadb-common-11.8.8-3.hum1 (noarch) * mariadb-connect-engine-11.8.8-3.hum1 (aarch64, x86_64) * mariadb-cracklib-password-check-11.8.8-3.hum1 (aarch64, x86_64) * mariadb-devel-11.8.8-3.hum1 (aarch64, x86_64) * mariadb-embedded-11.8.8-3.hum1 (aarch64, x86_64) * mariadb-embedded-devel-11.8.8-3.hum1 (aarch64, x86_64) * mariadb-errmsg-11.8.8-3.hum1 (noarch) * mariadb-gssapi-server-11.8.8-3.hum1 (aarch64, x86_64) * mariadb-oqgraph-engine-11.8.8-3.hum1 (aarch64, x86_64) * mariadb-pam-11.8.8-3.hum1 (aarch64, x86_64) * mariadb-rocksdb-engine-11.8.8-3.hum1 (x86_64) * mariadb-s3-engine-11.8.8-3.hum1 (aarch64, x86_64) * mariadb-server-11.8.8-3.hum1 (aarch64, x86_64) * mariadb-server-galera-11.8.8-3.hum1 (aarch64, x86_64) * mariadb-server-utils-11.8.8-3.hum1 (noarch) * mariadb-sphinx-engine-11.8.8-3.hum1 (aarch64, x86_64) * mariadb-test-11.8.8-3.hum1 (aarch64, x86_64) * mariadb11.8-11.8.8-3.hum1.src (src)

CWE-201Insertion of Sensitive Information Into Sent Data (opens in a new tab)
Base weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.
Requirements
Specify which data in the software should be regarded as sensitive. Consider which types of users should have access to which types of data.
Implementation
Ensure that any possibly sensitive data specified in the requirements is verified with designers to ensure that it is either a calculated risk or mitigated elsewhere.
System Configuration
Setup default error messages so that unexpected errors do not disclose sensitive information.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Choosing Message Identifier (opens in a new tab)
Exploiting Incorrectly Configured SSL/TLS (opens in a new tab)
WiFi MAC Address Tracking (opens in a new tab)
WiFi SSID Tracking (opens in a new tab)
Cellular Broadcast Message Request (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-770Allocation of Resources Without Limits or Throttling (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #25
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
Requirements
Clearly specify the minimum and maximum expectations for capabilities, and dictate which behaviors are acceptable when resource allocation reaches limits.
Architecture and Design
Limit the amount of resources that are accessible to unprivileged users. Set per-user limits for resources. Allow the system administrator to define these limits. Be careful to avoid CWE-410.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.4 (opens in a new tab)
V13.4.1 (opens in a new tab)
V11.1.4 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Exponential Data Expansion (opens in a new tab)
Serialized Data Parameter Blowup (opens in a new tab)
Serialized Data with Nested Payloads (opens in a new tab)
Oversized Serialized Data Payloads (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

Description

WeaknessesCWE-201, CWE-770

Technical details

References

Community reviews

Related threats