Quick answers
- Is CVE-2026-75760 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-75760 being exploited in the wild.
- How severe is CVE-2026-75760?
- Informational severity, with a CVSS score of 0, published 31 August 2026.
- Which products and versions are affected?
- Ash-Project Ash Ai 0.1.0 to before 1.0.0.
- Is there a fix for CVE-2026-75760?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-75760 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-75760?
- Check whether you run Ash-Project Ash Ai at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in AshAi.Changes.Vectorize, where failed embedding provider calls generate changeset errors that include the raw error term via string interpolation (An error occurred while generating embeddings: #{inspect(error)}). These error messages are rendered back to API clients by AshJsonApi and AshGraphql without sanitization. The embedding client's error struct can contain the request URL, provider response body, and—depending on the HTTP client implementation—the outbound Authorization header containing the provider API key. Attackers can trigger failures by submitting oversized or malformed vectorized content. The fix logs the raw error server-side and returns a generic, non-revealing error message to clients.
Affected products
- ash-project ash_ai 0.1.0 to before 1.0.0
Timeline
- 2026-08-31: disclosed