CVE-2025-64504: langfuse · Exposure of Sensitive Information Through Data Queries
Affects langfuseSource GCVE Database
Not known to be exploited · CVSS 5.0 Medium : upgrade to 3.124.1 or 2.95.11 when convenient.
Data as of 12 Nov 2026, 20:15 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 5.0 |
|---|
- Patch
- Available – fixed in 3.124.1, 2.95.11
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 12 Nov 2026.
What to do
Upgrade langfuse to 3.124.1 or 2.95.11.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| langfuse langfuse | Affected
| Fixed in
|
AI-suggested
Upgrading Langfuse to version 2.95.11 or later in the 2.x series, or 3.124.1 or later in the 3.x series, fully mitigates this vulnerability. Langfuse Cloud environments were patched by November 1, 2025. There are no known workarounds. Deployments using Enterprise SSO reduce the attack surface but do not fully mitigate the issue. Users should apply the official fixes promptly to prevent unauthorized enumeration of user information.
Description
CVE-2025-64504 is a vulnerability in Langfuse versions from 2.70.0 up to but not including 2.95.11 and from 3.0.0 up to but not including 3.124.1. It allows an authenticated user to enumerate names and email addresses of users in other organizations on the same Langfuse instance by manipulating the orgId parameter in certain project membership APIs. No other customer data is exposed. The issue was fixed in versions 2.95.11 and 3.124.1. No evidence of exploitation was found in Langfuse Cloud environments. Upgrading is required to fully mitigate this issue.
References
- github.com/langfuse/langfuse/security/advisories/GHSA-94hf-6gqq-pj69 (opens in a new tab)
- github.com/langfuse/langfuse/commit/67990ebfdcf0f0c32a6710efa7ddbda073812ab4 (opens in a new tab)
- github.com/langfuse/langfuse/commit/6c2529049a4c962928c435984c81a547a497e3e5 (opens in a new tab)
- github.com/langfuse/langfuse/releases/tag/v2.70.0 (opens in a new tab)
- github.com/langfuse/langfuse/releases/tag/v2.95.11 (opens in a new tab)
- github.com/langfuse/langfuse/releases/tag/v3.124.1 (opens in a new tab)