fkie_cve-2025-64504
Vulnerability from fkie_nvd
Published
2025-11-10 22:15
Modified
2025-11-12 16:19
Severity ?
5.0 (Medium) - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N
Summary
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.
References
security-advisories@github.comhttps://github.com/langfuse/langfuse/commit/67990ebfdcf0f0c32a6710efa7ddbda073812ab4
security-advisories@github.comhttps://github.com/langfuse/langfuse/commit/6c2529049a4c962928c435984c81a547a497e3e5
security-advisories@github.comhttps://github.com/langfuse/langfuse/releases/tag/v2.70.0
security-advisories@github.comhttps://github.com/langfuse/langfuse/releases/tag/v2.95.11
security-advisories@github.comhttps://github.com/langfuse/langfuse/releases/tag/v3.124.1
security-advisories@github.comhttps://github.com/langfuse/langfuse/security/advisories/GHSA-94hf-6gqq-pj69
Impacted products
Vendor Product Version


To clipboard 

{
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "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\u2011controlled 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\u2019s 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."
    },
    {
      "lang": "es",
      "value": "Langfuse es una plataforma de ingenier\u00eda de modelos de lenguaje grandes de c\u00f3digo abierto. A partir de la versi\u00f3n 2.70.0 y antes de las versiones 2.95.11 y 3.124.1, en ciertas API de membres\u00eda de proyectos, el servidor confiaba en un orgId controlado por el usuario y lo usaba en las comprobaciones de autorizaci\u00f3n. Como resultado, cualquier usuario autenticado en la misma instancia de Langfuse pod\u00eda enumerar nombres y direcciones de correo electr\u00f3nico de usuarios en otra organizaci\u00f3n si conoc\u00edan el ID de la organizaci\u00f3n objetivo. La divulgaci\u00f3n se limita a nombres y direcciones de correo electr\u00f3nico de miembros/invitados. Ning\u00fan dato de cliente como rastros, prompts o evaluaciones est\u00e1 expuesto o accesible. Para Langfuse Cloud, los mantenedores realizaron una investigaci\u00f3n exhaustiva de los registros de acceso de los \u00faltimos 30 d\u00edas y no pudieron encontrar ninguna evidencia de que esta vulnerabilidad fuera explotada. Para la mayor\u00eda de las implementaciones de autoalojamiento, la superficie de ataque se reduce significativamente dado que un proveedor de SSO est\u00e1 configurado y el registro por correo electr\u00f3nico/contrase\u00f1a est\u00e1 deshabilitado. En estos casos, solo los usuarios que se autentican a trav\u00e9s del IdP de SSO Empresarial (por ejemplo, Okta) podr\u00edan explotar esta vulnerabilidad para acceder a la lista de miembros, es decir, usuarios internos obteniendo acceso a una lista de otros usuarios internos. Para explotar la vulnerabilidad, el actor debe tener una cuenta de usuario v\u00e1lida de Langfuse dentro de la misma instancia, conocer el orgId objetivo y usar la solicitud hecha a la API que alimenta las tablas de membres\u00eda del frontend, incluyendo su token de autenticaci\u00f3n de proyecto/usuario, mientras cambia el orgId a la organizaci\u00f3n objetivo. Langfuse Cloud (UE, EE. UU., HIPAA) se vieron afectados hasta el despliegue de la correcci\u00f3n el 1 de noviembre de 2025. Los mantenedores revisaron los registros de acceso de Langfuse Cloud de los \u00faltimos 30 d\u00edas y no encontraron evidencia de que esta vulnerabilidad fuera explotada. Las versiones autoalojadas que contienen parches incluyen v2.95.11 para la versi\u00f3n principal 2 y v3.124.1 para la versi\u00f3n principal 3. No hay soluciones alternativas conocidas. Se requiere actualizar para mitigar completamente este problema."
    }
  ],
  "id": "CVE-2025-64504",
  "lastModified": "2025-11-12T16:19:59.103",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "NONE",
          "baseScore": 5.0,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "LOW",
          "integrityImpact": "NONE",
          "privilegesRequired": "LOW",
          "scope": "CHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 3.1,
        "impactScore": 1.4,
        "source": "security-advisories@github.com",
        "type": "Secondary"
      }
    ]
  },
  "published": "2025-11-10T22:15:39.273",
  "references": [
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/langfuse/langfuse/commit/67990ebfdcf0f0c32a6710efa7ddbda073812ab4"
    },
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/langfuse/langfuse/commit/6c2529049a4c962928c435984c81a547a497e3e5"
    },
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/langfuse/langfuse/releases/tag/v2.70.0"
    },
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/langfuse/langfuse/releases/tag/v2.95.11"
    },
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/langfuse/langfuse/releases/tag/v3.124.1"
    },
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/langfuse/langfuse/security/advisories/GHSA-94hf-6gqq-pj69"
    }
  ],
  "sourceIdentifier": "security-advisories@github.com",
  "vulnStatus": "Awaiting Analysis",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-202"
        }
      ],
      "source": "security-advisories@github.com",
      "type": "Primary"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.