RHSA-2026:97191HighCVSS 8.8

Red Hat Security Advisory: delve security, bug fix, and enhancement update

Published
November 10, 2026
Last Modified
November 12, 2026

🔗 CVE IDs covered (2)

CVE-2026-33810 →CVE-2026-33811 →

📋 Description

CVE-2026-33810 — crypto/x509: golang: Go crypto/x509: Certificate validation bypass due to incorrect DNS constraint application CVE-2026-33811 — net: golang: Go net package: Denial of Service via long CNAME response in LookupCNAME

🎯 Affected products11

  • Red Hat Enterprise Linux AppStream (v. 10)
  • delve-0:1.26.1-2.el10.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • delve-0:1.26.1-2.el10.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • delve-0:1.26.1-2.el10.src as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • delve-0:1.26.1-2.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • delve-debuginfo-0:1.26.1-2.el10.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • delve-debuginfo-0:1.26.1-2.el10.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • delve-debuginfo-0:1.26.1-2.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • delve-debugsource-0:1.26.1-2.el10.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • delve-debugsource-0:1.26.1-2.el10.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • delve-debugsource-0:1.26.1-2.el10.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10)

✅ Remediation

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Workaround: To mitigate this issue, applications can be configured to use the pure Go DNS resolver instead of the `cgo` DNS resolver. This can be achieved by setting the `GODEBUG` environment variable to `netdns=go`. For example, to run a Go application with this mitigation: `GODEBUG=netdns=go /path/to/your/go/application`. This change may require restarting affected applications or services to take effect. Users should verify that this change does not negatively impact DNS resolution for their specific application environment.

🔗 References (6)