Disclosed weakness · no CVE recorded

Transcription failures could copy transcripts into logs and errors

LiteLLM · LiteLLM audio transcription proxy

First documented disclosure · Review checkpoint

Summary

A contributor reported seeing full provider responses in error logging after Gemini transcription requests failed. The maintainer correction also covered client errors and monitoring traces.

Severity and exploitation evidence

No CVSS score recorded in this review.

Exploitation not established: Unintended logging was reported; malicious access to a transcript, cross-tenant access and abuse were not established.

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

The error handler preserved provider reply content instead of limiting the error to the status and failure category.

Conditions required

An affected audio-transcription route failed with transcript content in the response. Access to the receiving client, log or monitoring system determined who could see it.

Potential impact

Transcript content could be retained or sent beyond the intended transcription workflow.

Affected versions and configurations

The original observation concerned Gemini. The 1.108 LTS backport also identifies Vertex, other provider adapters and the shared converter; the starting affected release was not specified.

Fix and mitigation status

PR 50137 on main, backported by PR 50325; the fix is listed in 1.108.2 LTS.

Practical next steps

Upgrade and review log and trace destinations, access and retention for prior failing transcription requests. Limit captured error fields to those needed for diagnosis.

Operating lesson

Test how sensitive inputs are handled when a request fails, including what external monitoring systems receive.

Evidence and limits

The contributor reported unintended logging in their organization. That observation does not establish that anyone accessed the logs without authorization. No exact CVE or numerical severity was established.

Sources