Fixed packages 7
| Release | Package | Fixed in |
|---|---|---|
| Red Hat · Hardened Images 1 hummingbird:1 | bind | 0:9.18.48-1.hum1 |
| Red Hat · Hardened Images 1 hummingbird:1 | bind-chroot | 0:9.18.48-1.hum1 |
| Red Hat · Hardened Images 1 hummingbird:1 | bind-devel | 0:9.18.48-1.hum1 |
| Red Hat · Hardened Images 1 hummingbird:1 | bind-dnssec-utils | 0:9.18.48-1.hum1 |
| Red Hat · Hardened Images 1 hummingbird:1 | bind-doc | 0:9.18.48-1.hum1 |
| Red Hat · Hardened Images 1 hummingbird:1 | bind-libs | 0:9.18.48-1.hum1 |
| Red Hat · Hardened Images 1 hummingbird:1 | bind-utils | 0:9.18.48-1.hum1 |
Vulnerabilities 8
-
High 8.6CVE-2025-40778 Public exploit
Cache poisoning attacks with unsolicited RRs
Under certain circumstances, BIND is too lenient when accepting records from answers, allowing an attacker to inject forged data into the cache. This issue affects BIND 9 versions 9.11.0 through 9.16.50, 9.18.0 through 9.18.39, 9.20.0 through 9.20.13, 9.21.0 …
-
High 8.6
Cache poisoning due to weak PRNG
In specific circumstances, due to a weakness in the Pseudo Random Number Generator (PRNG) that is used, it is possible for an attacker to predict the source port and query ID that BIND will use. This issue affects BIND 9 versions 9.16.0 through 9.16.50, 9.18.…
-
High 7.5
Malformed BRID/HHIT records can cause named to terminate unexpectedly
Malformed BRID/HHIT records can cause `named` to terminate unexpectedly. This issue affects BIND 9 versions 9.18.40 through 9.18.43, 9.20.13 through 9.20.17, 9.21.12 through 9.21.16, 9.18.40-S1 through 9.18.43-S1, and 9.20.13-S1 through 9.20.17-S1.
-
High 7.5CVE-2025-8677 EPSS 11%
Resource exhaustion via malformed DNSKEY handling
Querying for records within a specially crafted zone containing certain malformed DNSKEY records can lead to CPU exhaustion. This issue affects BIND 9 versions 9.18.0 through 9.18.39, 9.20.0 through 9.20.13, 9.21.0 through 9.21.12, 9.18.11-S1 through 9.18.39-…
-
High 7.5
Excessive NSEC3 iterations cause high CPU load during insecure delegation validation
If a BIND resolver is performing DNSSEC validation and encounters a maliciously crafted zone, the resolver may consume excessive CPU. Authoritative-only servers are generally unaffected, although there are circumstances where authoritative servers may make re…
-
High 7.5
Memory leak in code preparing DNSSEC proofs of non-existence
A specially crafted domain can be used to cause a memory leak in a BIND resolver simply by querying this domain. This issue affects BIND 9 versions 9.20.0 through 9.20.20, 9.21.0 through 9.21.19, and 9.20.9-S1 through 9.20.20-S1. BIND 9 versions 9.18.0 throug…
-
Medium 6.5
Authenticated query containing a TKEY record may cause named to terminate unexpectedly
Under certain conditions, `named` may crash when processing a correctly signed query containing a TKEY record. The affected code can only be reached if an incoming request has a valid transaction signature (TSIG) from a key declared in the `named` configurati…
-
Medium 5.4
A stack use-after-return flaw in SIG(0) handling code may enable ACL bypass
A use-after-return vulnerability exists in the `named` server when handling DNS queries signed with SIG(0). Using a specially-crafted DNS request, an attacker may be able to cause an ACL to improperly (mis)match an IP address. In a default-allow ACL (denying …
References
-
article
https://images.redhat.com/
-
report
https://access.redhat.com/security/cve/CVE-2025-8677
-
article
https://access.redhat.com/security/updates/classification/
-
report
https://access.redhat.com/security/cve/CVE-2025-40780
-
report
https://access.redhat.com/security/cve/CVE-2025-40778
-
report
https://access.redhat.com/security/cve/CVE-2025-13878
-
report
https://access.redhat.com/security/cve/CVE-2026-3591
-
report
https://access.redhat.com/security/cve/CVE-2026-3119
-
report
https://access.redhat.com/security/cve/CVE-2026-3104
-
report
https://access.redhat.com/security/cve/CVE-2026-1519
-
advisory
https://security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_6935.json
-
report
https://bugzilla.redhat.com/show_bug.cgi?id=2405830
-
advisory
https://www.cve.org/CVERecord?id=CVE-2025-8677
-
advisory
https://nvd.nist.gov/vuln/detail/CVE-2025-8677
-
report
https://bugzilla.redhat.com/show_bug.cgi?id=2431600
-
advisory
https://www.cve.org/CVERecord?id=CVE-2025-13878
-
advisory
https://nvd.nist.gov/vuln/detail/CVE-2025-13878
-
report
https://bugzilla.redhat.com/show_bug.cgi?id=2405827
-
advisory
https://www.cve.org/CVERecord?id=CVE-2025-40778
-
advisory
https://nvd.nist.gov/vuln/detail/CVE-2025-40778
-
report
https://bugzilla.redhat.com/show_bug.cgi?id=2405829
-
advisory
https://www.cve.org/CVERecord?id=CVE-2025-40780
-
advisory
https://nvd.nist.gov/vuln/detail/CVE-2025-40780
-
report
https://bugzilla.redhat.com/show_bug.cgi?id=2451305
-
advisory
https://www.cve.org/CVERecord?id=CVE-2026-1519
-
advisory
https://nvd.nist.gov/vuln/detail/CVE-2026-1519
-
article
https://downloads.isc.org/isc/bind9/9.18.47
-
article
https://downloads.isc.org/isc/bind9/9.20.21
-
article
https://downloads.isc.org/isc/bind9/9.21.20
-
article
https://kb.isc.org/docs/cve-2026-1519
-
report
https://bugzilla.redhat.com/show_bug.cgi?id=2451310
-
advisory
https://www.cve.org/CVERecord?id=CVE-2026-3104
-
advisory
https://nvd.nist.gov/vuln/detail/CVE-2026-3104
-
article
https://kb.isc.org/docs/cve-2026-3104
-
report
https://bugzilla.redhat.com/show_bug.cgi?id=2451308
-
advisory
https://www.cve.org/CVERecord?id=CVE-2026-3119
-
advisory
https://nvd.nist.gov/vuln/detail/CVE-2026-3119
-
article
https://kb.isc.org/docs/cve-2026-3119
-
report
https://bugzilla.redhat.com/show_bug.cgi?id=2451298