bind: bump to 9.20.29 - #30558
Merged
Merged
bind: bump to 9.20.29#30558
Conversation
Includes several security fixes: - CVE-2026-19668 Prevent excessive CPU use validating crafted DNSSEC responses. - CVE-2026-19033 Require a TSIG on every message of incoming zone transfers. - CVE-2026-77119 Prevent a DNSSEC downgrade of secure delegations via unrelated NSEC3. - CVE-2026-19941 Prevent forged DNSSEC-validated NXDOMAIN responses. - CVE-2026-19666 DNS64 with break-dnssec could cause an assertion failure. - CVE-2026-19667 Reject negative cache records that do not fit in a dns_rdata_t. - CVE-2026-19662 Prevent resolver crash with cached DNSSEC proofs. - CVE-2026-75029 Discard repeated SOA, CNAME, and DNAME records when parsing DNS messages. - CVE-2026-77692 Fix an unauthenticated crash on HTTPS using SIG(0) - CVE-2026-81736 Cached HTTPS/SVCB aliases could exhaust resolver CPU. - CVE-2026-76163 Prevent TKEY queries from terminating named without global options. - CVE-2026-78301 Out-of-zone records in a zone database could be served as authoritative. - CVE-2026-80274 Crash on wildcard answers carrying both NSEC and NSEC3 proofs. - CVE-2026-81563 Following HTTPS/SVCB aliases could leak resolver cache memory. Complete upstream changelog is available at https://ftp.isc.org/isc/bind9/9.20.29/doc/arm/html/changelog.html Signed-off-by: Noah Meyerhans <frodo@morgul.net>
nmeyerhans
force-pushed
the
update-bind9
branch
from
September 18, 2026 15:10
74fa2fc to
64e5142
Compare
Contributor
Author
|
The CI failures seem unrelated to these changes. |
Member
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📦 Package Details
Maintainer: @nmeyerhans
Description:
New upstream stable release 9.20.29
Includes several security fixes:
CVE-2026-19668 Prevent excessive CPU use validating crafted DNSSEC responses.
CVE-2026-19033 Require a TSIG on every message of incoming zone transfers.
CVE-2026-77119 Prevent a DNSSEC downgrade of secure delegations via unrelated NSEC3.
CVE-2026-19941 Prevent forged DNSSEC-validated NXDOMAIN responses.
CVE-2026-19666 DNS64 with break-dnssec could cause an assertion failure.
CVE-2026-19667 Reject negative cache records that do not fit in a dns_rdata_t.
CVE-2026-19662 Prevent resolver crash with cached DNSSEC proofs.
CVE-2026-75029 Discard repeated SOA, CNAME, and DNAME records when parsing DNS messages.
CVE-2026-77692 Fix an unauthenticated crash on HTTPS using SIG(0)
CVE-2026-81736 Cached HTTPS/SVCB aliases could exhaust resolver CPU.
CVE-2026-76163 Prevent TKEY queries from terminating named without global options.
CVE-2026-78301 Out-of-zone records in a zone database could be served as authoritative.
CVE-2026-80274 Crash on wildcard answers carrying both NSEC and NSEC3 proofs.
CVE-2026-81563 Following HTTPS/SVCB aliases could leak resolver cache memory.
Complete upstream changelog is available at
https://ftp.isc.org/isc/bind9/9.20.29/doc/arm/html/changelog.html
🧪 Run Testing Details
✅ Formalities
If your PR contains a patch:
git am(e.g., subject line, commit description, etc.)
We must try to upstream patches to reduce maintenance burden.