Langfuse is an open source large language model engineering platform. Starting in version 2.70.0 and prior to versions 2.95.11 and 3.124.1, in certain project membership APIs, the server trusted a user‑controlled orgId and used it in authorization checks. As a result, any authenticated user on the same Langfuse instance could enumerate names and email addresses of users in another organization if they knew the target organization’s ID. Disclosure is limited to names and email addresses of members/invitees. No customer data such as traces, prompts, or evaluations is exposed or accessible. For Langfuse Cloud, the maintainers ran a thorough investigation of access logs of the last 30 days and could not find any evidence that this vulnerability was exploited. For most self-hosting deployments, the attack surface is significantly reduced given an SSO provider is configured and email/password sign-up is disabled. In these cases, only users who authenticate via the Enterprise SSO IdP (e.g. Okta) would be able to exploit this vulnerability to access the member list, i.e. internal users getting access to a list of other internal users. In order to exploit the vulnerability, the actor must have a valid Langfuse user account within the same instance, know the target orgId, and use the request made to the API that powers the frontend membership tables, including their project/user authentication token, while changing the orgId to the target organization. Langfuse Cloud (EU, US, HIPAA) were affected until fix deployment on November 1, 2025. The maintainers reviewed the Langfuse Cloud access logs from the past 30 days and found no evidence that this vulnerability was exploited. Self-Hosted versions which contain patches include v2.95.11 for major version 2 and v3.124.1 for major version 3. There are no known workarounds. Upgrading is required to fully mitigate this issue.
CVE-2025-64504
“—” beside the score: it is equal to the CVSS score beside it.
This medium-severity CVE scores 5.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (27th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Also known asEUVD-2025-50817 (ENISA EUVD)Source: ENISA EUVD
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 5.0
- EG Score
- 5.0MEDIUMmedium confidence
- EG Risk
- 23EG Risk 23/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity50% × 45%Impact severity (EG Severity): CVSS 5.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.3% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.3%
- EPSS %ILE
- 27th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (5.0): severity, escalated by confirmed exploitation. This CVE's 5.0 is its impact severity (EG Severity), not escalated.
- EG Severity
- 5.0 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
- EG Likelihood
- 0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
November 10, 2025
Last Modified
June 17, 2026
Advisory Details (6)
Auto-updated Oct 23, 2026Cross‑organization enumeration of member & invitation lists via project membership APIs · Advisory · langfuse/langfuse · GitHub
https://github.com/langfuse/langfuse/security/advisories/GHSA-94hf-6gqq-pj69v3.124.1
Patch available: langfuse/langfuse v3.124.1
https://github.com/langfuse/langfuse/releases/tag/v3.124.1v2.95.11
Patch available: langfuse/langfuse v2.95.11
https://github.com/langfuse/langfuse/releases/tag/v2.95.11v2.70.0
Patch available: langfuse/langfuse v2.70.0
https://github.com/langfuse/langfuse/releases/tag/v2.70.0commit 6c2529049a4c (langfuse/langfuse)
Patch available: langfuse/langfuse v4.44.0 (contains commit 6c2529049a4c)
https://github.com/langfuse/langfuse/commit/6c2529049a4c962928c435984c81a547a497e3e5commit 67990ebfdcf0 (langfuse/langfuse)
Patch available: langfuse/langfuse v4.44.0 (contains commit 67990ebfdcf0)
https://github.com/langfuse/langfuse/commit/67990ebfdcf0f0c32a6710efa7ddbda073812ab4Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 38× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 95 of 193 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 98 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.3% · 27th percentile
- 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
- 2026-10-31 18:25 UTCOSV refresh
- 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.3% · 27th percentile
- 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
- 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.3% · 27th percentile
- 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.3% · 27th percentile
- 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.3% · 27th percentile
- 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.3% · 27th percentile
- 2026-10-25 16:31 UTCEPSS rescoreEPSS 0.3% · 27th percentile
- 2026-10-25 16:11 UTCEG score recompute
- 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-10-23 13:33 UTCEG score recompute
- 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-10-18 05:20 UTCEG score recompute
- 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-10-16 16:39 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
Show 70 moreShow fewer
- 2026-10-12 16:49 UTCEG score recompute
- 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-10-11 20:24 UTCEG score recompute
- 2026-10-11 18:36 UTCEG score recompute
- 2026-10-11 15:11 UTCEG score recompute
- 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
- 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
- 2026-10-08 17:10 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
- 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
- 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
- 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
- 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
- 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
- 2026-10-02 00:41 UTCOSV refresh
- 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
- 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
- 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
- 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
- 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
- 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
- 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-09-19 15:42 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-09-15 03:10 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-09-12 18:06 UTCOSV refresh
- 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-08-24 23:44 UTCOSV refresh
- 2026-08-24 14:16 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-08-08 16:55 UTCOSV refresh
- 2026-08-08 16:36 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-08-07 16:26 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-08-04 15:09 UTCEPSS rescoreEPSS 0.3% · 24th percentile
- 2026-08-04 10:37 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-08-02 02:26 UTCEPSS rescoreEPSS 0.3% · 25th percentile
- 2026-08-01 04:15 UTCEPSS rescoreEPSS 0.3% · 25th percentile
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2025-64504?
When was the CVE record for CVE-2025-64504 published?
Is CVE-2025-64504 actively exploited?
What is the CVSS score of CVE-2025-64504?
How do I remediate CVE-2025-64504?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2025-64504
Is Your Infrastructure Affected by CVE-2025-64504?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.