Langfuse key disclosure via unredacted proxy errors
Published Mar 20, 2025 · Updated Mar 20, 2025
Information disclosure in Berri AI LiteLLM 1.52.1 and earlier allows remote attackers to read Langfuse API keys via proxy errors. In proxy_server.py, the team-settings error path returns unredacted langfuse_secret and langfuse_public_key values when parsing fails. A reachable proxy configured with Langfuse is required; the exposed keys grant access to the Langfuse project and its stored requests.
Summary
What happened
Information disclosure in Berri AI LiteLLM 1.52.1 and earlier allows remote attackers to read Langfuse API keys via proxy errors. In proxy_server.py, the team-settings error path returns unredacted langfuse_secret and langfuse_public_key values when parsing fails. A reachable proxy configured with Langfuse is required; the exposed keys grant access to the Langfuse project and its stored requests.
The record
- CVE
- CVE-2025-0330
- Published
- Mar 20, 2025
- Updated
- Mar 20, 2025
- Vendor
- Berri AI
- Product
- LiteLLM
- Classifications
- CWE-1230, T1552
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 20, 2025CVE publishedPublication date reported by the CVE source.
- Mar 20, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <=latest
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo