A too-strict assertion check could be triggered when responses in BIND 9.16.19 and 9.17.16 require UDP fragmentation if RRL is in use
At a glance
Severity
HIGH 7.5
EPSS
EPSS 3.59 % · percentile 89 (2026-10-27)
State
PUBLISHED
Published
Updated
Assigner
isc
NVD status
Modified
Description
In BIND 9.16.19, 9.17.16. Also, version 9.16.19-S1 of BIND Supported Preview Edition When a vulnerable version of named receives a query under the circumstances described above, the named process will terminate due to a failed assertion check. The vulnerability affects only BIND 9 releases 9.16.19, 9.17.16, and release 9.16.19-S1 of the BIND Supported Preview Edition.