CVE-2026-115482 litespeedtech CVE debrief

Who should care

System administrators and security teams responsible for HTTP/3 server infrastructure should assess exposure and prioritize patching or upgrading to version 4.9.0 or later to prevent potential memory exhaustion attacks.

Why it matters

CVE-2026-115482 is a high-severity vulnerability in the lsquic library used for HTTP/3 implementation. It allows for excessive memory usage due to an unlimited number of buffered header sets, making it susceptible to QPACK amplification attacks. Defenders should prioritize patching or upgrading to version 4.9.0 or later to prevent potential memory exhaustion attacks. System administrators and security teams responsible for HTTP/3 server infrastructure should assess exposure and take action.

• Potential memory exhaustion due to QPACK amplification attacks
• Need to verify and patch vulnerable lsquic versions
• Possible performance impact due to excessive memory usage

Technical summary

The lsquic library, used for HTTP/3 implementation, has a vulnerability that allows for excessive memory usage due to an unlimited number of buffered header sets. This makes it susceptible to QPACK amplification attacks. The issue was fixed in version 4.9.0. The vulnerability has a CVSS score of 7.5 and is considered HIGH severity. The CVE record and source item provide details on the vulnerability, including its description, CVSS score, and affected versions. Defenders should prioritize patching or upgrading to version 4.9.0 or later to prevent potential memory exhaustion attacks.

Defensive priority

Defenders should prioritize patching or upgrading to version 4.9.0 or later to prevent potential memory exhaustion attacks. System administrators and security teams responsible for HTTP/3 server infrastructure should assess exposure and take action.

Recommended defensive actions

• Patch or upgrade lsquic to version 4.9.0 or later
• Assess exposure and prioritize patching for HTTP/3 server infrastructure
• Monitor for potential QPACK amplification attacks
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details on the vulnerability, including its description, CVSS score, and affected versions. However, the corpus does not provide information on actual exploitation or victim impact.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.