CVE-2026-108264 wizarrrr CVE debrief

Who should care

Administrators and users of Wizarr, particularly those who have access to the wizard step rendering functionality, should assess their exposure and take necessary actions to mitigate the vulnerability.

Why it matters

This vulnerability is critical, with a CVSS score of 9.1, and requires immediate attention from administrators and users of Wizarr. The vulnerability allows an authenticated user to execute arbitrary Python code, which could lead to a compromise of the system and sensitive information disclosure.

• Potential Remote Code Execution (RCE) leading to arbitrary Python code execution
• Disclosure of sensitive information, including the Flask SECRET_KEY
• Access to connected service credentials and the database
• Production of stored cross-site scripting

Technical summary

Wizarr, an advanced user invitation and management system, is vulnerable to authenticated Server-Side Template Injection (SSTI) in its wizard step rendering functionality. This could lead to Remote Code Execution (RCE) and allow an attacker to execute arbitrary Python code, disclose the Flask SECRET_KEY, access connected service credentials and the database, and produce stored cross-site scripting.

Defensive priority

High

Recommended defensive actions

• Upgrade to version 2026.9.1 or later
• Review and restrict access to the wizard step rendering functionality
• Monitor for suspicious activity related to the vulnerability
• 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 CVSS score of 9.1 and the affected versions of Wizarr. The vulnerability was reported through a responsible disclosure process and was fixed in version 2026.9.1. The evidence is based on the official CVE Program record and the source item providing details on the vulnerability.

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.