RHSA-2026:99038: Important: go-fdo-server security update

Q: Which deployments are most likely exposed to the denial-of-service issues?

Deployments running the go-fdo-server package or its manufacturer, owner, or rendezvous components may be exposed where they process TLS or HTTP/2 traffic. The advisory identifies denial-of-service issues in Go TLS handling and HTTP/2 SETTINGS frame processing.

Q: What attacker access is indicated by the advisory?

The advisory indicates that an attacker must be able to send crafted TLS or HTTP/2 traffic to an affected service. It does not state that authentication, local access, or administrative privileges are required.

Q: Does the update address risks beyond service availability?

Yes. It also fixes a crypto/x509 issue described as permitting man-in-the-middle attacks through untrusted intermediate certificates, in addition to the TLS and HTTP/2 denial-of-service issues.

Q: Which installed packages should be checked when assessing exposure?

Check for redhat/go-fdo-server and the related redhat/go-fdo-server-manufacturer, redhat/go-fdo-server-owner, and redhat/go-fdo-server-rendezvous packages. The debuginfo and debugsource packages are also included in the update, but the advisory describes the affected server functionality through the go-fdo-server components.

Published Nov 11, 2026

This package provides a server-side implementation of the FIDO Device Onboard (FDO) specification, written in Go. FDO is an open standard for the late binding of device credentials, allowing for automated and secure on-boarding of devices when they are first powered on in their final location.Security Fix(es): crypto/tls: golang: crypto/tls: Denial of Service via multiple ECH outer extension references (CVE-2026-97031) net/http: net/http/internal/http2: golang.org/x/net/http2: net/http: Denial of Service via excessive HTTP/2 SETTINGS frames (CVE-2026-78669) crypto/x509: golang: crypto/x509: Man-in-the-middle attacks via untrusted intermediate certificates (CVE-2026-111943) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Affected Software

10 affected componentsFixes available

redhat/go-fdo-server<1.0.1-2.el10_2.6

1.0.1-2.el10_2.6

redhat/go-fdo-server<1.0.1-2.el10_2.6

1.0.1-2.el10_2.6

redhat/go-fdo-server-debuginfo<1.0.1-2.el10_2.6

1.0.1-2.el10_2.6

redhat/go-fdo-server-debugsource<1.0.1-2.el10_2.6

1.0.1-2.el10_2.6

redhat/go-fdo-server-manufacturer<1.0.1-2.el10_2.6

1.0.1-2.el10_2.6

redhat/go-fdo-server-owner<1.0.1-2.el10_2.6

1.0.1-2.el10_2.6

redhat/go-fdo-server-rendezvous<1.0.1-2.el10_2.6

1.0.1-2.el10_2.6

redhat/go-fdo-server<1.0.1-2.el10_2.6.aa

1.0.1-2.el10_2.6.aa

redhat/go-fdo-server-debuginfo<1.0.1-2.el10_2.6.aa

1.0.1-2.el10_2.6.aa

redhat/go-fdo-server-debugsource<1.0.1-2.el10_2.6.aa

1.0.1-2.el10_2.6.aa

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade redhat/go-fdo-server to a version that resolves this vulnerability.
Fixed in 1.0.1-2.el10_2.6
Upgrade
Upgrade redhat/go-fdo-server-debuginfo to a version that resolves this vulnerability.
Fixed in 1.0.1-2.el10_2.6
Upgrade
Upgrade redhat/go-fdo-server-debugsource to a version that resolves this vulnerability.
Fixed in 1.0.1-2.el10_2.6
Upgrade
Upgrade redhat/go-fdo-server-manufacturer to a version that resolves this vulnerability.
Fixed in 1.0.1-2.el10_2.6
Upgrade
Upgrade redhat/go-fdo-server-owner to a version that resolves this vulnerability.
Fixed in 1.0.1-2.el10_2.6
Upgrade
Upgrade redhat/go-fdo-server-rendezvous to a version that resolves this vulnerability.
Fixed in 1.0.1-2.el10_2.6
Upgrade
Upgrade redhat/go-fdo-server to a version that resolves this vulnerability.
Fixed in 1.0.1-2.el10_2.6.aa
Upgrade
Upgrade redhat/go-fdo-server-debuginfo to a version that resolves this vulnerability.
Fixed in 1.0.1-2.el10_2.6.aa
Upgrade
Upgrade redhat/go-fdo-server-debugsource to a version that resolves this vulnerability.
Fixed in 1.0.1-2.el10_2.6.aa

Event History

Nov 11, 2026

Advisory Published

via Red Hat·12:00 AM

Data Sourced

via Red Hat·12:00 AM

RemedyDescriptionAffected Software

Frequently Asked Questions

Which deployments are most likely exposed to the denial-of-service issues?

Deployments running the go-fdo-server package or its manufacturer, owner, or rendezvous components may be exposed where they process TLS or HTTP/2 traffic. The advisory identifies denial-of-service issues in Go TLS handling and HTTP/2 SETTINGS frame processing.

What attacker access is indicated by the advisory?

The advisory indicates that an attacker must be able to send crafted TLS or HTTP/2 traffic to an affected service. It does not state that authentication, local access, or administrative privileges are required.

Does the update address risks beyond service availability?

Yes. It also fixes a crypto/x509 issue described as permitting man-in-the-middle attacks through untrusted intermediate certificates, in addition to the TLS and HTTP/2 denial-of-service issues.

Which installed packages should be checked when assessing exposure?

Check for redhat/go-fdo-server and the related redhat/go-fdo-server-manufacturer, redhat/go-fdo-server-owner, and redhat/go-fdo-server-rendezvous packages. The debuginfo and debugsource packages are also included in the update, but the advisory describes the affected server functionality through the go-fdo-server components.

RHSA-2026:99038: Important: go-fdo-server security update

Affected Software

Remediation

Event History

Frequently Asked Questions

Which deployments are most likely exposed to the denial-of-service issues?

What attacker access is indicated by the advisory?

Does the update address risks beyond service availability?

Which installed packages should be checked when assessing exposure?

Company

Resources

Contact

Frequently Asked Questions

Which deployments are most likely exposed to the denial-of-service issues?

What attacker access is indicated by the advisory?

Does the update address risks beyond service availability?

Which installed packages should be checked when assessing exposure?