| CVE-2023-44487 |
high |
7.5 |
10.0 |
|
|
|
3y ago |
Moderate: nginx:1.22 security update |
| CVE-2026-39821 |
critical |
9.6 |
9.6 |
|
|
|
14d ago |
Invoking failure to reject ASCII-only Punycode-encoded labels in golang.org/x/net/idna |
| CVE-2023-45288 |
high |
— |
8.0 |
|
|
|
2y ago |
An attacker may cause an HTTP/2 endpoint to read arbitrary amounts of header data by sending an excessive number of CONTINUATION frames. Maintaining HPACK state requires parsing and processing all HE… |
| CVE-2023-39325 |
high |
— |
8.0 |
|
|
|
3y ago |
Important: go-toolset and golang security and bug fix update |
| CVE-2019-9514 |
high |
— |
8.0 |
|
|
|
4y ago |
RHSA-2019:4273: container-tools:1.0 security update (Important) |
| CVE-2019-9512 |
high |
— |
8.0 |
|
|
|
4y ago |
RHSA-2019:4273: container-tools:1.0 security update (Important) |
| CVE-2021-44716 |
high |
— |
8.0 |
|
|
|
5y ago |
net/http in Go before 1.16.12 and 1.17.x before 1.17.5 allows uncontrolled memory consumption in the header canonicalization cache via HTTP/2 requests. |
| CVE-2026-33814 |
high |
7.5 |
7.5 |
|
|
|
29d ago |
When processing HTTP/2 SETTINGS frames, transport will enter an infinite loop of writing CONTINUATION frames if it receives a SETTINGS_MAX_FRAME_SIZE with a value of 0. |
