CVE-2026-91991 tornadoweb CVE debrief

Who should care

Defenders responsible for Tornado applications and infrastructure should assess exposure and prioritize verification and remediation to prevent potential security impacts. This includes reviewing and updating cookie handling and validation in Tornado applications, monitoring for potential exploitation attempts, and verifying the affected versions of Tornado.

Why it matters

CVE-2026-91991 is a medium-severity vulnerability in Tornado that allows attackers to inject arbitrary cookie attributes. Defenders responsible for Tornado applications and infrastructure should assess exposure and prioritize verification and remediation to prevent potential security impacts.

• Potential modification of cookie security attributes
• Bypass of validation for cookie attributes
• Possible impact on session management and security

Technical summary

The vulnerability in Tornado before version 6.5.8 allows attackers to inject arbitrary cookie attributes by passing capitalized or legacy keyword arguments to set_cookie. This can be used to bypass validation and modify cookie security attributes, potentially impacting session management and security. The vulnerability is due to an incomplete fix for cookie attribute injection, which permits attackers to embed semicolon-delimited data in capitalized parameters like Domain, Path, or SameSite to bypass validation and modify cookie security attributes.

Defensive priority

Defenders should prioritize verifying and upgrading to Tornado version 6.5.8 or later to mitigate this vulnerability.

Recommended defensive actions

• Verify and upgrade to Tornado version 6.5.8 or later
• Review and update cookie handling and validation in Tornado applications
• Monitor for potential exploitation attempts
• 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 NVD entry provide details on the vulnerability, but the scope of affected versions and potential impact require further verification and defensive review. Defenders should verify the affected versions of Tornado and assess the potential impact on their applications and infrastructure. The CVE record and NVD entry provide a starting point for this verification, but additional research may be necessary to fully understand the vulnerability and its implications.

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.