Server-Side Request Forgery (SSRF) Affecting jitsucom-jitsu package, versions <2.11.0-r1
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 applicationsSnyk Learn
Learn about Server-Side Request Forgery (SSRF) vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-CHAINGUARDLATEST-JITSUCOMJITSU-12454140
- published3 Sept 2025
- disclosed29 Aug 2025
Introduced: 29 Aug 2025
NewCVE-2025-57822 (opens in a new tab)How to fix?
Upgrade Chainguard jitsucom-jitsu to version 2.11.0-r1 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream jitsucom-jitsu package and not the jitsucom-jitsu 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.