CVE-2026-44432VulnerabilityPublished 11 Apr 2026Updated 31 Oct 2026

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

Affects Red Hat waybackpySource GCVE Database

Compare

Not known to be exploited · fixed in Red Hat package updates : patch Red Hat waybackpy soon.

Data as of 31 Oct 2026, 20:20 UTC

Severity

High

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

EPSS: 0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.0.6_12, 0.52.1_1, 1.50.4 +1

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Apr 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 31 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.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
Homebrewwaybackpy`pkg:brew/waybackpy`Other threats	Affected >=3.0.6_9 <3.0.6_12	Fixed in 3.0.6_12
Homebrewtoot`pkg:brew/toot`Other threats	Affected >=0.51.0_1 <0.52.1_1	Fixed in 0.52.1_1
Homebrewggshield`pkg:brew/ggshield`Other threats	Affected >=1.48.0 <1.50.4	Fixed in 1.50.4
Homebrewparliament`pkg:brew/parliament`Other threats	Affected >=1.6.4_2 <1.6.4_4	Fixed in 1.6.4_4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Red Hat has released updated RPM packages (version 21.1.8-1.1.hum1) for the affected components. Applying these updates will remediate the vulnerabilities. No alternative mitigations are indicated or recommended by the vendor. Users should follow Red Hat's official update procedures to deploy the fixed packages. Since no exploits are known in the wild, urgent exploitation mitigation is not indicated beyond applying the official fixes.

Description

This update includes the following RPMs: llvm: * clang-21.1.8-1.1.hum1 (aarch64, x86_64) * clang-analyzer-21.1.8-1.1.hum1 (aarch64, x86_64) * clang-devel-21.1.8-1.1.hum1 (aarch64, x86_64) * clang-libs-21.1.8-1.1.hum1 (aarch64, x86_64) * clang-resource-filesystem-21.1.8-1.1.hum1 (aarch64, x86_64) * clang-tools-extra-21.1.8-1.1.hum1 (aarch64, x86_64) * clang-tools-extra-devel-21.1.8-1.1.hum1 (aarch64, x86_64) * compiler-rt-21.1.8-1.1.hum1 (aarch64, x86_64) * git-clang-format-21.1.8-1.1.hum1 (aarch64, x86_64) * libcxx-21.1.8-1.1.hum1 (aarch64, x86_64) * libcxx-devel-21.1.8-1.1.hum1 (aarch64, x86_64) * libcxx-static-21.1.8-1.1.hum1 (aarch64, x86_64) * libcxxabi-21.1.8-1.1.hum1 (aarch64, x86_64) * libcxxabi-devel-21.1.8-1.1.hum1 (aarch64, x86_64) * libcxxabi-static-21.1.8-1.1.hum1 (aarch64, x86_64) * libomp-21.1.8-1.1.hum1 (aarch64, x86_64) * libomp-devel-21.1.8-1.1.hum1 (aarch64, x86_64) * lld-21.1.8-1.1.hum1 (aarch64, x86_64) * lld-devel-21.1.8-1.1.hum1 (aarch64, x86_64) * lld-libs-21.1.8-1.1.hum1 (aarch64, x86_64) * lldb-21.1.8-1.1.hum1 (aarch64, x86_64) * lldb-devel-21.1.8-1.1.hum1 (aarch64, x86_64) * llvm-21.1.8-1.1.hum1 (aarch64, x86_64) * llvm-bolt-21.1.8-1.1.hum1 (aarch64, x86_64) * llvm-cmake-utils-21.1.8-1.1.hum1 (aarch64, x86_64) * llvm-devel-21.1.8-1.1.hum1 (aarch64, x86_64) * llvm-doc-21.1.8-1.1.hum1 (noarch) * llvm-filesystem-21.1.8-1.1.hum1 (aarch64, x86_64) * llvm-googletest-21.1.8-1.1.hum1 (aarch64, x86_64) * llvm-libs-21.1.8-1.1.hum1 (aarch64, x86_64) * llvm-libunwind-21.1.8-1.1.hum1 (aarch64, x86_64) * llvm-libunwind-devel-21.1.8-1.1.hum1 (aarch64, x86_64) * llvm-libunwind-static-21.1.8-1.1.hum1 (aarch64, x86_64) * llvm-static-21.1.8-1.1.hum1 (aarch64, x86_64) * llvm-test-21.1.8-1.1.hum1 (aarch64, x86_64) * mlir-21.1.8-1.1.hum1 (aarch64, x86_64) * mlir-devel-21.1.8-1.1.hum1 (aarch64, x86_64) * mlir-static-21.1.8-1.1.hum1 (aarch64, x86_64) * polly-21.1.8-1.1.hum1 (aarch64, x86_64) * polly-devel-21.1.8-1.1.hum1 (aarch64, x86_64) * python3-clang-21.1.8-1.1.hum1 (aarch64, x86_64) * python3-lit-21.1.8-1.1.hum1 (noarch) * python3-lldb-21.1.8-1.1.hum1 (aarch64, x86_64) * python3-mlir-21.1.8-1.1.hum1 (aarch64, x86_64) * llvm-21.1.8-1.1.hum1.src (src)

Impact

The vulnerabilities addressed in this advisory can lead to memory corruption, double free conditions, or resource exhaustion, potentially causing denial of service or application crashes. These issues affect the availability and stability of systems using the affected Red Hat Hardened Images RPMs. No confidentiality or integrity impacts are explicitly stated. The severity is rated high by Red Hat, reflecting the potential for significant disruption if exploited.

Summary

Red Hat issued a security advisory (RHSA-2026:7634) for Red Hat Hardened Images RPMs addressing multiple vulnerabilities including CVE-2026-44432. The update includes a comprehensive set of LLVM-related RPM packages (version 21.1.8-1.1.hum1) for aarch64 and x86_64 architectures. The vulnerabilities involve issues classified under CWE-120 (buffer copy without checking size), CWE-805 (buffer access with incorrect length value), CWE-409 (double free), and CWE-770 (allocation of resources without limits or throttling). The advisory does not specify detailed technical exploitation methods but indicates these flaws could lead to memory corruption or resource exhaustion. The vendor advisory confirms that fixes are included in the updated RPM packages and recommends applying these updates. No active exploits are known in the wild.

CWE-120Buffer Copy without Checking Size of Input (Classic Buffer Overflow) (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #11
The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
OWASP Cheat Sheets
Docker Security (opens in a new tab)
XML Security (opens in a new tab)
OWASP ASVS 4.0.3
V5.4.1 (opens in a new tab)
V14.1.2 (opens in a new tab)
V13.3.1 (opens in a new tab)
Attack patterns
Buffer Overflow via Environment Variables (opens in a new tab)
Overflow Buffers (opens in a new tab)
Client-side Injection-induced Buffer Overflow (opens in a new tab)
Filter Failure through Buffer Overflow (opens in a new tab)
MIME Conversion (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-805Buffer Access with Incorrect Length Value (opens in a new tab)
Base weaknessLikelihood of exploit: High
The product uses a sequential operation to read or write a buffer, but it uses an incorrect length value that causes it to access memory that is outside of the bounds of the buffer.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Overflow Buffers (opens in a new tab)
SOAP Array Overflow (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-409Improper Handling of Highly Compressed Data (Data Amplification) (opens in a new tab)
Base weakness
The product does not handle or incorrectly handles a compressed input with a very high compression ratio that produces a large output.
OWASP Cheat Sheets
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V12.1.2 (opens in a new tab)
V12.1.1 (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

What to do

Affected software

Description

AI analysisMachine-generated, updated 16 Aug 2026, 17:30 UTC

WeaknessesCWE-120, CWE-805, CWE-409 +1

Technical details

References

Community reviews

Related threats