Skip to content
Threat Brief

← All advisories

CVE-2026-75760

High 7.1No known exploitationFix available

AshAi vectorize change leaks raw embedding-provider errors, including credentials, in a user-facing error

Record last updated

CVSS score

7.1

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.4%

Higher than 30% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

Generation of Error Message Containing Sensitive Information vulnerability in ash-project ash_ai discloses provider request state and credentials in a user-facing validation error. In AshAi.Changes.Vectorize, when the embedding provider call fails the change added a changeset error whose message inspected the raw error term (An error occurred while generating embeddings: #{inspect(error)}). A plain-string add_error produces an Ash.Error.Changes.InvalidChanges in the :invalid class, which AshJsonApi and AshGraphql render back to the caller. The embedding client's error term is not sanitized, so it can carry the request URL, the provider response body, and, for HTTP clients that keep the request in the error struct, the outbound Authorization header with the provider API key. Failures are attacker-reachable via oversized or malformed vectorized content. The fix logs the raw error and returns a generic message. This issue affects ash_ai: from 0.1.0 before 1.0.0.

Weakness: CWE-209

Patching and mitigation

Patch status
Fix available (source: CVE record (EEF))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
ash-projectash_aifrom 0.1.0 before 1.0.01.0.0CVE Program
ash-projectash_aifrom 5334edc73a007f0629661761d6a75796f2fc0004 before 088a2562e16d65f36cec178070de683636479f58088a2562e16d65f36cec178070de683636479f58CVE Program

Timeline

  1. Disclosure

    CVE record published by EEF

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (EEF)

    Source: CVE record (EEF) (opens in a new tab)

Vendor guidance and references