CVE-2026-40035: Unfurl Flask Debug Mode RCE Vulnerability

CVE-2026-40035 Overview

CVE-2026-40035 is an improper input validation vulnerability in Unfurl through version 2025.08 that affects the configuration parsing mechanism. The vulnerability allows Flask debug mode to be enabled by default due to the debug configuration value being read as a string and passed directly to app.run(). Since any non-empty string evaluates as truthy in this context, attackers can access the Werkzeug debugger, leading to sensitive information disclosure or remote code execution.

Critical Impact

This vulnerability enables unauthorized access to the Werkzeug debugger, potentially allowing attackers to disclose sensitive information or achieve remote code execution on affected systems.

Affected Products

• Unfurl through version 2025.08

Discovery Timeline

• April 8, 2026 - CVE CVE-2026-40035 published to NVD
• April 9, 2026 - Last updated in NVD database

Technical Details for CVE-2026-40035

Vulnerability Analysis

This vulnerability falls under CWE-489 (Active Debug Code), where debugging functionality is inadvertently left enabled in production environments. The root issue lies in how Unfurl processes configuration values for Flask's debug mode setting. When the configuration parser reads the debug setting, it treats the value as a string rather than converting it to a proper boolean.

In Python and Flask, the app.run(debug=value) function interprets any non-empty string as True. This means configuration values like "false", "no", or "0" (as strings) will still enable debug mode because they are non-empty strings that evaluate as truthy. Only an empty string or an actual boolean False would disable debug mode.

When debug mode is enabled, Flask exposes the Werkzeug interactive debugger on error pages. This debugger provides a Python console in the browser that runs with the application's privileges, allowing arbitrary code execution. Additionally, the debugger interface displays stack traces and application internals, exposing sensitive configuration data, database credentials, API keys, and other secrets.

Root Cause

The root cause is improper input validation in the configuration parsing logic. The application fails to properly convert the string configuration value to a boolean before passing it to Flask's app.run() method. String values like "False" or "false" are not properly interpreted as boolean False, causing the debug parameter to evaluate as truthy and enabling the Werkzeug debugger.

Attack Vector

This vulnerability is exploitable over the network without authentication. An attacker can trigger an application error to access the Werkzeug debugger interface. From there, they can execute arbitrary Python code on the server, read sensitive files, access environment variables containing secrets, or establish persistent access to the system.

The attack does not require user interaction and can be exploited with low complexity once an error condition is triggered. The impact includes high confidentiality and integrity compromise, as attackers gain the ability to read sensitive data and execute arbitrary commands on the vulnerable system.

Detection Methods for CVE-2026-40035

Indicators of Compromise

• HTTP responses containing Werkzeug debugger HTML content or interactive console elements
• Unexpected access to /__debugger__ or similar Flask debug endpoints
• Application error pages exposing full Python stack traces and local variables
• Log entries showing debugger PIN access attempts or console code execution

Detection Strategies

• Monitor web server logs for requests to Flask debug endpoints such as /__debugger__
• Implement web application firewall rules to detect and block Werkzeug debugger response patterns
• Deploy endpoint detection to identify unauthorized Python code execution originating from web application processes
• Review application configurations for improper boolean handling in debug settings

Monitoring Recommendations

• Enable comprehensive logging for Flask applications and monitor for debug-related activity
• Set up alerts for unusual application behavior such as unexpected subprocess spawning from web workers
• Monitor network traffic for patterns consistent with interactive debugger sessions
• Conduct periodic configuration audits to ensure debug mode is properly disabled in production

How to Mitigate CVE-2026-40035

Immediate Actions Required

• Upgrade Unfurl to a patched version that properly handles boolean configuration values
• Review Flask application configurations and ensure debug mode is explicitly set to boolean False
• Implement network-level controls to restrict access to application endpoints from untrusted sources
• Audit deployed instances for signs of prior exploitation or unauthorized debugger access

Patch Information

Review the GitHub Security Advisory for official patch information and upgrade instructions. The Vulncheck Advisory on Debugger Exposure provides additional technical context on this vulnerability class.

Workarounds

• Explicitly set the Flask debug parameter to boolean False in code rather than relying on configuration file parsing
• Deploy the application behind a reverse proxy that strips or blocks access to debug endpoints
• Use environment variable type conversion libraries that properly handle boolean conversions
• Implement application-level middleware to disable debug features regardless of configuration

# Configuration example - ensure debug is disabled in production
export FLASK_DEBUG=0
export FLASK_ENV=production

# Verify debug mode is disabled before deployment
python -c "from unfurl import app; print('Debug mode:', app.debug)"