Red Hat BIND Update Fixes Five RHEL 10 Flaws
Tech GuruQuick Answer
Red Hat published RHSA-2026:75577 for RHEL 10 BIND DNS server and utility packages. Match entitled systems to the advisory scope, install bind 9.18.33-15.el10_2.12, validate dependent operations, and retain change evidence.
Validate BIND Scope And Apply The Red Hat Fix
What to do now: Inventory RHEL 10 BIND DNS server and utility packages, confirm the exact entitled branch and installed build, apply the advisory-listed content, validate representative services, and document exceptions.
Last verified: 2026-10-05 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | RHEL 10 BIND DNS server and utility packages |
|---|---|
| Advisory | RHSA-2026:75577 |
| CVEs | CVE-2026-19666, CVE-2026-19667, CVE-2026-80274, CVE-2026-81563, CVE-2026-81736 |
| Authoritative release date | 2026-10-05 06:19:54 UTC |
| Authority revision date | 2026-10-05 10:49:06 UTC |
| Affected versions | The supported RHEL 10 BIND DNS server and utility packages builds identified as affected in the advisory product-status relationships. |
| Fixed version | bind 9.18.33-15.el10_2.12 |
| CVSS base score | 7.5 (CVSS v3.1) |
| CVSS severity | High |
| Exploitation status | Not stated by the authority; no exploitation claim is inferred. |
What Changed
Red Hat published supported BIND replacement content for the advisory-listed CVEs and product branches.
What To Validate Now
- Inventory. Locate RHEL 10 BIND DNS server and utility packages; record the installed build, repository and entitlement, owner, exposure, dependencies, and maintenance group.
- Establish applicability. Compare every system with the product and package relationships in RHSA-2026:75577. Do not infer applicability from the component name or CVSS rating alone.
- Remediate. Install bind 9.18.33-15.el10_2.12 from the supported Red Hat channel for the exact branch.
- Validate. Confirm the installed package or image digest, exercise representative BIND functions and recovery paths, monitor for regressions, and record the result.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Stage authoritative and recursive DNS changes separately where possible; validate zones, DNSSEC, forwarding, recursion, and failover. Preserve pre-change versions, logs, installation output, validation evidence, and any rollback decision.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
