Server-Side Request Forgery (SSRF) The advisory has been revoked - it doesn't affect any version of package langfuse (opens in a new tab)
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-WOLFILATEST-LANGFUSE-15400518
- published5 Mar 2026
- disclosed29 Aug 2025
Introduced: 29 Aug 2025
CVE-2025-57822 (opens in a new tab)Amendment
The Wolfi security team deemed this advisory irrelevant for Wolfi:latest.
NVD Description
Note: Versions mentioned in the description apply only to the upstream langfuse package and not the langfuse package as distributed by Wolfi.
Next.js is a React framework for building full-stack web applications. Prior to versions 14.2.32 and 15.4.7, when next() was used without explicitly passing the request object, it could lead to SSRF in self-hosted applications that incorrectly forwarded user-supplied headers. This vulnerability has been fixed in Next.js versions 14.2.32 and 15.4.7. All users implementing custom middleware logic in self-hosted environments are strongly encouraged to upgrade and verify correct usage of the next() function.