Server-Side Request Forgery (SSRF) Affecting langfuse package, versions <3.106.1-r1


Severity

Recommended
0.0
high
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

Exploit Maturity
Proof of Concept
EPSS
5.85% (91st percentile)

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 Learn

Learn about Server-Side Request Forgery (SSRF) vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-CHAINGUARDLATEST-LANGFUSE-12483952
  • published3 Sept 2025
  • disclosed29 Aug 2025

Introduced: 29 Aug 2025

NewCVE-2025-57822  (opens in a new tab)
CWE-918  (opens in a new tab)

How to fix?

Upgrade Chainguard langfuse to version 3.106.1-r1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream langfuse package and not the langfuse package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1