rpm package
almalinux/go-fdo-server-owner
pkg:rpm/almalinux/go-fdo-server-owner
Vulnerabilities (19)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2026-97031 | Hig | 7.5 | < 1.0.1-6.el10_3.9 | 1.0.1-6.el10_3.9 | Oct 8, 2026 | Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references. We now reject these as malformed and curb the memory ampli | |
| CVE-2026-78669 | Hig | 7.5 | < 1.0.1-6.el10_3.9 | 1.0.1-6.el10_3.9 | Oct 8, 2026 | A malicious HTTP/2 peer can cause excessive CPU consumption in the client or server by opening a large number of streams and then sending many small SETTINGS frames containing SETTINGS_INITIAL_WINDOW_SIZE values. | |
| CVE-2026-56862 | Hig | 7.5 | < 1.0.1-2.el10_2.4 | 1.0.1-2.el10_2.4 | Aug 13, 2026 | Handshake messages, such as KeyUpdate, are always considered as state-advancing, regardless of whether a handshake has been completed or not. As a result, a malicious client can keep sending KeyUpdate messages to force the server to keep performing key derivation operations indef | |
| CVE-2026-56860 | Med | 5.9 | < 1.0.1-2.el10_2.4 | 1.0.1-2.el10_2.4 | Aug 13, 2026 | Previously, resolving relative paths containing parent directory ('..') segments performed string conversions and buffer rewrites on each step, resulting in quadratic time complexity and high memory allocation overhead. Now, path resolution operates on a byte buffer using index-b | |
| CVE-2026-56859 | Hig | 7.5 | < 1.0.1-6.el10_3 | 1.0.1-6.el10_3 | Aug 13, 2026 | Previously, DecodeElement would reset the depth counter causing it to never fire; this could lead to stack exhaustion. | |
| CVE-2026-56853 | Hig | 7.5 | < 1.0.1-2.el10_2.4 | 1.0.1-2.el10_2.4 | Aug 13, 2026 | When a server is configured to support unencrypted HTTP/2, it reads a few bytes from each new connection to see if they contain the HTTP/2 client preface. ReadHeaderTimeout is unexpectedly not being applied when doing this. | |
| CVE-2026-33818 | Hig | 7.5 | < 1.0.1-2.el10_2.4 | 1.0.1-2.el10_2.4 | Aug 13, 2026 | Enforce a recursion limit in Unmarshal to prevent stack exhaustion when parsing deeply-nested, recursive structures. | |
| CVE-2026-27145 | Med | 6.5 | < 1.0.1-2.el10_2.3 | 1.0.1-2.el10_2.3 | Jun 2, 2026 | (*x509.Certificate).VerifyHostname previously called matchHostnames in a loop over all DNS Subject Alternative Name (SAN) entries. This caused strings.Split(host, ".") to execute repeatedly on the same input hostname. With a large DNS SAN list, verification costs scaled quadratic | |
| CVE-2026-39821 | Cri | 9.6 | < 1.0.1-2.el10_2.3 | 1.0.1-2.el10_2.3 | May 22, 2026 | The ToASCII and ToUnicode functions incorrectly accept Punycode-encoded labels that decode to an ASCII-only label. For example, ToUnicode("xn--example-.com") incorrectly returns the name "example.com" rather than an error. This behavior can lead to privilege escalation in program | |
| CVE-2026-33811 | Hig | 7.5 | < 1.0.1-6.el10_3 | 1.0.1-6.el10_3 | May 7, 2026 | When using LookupCNAME with the cgo DNS resolver, a very long CNAME response can trigger a double-free of C memory and a crash. | |
| CVE-2026-33810 | Hig | 8.2 | < 1.0.1-2.el10_2.4 | 1.0.1-2.el10_2.4 | Apr 8, 2026 | When verifying a certificate chain containing excluded DNS constraints, these constraints are not correctly applied to wildcard DNS SANs which use a different case than the constraint. This only affects validation of otherwise trusted certificate chains, issued by a root CA in th | |
| CVE-2026-32283 | Hig | 7.5 | < 1.0.1-1.el10_2 | 1.0.1-1.el10_2 | Apr 8, 2026 | If one side of the TLS connection sends multiple key update messages post-handshake in a single record, the connection can deadlock, causing uncontrolled consumption of resources. This can lead to a denial of service. This only affects TLS 1.3. | |
| CVE-2026-32282 | Med | 6.4 | < 1.0.1-2.el10_2 | 1.0.1-2.el10_2 | Apr 8, 2026 | On Linux, if the target of Root.Chmod is replaced with a symlink while the chmod operation is in progress, Chmod can operate on the target of the symlink, even when the target lies outside the root. The Linux fchmodat syscall silently ignores the AT_SYMLINK_NOFOLLOW flag, which R | |
| CVE-2026-32281 | Hig | 7.5 | < 1.0.1-2.el10_2 | 1.0.1-2.el10_2 | Apr 8, 2026 | Validating certificate chains which use policies is unexpectedly inefficient when certificates in the chain contain a very large number of policy mappings, possibly causing denial of service. This only affects validation of otherwise trusted certificate chains, issued by a root C | |
| CVE-2026-32280 | Hig | 7.5 | < 1.0.1-2.el10_2 | 1.0.1-2.el10_2 | Apr 8, 2026 | During chain building, the amount of work that is done is not correctly limited when a large number of intermediate certificates are passed in VerifyOptions.Intermediates, which can lead to a denial of service. This affects both direct users of crypto/x509 and users of crypto/tls | |
| CVE-2026-33816 | Cri | 9.8 | < 1.0.1-1.el10_2 | 1.0.1-1.el10_2 | Apr 7, 2026 | Memory-safety vulnerability in github.com/jackc/pgx/v5. | |
| CVE-2026-27137 | Hig | 7.5 | < 1.0.1-6.el10_3 | 1.0.1-6.el10_3 | Mar 6, 2026 | When verifying a certificate chain which contains a certificate containing multiple email address constraints which share common local portions but different domain portions, these constraints will not be properly applied, and only the last constraint will be considered. | |
| CVE-2026-25679 | Hig | 7.5 | < 1.0.1-6.el10_3 | 1.0.1-6.el10_3 | Mar 6, 2026 | url.Parse insufficiently validated the host/authority component and accepted some invalid URLs. | |
| CVE-2025-68121 | Cri | 10.0 | < 1.0.1-2.el10_2 | 1.0.1-2.el10_2 | Feb 5, 2026 | During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between the initial handshake and the resumed handshake, the resumed handshake may succeed when it should have failed. This may happen when a user calls Config.Clone and |
- affected < 1.0.1-6.el10_3.9fixed 1.0.1-6.el10_3.9
Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references. We now reject these as malformed and curb the memory ampli
- affected < 1.0.1-6.el10_3.9fixed 1.0.1-6.el10_3.9
A malicious HTTP/2 peer can cause excessive CPU consumption in the client or server by opening a large number of streams and then sending many small SETTINGS frames containing SETTINGS_INITIAL_WINDOW_SIZE values.
- affected < 1.0.1-2.el10_2.4fixed 1.0.1-2.el10_2.4
Handshake messages, such as KeyUpdate, are always considered as state-advancing, regardless of whether a handshake has been completed or not. As a result, a malicious client can keep sending KeyUpdate messages to force the server to keep performing key derivation operations indef
- affected < 1.0.1-2.el10_2.4fixed 1.0.1-2.el10_2.4
Previously, resolving relative paths containing parent directory ('..') segments performed string conversions and buffer rewrites on each step, resulting in quadratic time complexity and high memory allocation overhead. Now, path resolution operates on a byte buffer using index-b
- affected < 1.0.1-6.el10_3fixed 1.0.1-6.el10_3
Previously, DecodeElement would reset the depth counter causing it to never fire; this could lead to stack exhaustion.
- affected < 1.0.1-2.el10_2.4fixed 1.0.1-2.el10_2.4
When a server is configured to support unencrypted HTTP/2, it reads a few bytes from each new connection to see if they contain the HTTP/2 client preface. ReadHeaderTimeout is unexpectedly not being applied when doing this.
- affected < 1.0.1-2.el10_2.4fixed 1.0.1-2.el10_2.4
Enforce a recursion limit in Unmarshal to prevent stack exhaustion when parsing deeply-nested, recursive structures.
- affected < 1.0.1-2.el10_2.3fixed 1.0.1-2.el10_2.3
(*x509.Certificate).VerifyHostname previously called matchHostnames in a loop over all DNS Subject Alternative Name (SAN) entries. This caused strings.Split(host, ".") to execute repeatedly on the same input hostname. With a large DNS SAN list, verification costs scaled quadratic
- affected < 1.0.1-2.el10_2.3fixed 1.0.1-2.el10_2.3
The ToASCII and ToUnicode functions incorrectly accept Punycode-encoded labels that decode to an ASCII-only label. For example, ToUnicode("xn--example-.com") incorrectly returns the name "example.com" rather than an error. This behavior can lead to privilege escalation in program
- affected < 1.0.1-6.el10_3fixed 1.0.1-6.el10_3
When using LookupCNAME with the cgo DNS resolver, a very long CNAME response can trigger a double-free of C memory and a crash.
- affected < 1.0.1-2.el10_2.4fixed 1.0.1-2.el10_2.4
When verifying a certificate chain containing excluded DNS constraints, these constraints are not correctly applied to wildcard DNS SANs which use a different case than the constraint. This only affects validation of otherwise trusted certificate chains, issued by a root CA in th
- affected < 1.0.1-1.el10_2fixed 1.0.1-1.el10_2
If one side of the TLS connection sends multiple key update messages post-handshake in a single record, the connection can deadlock, causing uncontrolled consumption of resources. This can lead to a denial of service. This only affects TLS 1.3.
- affected < 1.0.1-2.el10_2fixed 1.0.1-2.el10_2
On Linux, if the target of Root.Chmod is replaced with a symlink while the chmod operation is in progress, Chmod can operate on the target of the symlink, even when the target lies outside the root. The Linux fchmodat syscall silently ignores the AT_SYMLINK_NOFOLLOW flag, which R
- affected < 1.0.1-2.el10_2fixed 1.0.1-2.el10_2
Validating certificate chains which use policies is unexpectedly inefficient when certificates in the chain contain a very large number of policy mappings, possibly causing denial of service. This only affects validation of otherwise trusted certificate chains, issued by a root C
- affected < 1.0.1-2.el10_2fixed 1.0.1-2.el10_2
During chain building, the amount of work that is done is not correctly limited when a large number of intermediate certificates are passed in VerifyOptions.Intermediates, which can lead to a denial of service. This affects both direct users of crypto/x509 and users of crypto/tls
- affected < 1.0.1-1.el10_2fixed 1.0.1-1.el10_2
Memory-safety vulnerability in github.com/jackc/pgx/v5.
- affected < 1.0.1-6.el10_3fixed 1.0.1-6.el10_3
When verifying a certificate chain which contains a certificate containing multiple email address constraints which share common local portions but different domain portions, these constraints will not be properly applied, and only the last constraint will be considered.
- affected < 1.0.1-6.el10_3fixed 1.0.1-6.el10_3
url.Parse insufficiently validated the host/authority component and accepted some invalid URLs.
- affected < 1.0.1-2.el10_2fixed 1.0.1-2.el10_2
During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between the initial handshake and the resumed handshake, the resumed handshake may succeed when it should have failed. This may happen when a user calls Config.Clone and