Bug 2479771 (CVE-2026-5946)

Summary:	CVE-2026-5946 bind: BIND: Denial of Service via specially crafted DNS messages
Product:	[Other] Security Response	Reporter:	OSIDB Bzimport <bzimport>
Component:	vulnerability	Assignee:	Product Security <prodsec-ir-bot>
Status:	NEW ---	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	unspecified	CC:	akhatavk, aos-team-art-private, asdas, dpaolell, jdelft, jupierce, lgarciaa, mbiarnes, ppalepu, ppostler, prdhamdh, rhel-process-autobot, security-response-team, sghai, sidsharm, suppawar, vlaad, watson-tool-maintainers
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:	A flaw was found in the bind component, specifically within the `named` daemon. This vulnerability allows a remote attacker to send specially crafted Domain Name System (DNS) messages. These messages, which use unusual classes or meta-classes, can trigger assertion failures in the `named` daemon when processed. Successful exploitation leads to an application level Denial of Service (DoS), making the DNS service unavailable.	Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	2480121, 2484321, 2484322
Bug Blocks:

Description OSIDB Bzimport 2026-05-19 09:59:09 UTC

Multiple flaws have been identified in named related to the handling of DNS messages whose CLASS is not Internet (IN) — for example, CHAOS or HESIOD, or DNS messages that specify meta-classes (ANY or NONE) in the question section. Specially crafted requests reaching the affected code paths — recursion, dynamic updates (UPDATE), zone change notifications (NOTIFY), or processing of IN-specific record types in non-IN data — can cause assertion failures in named.

Comment 4 errata-xmlrpc 2026-06-04 15:11:12 UTC

This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:23360 https://access.redhat.com/errata/RHSA-2026:23360

Comment 5 errata-xmlrpc 2026-06-08 02:53:51 UTC

This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:24339 https://access.redhat.com/errata/RHSA-2026:24339

Comment 6 errata-xmlrpc 2026-06-08 02:55:09 UTC

This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:24338 https://access.redhat.com/errata/RHSA-2026:24338

Comment 7 errata-xmlrpc 2026-06-08 09:36:45 UTC

This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:24367 https://access.redhat.com/errata/RHSA-2026:24367

Comment 8 errata-xmlrpc 2026-06-08 10:48:11 UTC

This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:24368 https://access.redhat.com/errata/RHSA-2026:24368

Comment 10 errata-xmlrpc 2026-08-17 03:44:32 UTC

This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.6 Extended Update Support

Via RHSA-2026:55441 https://access.redhat.com/errata/RHSA-2026:55441

Comment 11 errata-xmlrpc 2026-08-19 23:36:52 UTC

This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.4 Update Services for SAP Solutions

Via RHSA-2026:57189 https://access.redhat.com/errata/RHSA-2026:57189

Comment 12 errata-xmlrpc 2026-08-26 19:44:59 UTC

This issue has been addressed in the following products:

  Red Hat Enterprise Linux 7 Extended Lifecycle Support

Via RHSA-2026:60383 https://access.redhat.com/errata/RHSA-2026:60383