CVE-2026-75760

AshAi embedding failures could reveal provider request credentials

ash-project · ash_ai

First documented disclosure · Review checkpoint

Summary

A failed embedding request could expose internal provider state to an API caller.

Severity and exploitation evidence

High · 7.1/10 · CVSS 4.0. Severity source.

Exploitation not established: Malicious exploitation is not established by the reviewed originals. Public demonstrations and catalog absence do not establish exploitation status.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

Vectorize inspected the raw provider error into a user-facing validation error.

Conditions required

A caller can submit vectorized content that triggers an embedding-provider error; API-key exposure depends on the HTTP client retaining its request in the error.

Potential impact

Request URLs and response bodies can leak; retained Authorization headers can disclose the provider API key.

Affected versions and configurations

ash_ai: 0.1.0 through versions before 1.0.0.

Fix and mitigation status

1.0.0.

Practical next steps

Apply the issue-specific correction: 1.0.0.

Operating lesson

Return a bounded generic error and keep raw provider state out of client responses.

Evidence and limits

Earliest reviewed public evidence 2026-08-30; CVE publication 2026-08-31. CVSS 4.0 7.1 is attributed to EEF in the CNA record.

Sources