Information Exposure Through Caching Affecting langfuse-2 package, versions <2.95.12-r35


Severity

Recommended
0.0
medium
0
10

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

Threat Intelligence

EPSS
0.34% (27th 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 IDSNYK-CHAINGUARDLATEST-LANGFUSE2-18292478
  • published24 Jul 2026
  • disclosed27 Jul 2026

Introduced: 24 Jul 2026

CVE-2026-64648  (opens in a new tab)
CWE-524  (opens in a new tab)

How to fix?

Upgrade Chainguard langfuse-2 to version 2.95.12-r35 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream langfuse-2 package and not the langfuse-2 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. In versions 12.0.0 through 15.5.20 and 16.0.0 through 16.2.10, a server-side fetch with a request body may return a cached response body from a different request to the same URL but different body. Confidential data in the POST's response body would then leak to unauthorized requests. Though the request itself will not be deduped. This only applies to fetch calls with a request that has a different init than the one passed to fetch. A safe request would be: fetch(new Request(init), init). An unsafe request would be: fetch(new Request(init), aDifferentInit). This issue has been fixed in versions 15.5.21 and 16.2.11.

CVSS Base Scores

version 3.1