CVE-2026-75760 ash-project CVE debrief

Who should care

Organizations and developers using ash_ai versions between 0.1.0 and before 1.0.0 should be aware of this vulnerability and take steps to mitigate it. They should confirm whether affected product deployments exist in managed environments and assign an owner for follow-up. Affected operators, platforms, vulnerability-management, and security teams should prioritize patching to prevent potential sensitive information disclosure. They should also conduct inventory checks to identify and update vulnerable ash_ai installations, monitor for suspicious activity related to oversized or malformed vectorized content, and consider exception tracking for unusual error patterns.

Technical summary

The ash_ai product is vulnerable to Generation of Error Message Containing Sensitive Information. When the embedding provider call fails, the error message could potentially disclose sensitive information such as the request URL, provider response body, and outbound Authorization header with the provider API key. This issue is reachable via oversized or malformed vectorized content. The fix involves logging the raw error and returning a generic message.

Defensive priority

Organizations using ash_ai should prioritize patching to prevent potential sensitive information disclosure.

Recommended defensive actions

• Review and apply the patch for ash_ai version 1.0.0 or later.
• Implement compensating controls to monitor and limit sensitive information disclosure.
• Conduct inventory checks to identify and update vulnerable ash_ai installations.
• Monitor for suspicious activity related to oversized or malformed vectorized content.
• Consider exception tracking for unusual error patterns.

Evidence notes

The CVE-2026-75760 issue arises from the ash_ai product's handling of embedding provider errors. When the embedding provider call fails, the change adds a changeset error whose message inspects the raw error term. This could potentially disclose sensitive information such as the request URL, provider response body, and outbound Authorization header with the provider API key. The issue is reachable via oversized or malformed vectorized content. The fix involves logging the raw error and returning a generic message.

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.