CVE-2026-40035: CWE-489 Active Debug Code in obsidianforensics unfurl
Unfurl versions through 2025. 08 contain a vulnerability where the Flask debug mode is enabled by default due to improper input validation in configuration parsing. This occurs because the debug configuration value is read as a string and passed directly to app. run(), causing any non-empty string to be treated as true. This allows attackers to access the Werkzeug debugger, potentially disclosing sensitive information or enabling remote code execution.
AI Analysis
Technical Summary
CVE-2026-40035 is a critical vulnerability in the obsidianforensics product 'unfurl' up to version 2025.08. The flaw arises from improper input validation in the config parsing logic that enables Flask debug mode by default. Specifically, the debug configuration value is read as a string and passed directly to Flask's app.run() method. Since any non-empty string evaluates as truthy in Python, this results in debug mode activation unintentionally. This exposes the Werkzeug debugger interface, which can be exploited by attackers to disclose sensitive application information or execute arbitrary code remotely. The CVSS 4.0 score is 9.3, reflecting the high impact and ease of exploitation without authentication or user interaction.
Potential Impact
Successful exploitation allows unauthenticated attackers to access the Werkzeug debugger interface, leading to disclosure of sensitive information and potential remote code execution on the affected system. This poses a critical risk to confidentiality and integrity of the application and underlying host.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, users should avoid running unfurl versions through 2025.08 in production environments or disable Flask debug mode manually by ensuring the debug configuration value is set to a boolean false or omitted. Monitor vendor channels for an official fix or update.
CVE-2026-40035: CWE-489 Active Debug Code in obsidianforensics unfurl
Description
Unfurl versions through 2025. 08 contain a vulnerability where the Flask debug mode is enabled by default due to improper input validation in configuration parsing. This occurs because the debug configuration value is read as a string and passed directly to app. run(), causing any non-empty string to be treated as true. This allows attackers to access the Werkzeug debugger, potentially disclosing sensitive information or enabling remote code execution.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-40035 is a critical vulnerability in the obsidianforensics product 'unfurl' up to version 2025.08. The flaw arises from improper input validation in the config parsing logic that enables Flask debug mode by default. Specifically, the debug configuration value is read as a string and passed directly to Flask's app.run() method. Since any non-empty string evaluates as truthy in Python, this results in debug mode activation unintentionally. This exposes the Werkzeug debugger interface, which can be exploited by attackers to disclose sensitive application information or execute arbitrary code remotely. The CVSS 4.0 score is 9.3, reflecting the high impact and ease of exploitation without authentication or user interaction.
Potential Impact
Successful exploitation allows unauthenticated attackers to access the Werkzeug debugger interface, leading to disclosure of sensitive information and potential remote code execution on the affected system. This poses a critical risk to confidentiality and integrity of the application and underlying host.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, users should avoid running unfurl versions through 2025.08 in production environments or disable Flask debug mode manually by ensuring the debug configuration value is set to a boolean false or omitted. Monitor vendor channels for an official fix or update.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-04-08T13:36:58.277Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69d6d13b1cc7ad14dab766cb
Added to database: 4/8/2026, 10:05:47 PM
Last enriched: 4/8/2026, 10:20:48 PM
Last updated: 4/9/2026, 2:34:14 AM
Views: 7
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.