CVE-2026-108787 houtini-ai CVE debrief

Who should care

Defenders responsible for the houtini-ai voice-analyser-mcp package, especially those using version 2.1.1 or earlier, should assess their exposure and prioritize verification and potential remediation.

Why it matters

Defenders should care about CVE-2026-108787 because it allows for server-side request forgery in the houtini-ai voice-analyser-mcp package, potentially leading to unauthorized requests, data leakage, or exposure of internal systems. Those responsible for this package should verify its presence in their inventory, assess exposure, and prioritize remediation or compensating controls.

• Potential for unauthorized requests to internal resources
• Possible data leakage or exposure of internal systems
• Need for verification of package version and exposure in inventory
• Potential impact on data integrity and confidentiality

Technical summary

The vulnerability is located in the fetch function of the src/utils/crawler.ts file within the collect_corpus component of the houtini-ai voice-analyser-mcp package. By manipulating the sitemap_url argument, an attacker can exploit this vulnerability remotely to perform server-side request forgery attacks. This could lead to unauthorized requests to internal resources, potential data leakage, or exposure of internal systems. Defenders should prioritize verifying the presence of this vulnerability in their inventory, especially if using the affected package version, and assess exposure based on their specific deployment context. The exploit has been made public, and remote exploitation is possible, emphasizing  

Defensive priority

Defenders should prioritize verifying the presence of this vulnerability in their inventory, especially if using the affected package version, and assess exposure based on their specific deployment context.

Recommended defensive actions

• Verify the presence of the houtini-ai voice-analyser-mcp package in your inventory, especially version 2.1.1 or earlier.
• Assess exposure based on your specific deployment context and the collect_corpus feature usage.
• Consider implementing compensating controls or monitoring for potential SSRF attacks.
• Review and apply vendor remediation if available.
• Perform vulnerability scanning to identify potential entry points for SSRF attacks.
• Implement additional logging and monitoring to detect suspicious activity related to the collect_corpus feature.
• Review and update incident response plans to include procedures for handling SSRF attacks.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description, CVSS score, and affected component. However, the vendor's response to disclosure is unknown, and no additional information on exploitation or impact is available.

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.