Directory Traversal Affecting trigger-dev package, versions <4.5.0-r0
Threat Intelligence
This vulnerability is trending on Twitter; this may indicate a growing threat.
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 applications- Snyk IDSNYK-MINIMOSLATEST-TRIGGERDEV-19660106
- published10 Sept 2026
- disclosed1 Sept 2026
Introduced: 1 Sep 2026
NewCVE-2026-75604 (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. From 13.4.0 until 15.5.24 and 16.3.3, Next.js applications using Pages Router or App Router without Cache Components on Windows-hosted servers do not consistently escape backslashes in route segments before constructing incremental-cache paths. In packages/next/src/shared/lib/router/utils/escape-path-delimiters.ts and packages/next/src/server/lib/incremental-cache/file-system-cache.ts, a remote request can supply encoded Windows path separators that traverse outside the intended cache root and expose private build data, including the server-reference-manifest encryption key. Disclosure of that key can enable remote code execution in the affected application. This issue is fixed in versions 15.5.24 and 16.3.3.
References
- https://www.cve.org/CVERecord?id=CVE-2026-75604
- https://github.com/advisories/GHSA-p293-qw3h-jr36
- https://osv.dev/vulnerability/MINI-6jhj-g3wm-jwvf
- https://osv.dev/vulnerability/CVE-2026-75604
- https://github.com/vercel/next.js/commit/968b9fcb26bdeb8e0a861a9df05361474666d51b
- https://github.com/vercel/next.js/commit/b0f3460a92b955d3ca41fccff9a525a2b910fbf3
- https://github.com/vercel/next.js/releases/tag/v15.5.24
- https://github.com/vercel/next.js/releases/tag/v16.3.3
- https://github.com/vercel/next.js/security/advisories/GHSA-p293-qw3h-jr36
- https://github.com/rafabd1/CVE-2026-75604-poc