Server-Side Request Forgery (SSRF) Affecting trigger-dev package, versions <4.5.0-r0


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
2.5% (84th 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-MINIMOSLATEST-TRIGGERDEV-17805333
  • published3 Jul 2026
  • disclosed29 Aug 2025

Introduced: 29 Aug 2025

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

How to fix?

Upgrade Minimos:latest trigger-dev to version 4.5.0-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream trigger-dev package and not the trigger-dev package as distributed by Minimos. See How to fix? for Minimos:latest 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