Provider API key disclosure via redirected connection test
Published May 8, 2026 · Updated May 8, 2026
Improper access control in Langfuse 3.68.0 through versions before 3.167.0 allows remote authenticated users to disclose provider API keys. The llmApiKey.testUpdate flow accepts a member-supplied baseURL, decrypts and reuses the existing connection secret, then sends a test request to that destination. Project membership with the member role and an existing LLM connection are required; the attacker-controlled endpoint receives the plaintext credential.
Summary
What happened
Improper access control in Langfuse 3.68.0 through versions before 3.167.0 allows remote authenticated users to disclose provider API keys. The llmApiKey.testUpdate flow accepts a member-supplied baseURL, decrypts and reuses the existing connection secret, then sends a test request to that destination. Project membership with the member role and an existing LLM connection are required; the attacker-controlled endpoint receives the plaintext credential.
The record
- CVE
- CVE-2026-41487
- Published
- May 8, 2026
- Updated
- May 8, 2026
- Vendor
- Langfuse
- Product
- Langfuse
- Classifications
- CWE-284, T1212
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 8, 2026CVE publishedPublication date reported by the CVE source.
- May 8, 2026Record 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=>= 3.68.0, < 3.167.0
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.
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