CVE-2026-41487: medium-severity vulnerability in langfuse
Langfuse: Improper role-based-access control in Langfuse LLM connection management allowed users of role “member” to retrieve stored LLM provider API keys
Published
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 5.3epss 0.2%
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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
Affected products
langfuse · langfuseRelated CVEs — langfuse
In the same product, most dangerous first.
CVE-2026-24055MEDIUMLangfuse Slack OAuth Installation Endpoint Lacks Authentication, Enabling Arbitrary Project LinkingEPSS 0.4%CVE-2025-64504MEDIUMLangfuse vulnerable to cross‑organization enumeration of member & invitation lists via project membership APIsEPSS 0.3%CVE-2025-65107MEDIUMLangfuse SSO Account Takeover via CSRF or phishing attackEPSS 0.2%
References
https://github.com/langfuse/langfuse/commit/7527bb0d84bc0a3dc24a4b16d22ed2e46e6dddffhttps://github.com/langfuse/langfuse/commit/e12386f9d4368bbfff24a4ad7fd53641091605ffhttps://github.com/langfuse/langfuse/pull/13027https://github.com/langfuse/langfuse/pull/13055https://github.com/langfuse/langfuse/releases/tag/v3.167.0https://github.com/langfuse/langfuse/security/advisories/GHSA-2524-j966-gfgh