8 matches found
CVE-2026-115482
In lsquic before 4.9.0, the HTTP/3 implementation can use an excessive amount of memory because the number of buffered header sets is not limited, as demonstrated by a QPACK amplification attack. This is related to headeroutdynamicentry and esmaxheaderlistsize...
CVE-2026-115482
In lsquic before 4.9.0, the HTTP/3 implementation can use an excessive amount of memory because the number of buffered header sets is not limited, as demonstrated by a QPACK amplification attack. This is related to headeroutdynamicentry and esmaxheaderlistsize...
CVE-2026-115482
In lsquic before 4.9.0, the HTTP/3 implementation can use an excessive amount of memory because the number of buffered header sets is not limited, as demonstrated by a QPACK amplification attack. This is related to headeroutdynamicentry and esmaxheaderlistsize...
CVE-2026-115482
In lsquic before 4.9.0, the HTTP/3 implementation can use an excessive amount of memory because the number of buffered header sets is not limited, as demonstrated by a QPACK amplification attack. This is related to headeroutdynamicentry and esmaxheaderlistsize...
CVE-2026-115482
The lsquic library (versions before 4.9.0 ) is vulnerable to a memory exhaustion issue within its HTTP/3 implementation. The root cause is an unlimited number of buffered header sets , which can be exploited via a QPACK amplification attack . This vulnerability is specifically related to header_o...
EUVD-2026-108211
In lsquic before 4.9.0, the HTTP/3 implementation can use an excessive amount of memory because the number of buffered header sets is not limited, as demonstrated by a QPACK amplification attack. This is related to headeroutdynamicentry and esmaxheaderlistsize...
PT-2026-121409
In lsquic before 4.9.0, the HTTP/3 implementation can use an excessive amount of memory because the number of buffered header sets is not limited, as demonstrated by a QPACK amplification attack. This is related to header out dynamic entry and es max header list size...
LiteSpeed Tech “Resource Management Error” vulnerability
LiteSpeed Tech versions prior to 4.9.0 contain a resource management error vulnerability. This vulnerability arises because the HTTP/3 implementation fails to limit the number of buffer header sets, potentially leading to excessive memory consumption and susceptibility to QPACK amplification...