RHSA-2026:24013HighCVSS 7.5

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

Published
June 7, 2026
Last Modified
August 31, 2026

🔗 CVE IDs covered (3)

CVE-2026-41292 →CVE-2026-42534 →CVE-2026-44390 →

📋 Description

CVE-2026-41292 — unbound: Unbound: Denial of Service via excessive EDNS options CVE-2026-42534 — unbound: Unbound: Denial of Service due to degraded resolution performance in jostle logic CVE-2026-44390 — unbound: Unbound: Denial of Service due to excessive resource consumption with large DNS Resource Record Sets

🎯 Affected products5

  • Red Hat Hardened Images
  • unbound-main@aarch64 as a component of Red Hat Hardened Images
  • unbound-main@noarch as a component of Red Hat Hardened Images
  • unbound-main@src as a component of Red Hat Hardened Images
  • unbound-main@x86_64 as a component of Red Hat Hardened Images

✅ Remediation

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ Workaround: Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. Until patched, restrict the resolver to authorized client networks via firewall and apply DNS rate limiting per source IP. Service watchdog and cgroup limits provide resilience but are not a substitute for patching. Workaround: To mitigate the risk of denial of resolution service, restrict Unbound's network exposure. Configure Unbound to only accept queries from trusted internal networks and to forward its own queries exclusively to trusted, well-maintained upstream DNS servers. This reduces the opportunity for an adversary to interact with or act as a malicious upstream for the vulnerable Unbound instance. After modifying Unbound's configuration, a service restart is required for changes to take effect. This may temporarily interrupt DNS resolution services. Workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

🔗 References (7)