CVE-2025-59305: 
Wolfi vulnerability analysis and mitigation

CVE-2025-59305 is an improper authorization vulnerability in Langfuse's background migration endpoints that allows any authenticated user to invoke privileged migration control functions. It affects Langfuse versions 3.1.0 through 3.108.x (before 3.109.0 / commit d67b317), and was publicly disclosed on September 24, 2025. The vulnerability carries a CVSS v3.1 base score of 7.6 (High), as assessed by CISA-ADP (Red Hat CVE, Feedly).

The root cause is CWE-285 (Improper Authorization): the TRPC router for background migrations failed to enforce admin-level access controls, allowing any authenticated session to call sensitive endpoints. Specifically, the backgroundMigrations.all, backgroundMigrations.status, and backgroundMigrations.retry TRPC procedures were accessible without verifying that the caller held an admin API key. The fix introduced a dedicated adminProcedure in trpc.ts and refactored AdminApiAuthService to require admin API key verification before any migration retry or status operation is permitted (GitHub PR #9028, DepthFirst Case Study). A public case study notes this vulnerability was discovered by an LLM-based security agent, highlighting a novel AI-assisted vulnerability discovery approach (Reddit r/netsec).

An authenticated low-privilege user can invoke background migration control functions, potentially causing data corruption by triggering unintended or repeated database migrations, disrupting ongoing migration processes, or causing denial of service. The high confidentiality impact score reflects that migration status endpoints may expose sensitive internal system state and data schema information. While the vulnerability does not grant remote code execution, the integrity and availability risks from unauthorized migration retries in a production AI observability platform can be significant (Feedly, DepthFirst Case Study).

A proof-of-concept case study is publicly available on depthfirst.com, demonstrating how the authorization flaw can be exploited. There is no evidence of active in-the-wild exploitation at this time, and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. The EPSS score is approximately 0.038%, indicating low near-term exploitation probability. Exploitation requires only a valid authenticated session (low privilege), making it accessible to any registered user of a vulnerable Langfuse instance (Feedly, DepthFirst Case Study).

1. Reconnaissance: Identify a Langfuse instance running version 3.1.0–3.108.x (before commit d67b317 / version 3.109.0). This can be done by checking version disclosure in the UI or API responses.
2. Authenticate: Obtain any valid authenticated session — even a low-privilege user account suffices. Log in via the Langfuse web interface or API to acquire a session token or API key.
3. Invoke unauthorized TRPC endpoints: Send authenticated HTTP requests directly to the TRPC API endpoints that lack proper authorization checks, such as:
   • backgroundMigrations.all — to enumerate all background migrations and their state
   • backgroundMigrations.status — to retrieve detailed status of ongoing migrations
   • backgroundMigrations.retry — to trigger a retry of a migration, potentially causing data corruption or service disruption
4. Achieve objective: Depending on intent, the attacker can enumerate sensitive migration metadata (confidentiality impact), trigger repeated or conflicting migration retries to corrupt database state (integrity impact), or cause service disruption by repeatedly invoking migration operations (availability impact) (DepthFirst Case Study, GitHub PR #9028).

• Network: Unusual authenticated HTTP POST requests to TRPC endpoints containing backgroundMigrations.all, backgroundMigrations.status, or backgroundMigrations.retry from non-admin user sessions; repeated calls to these endpoints in short succession.
• Logs: Application logs showing low-privilege user accounts invoking background migration TRPC procedures; unexpected migration retry events in Langfuse server logs outside of scheduled maintenance windows.
• Application Behavior: Unexpected database migration activity or repeated migration retries visible in the Langfuse admin dashboard; migration status changes not initiated by administrators.

Langfuse addressed this vulnerability in version 3.109.0 (commit d67b317 / merged via PR #9028 on September 10, 2025). The fix requires an admin API key for all background migration TRPC endpoints by introducing a dedicated adminProcedure and refactoring AdminApiAuthService. All users running Langfuse 3.1.0 through 3.108.x should upgrade to 3.109.0 or later immediately. As a temporary workaround prior to upgrading, restrict network access to the Langfuse TRPC API to trusted admin users only, and audit user accounts with access to the platform (GitHub PR #9028, Feedly).

The vulnerability attracted notable community attention primarily due to its discovery method: an LLM-based security agent reportedly found the zero-day, sparking discussion across Reddit (r/netsec, r/cybersecurity, r/ComputerSecurity) and Bluesky about AI-assisted vulnerability research. The DepthFirst case study framing it as a "common security blind spot" resonated with the appsec community. No major vendor statements beyond the GitHub fix and CVE disclosure have been issued (Reddit r/netsec, Reddit r/cybersecurity).