Improper Input Validation Affecting langfuse-3 package, versions <3.224.3-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.46% (38th 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-WOLFILATEST-LANGFUSE3-18759488
  • published13 Aug 2026
  • disclosed12 Aug 2026

Introduced: 12 Aug 2026

NewCVE-2026-73418  (opens in a new tab)
CWE-20  (opens in a new tab)
CWE-248  (opens in a new tab)

How to fix?

Upgrade Wolfi langfuse-3 to version 3.224.3-r0 or higher.

NVD Description

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

NextAuth.js provides authentication for Next.js. Prior to @auth/core 0.41.3 and next-auth 4.24.15 and 5.0.0-beta.32, the exported getToken() helper in the next-auth/jwt and @auth/core/jwt modules can throw an uncaught exception when it reads a malformed Authorization: Bearer header. When no session cookie is present, getToken() URL-decodes the bearer value before validating it, and malformed percent encoding causes decodeURIComponent() to throw instead of treating the token as invalid. Because getToken() is commonly called in API routes, middleware, and server-side request handlers, a single unauthenticated request can trigger an unhandled exception in code paths that authenticate requests, causing a per-request denial of service without exposing tokens, sessions, or other data and without bypassing authentication. This issue is fixed in @auth/core 0.41.3 and next-auth 4.24.15 and 5.0.0-beta.32.