CVE-2026-41487: Langfuse: Improper role-based-access control in Langfuse LLM connection management allowed users of role “member” to retrieve stored LLM provider API keys
Langfuse is an open source large language model engineering platform. From version 3.68.0 to before version 3.167.0, there is a role-based-access control flaw in the LLM connection update flow. An authenticated, low-privileged user of role “member” in a project could request the update of an existing LLM connection to an attacker-controlled baseUrl, causing Langfuse to reuse the stored provider secret and redirect the test request to an attacker-controlled endpoint. This could expose the plaintext provider LLM API key for that connection. The attack is only possible if a user is already part of a project and has “member” scoped access. This issue has been patched in version 3.167.0.
Affected Software
Remediation
Patch Available
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2026-41487?
CVE-2026-41487 has been classified with a critical severity level due to the potential exposure of sensitive API keys.
How do I fix CVE-2026-41487?
To remediate CVE-2026-41487, update Langfuse to version 3.167.0 or later to ensure proper role-based access control is enforced.
Who is affected by CVE-2026-41487?
CVE-2026-41487 affects users of Langfuse versions from 3.68.0 up to but not including 3.167.0.
What type of vulnerability is CVE-2026-41487?
CVE-2026-41487 is classified as an improper role-based access control vulnerability.
What consequences might arise from CVE-2026-41487?
Exploitation of CVE-2026-41487 could allow unauthorized users to access and retrieve stored API keys, exposing sensitive information.