Improper Handling of Exceptional Conditions Affecting trigger-dev package, versions <4.5.11-r1


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.52% (42nd 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-18864185
  • published17 Aug 2026
  • disclosed30 Jul 2026

Introduced: 30 Jul 2026

CVE-2026-59952  (opens in a new tab)
CWE-755  (opens in a new tab)

How to fix?

Upgrade Minimos:latest trigger-dev to version 4.5.11-r1 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.

Valibot helps validate data using a schema. Versions prior to 1.4.2 can throw a TypeError inside its flatten() helper when validation issues contain attacker-controlled object keys such as toString, valueOf, or hasOwnProperty. The issue is reachable through normal record() validation. record() intentionally filters proto, prototype, and constructor, but it still accepts other own keys that collide with inherited Object.prototype properties. If the record key schema or value schema rejects such an entry, Valibot creates an issue path containing that key. Passing the resulting issues to Valibot's documented flatten() helper causes flatErrors.nested[dotPath] to resolve to the inherited method instead of an own error array, and the helper calls .push(...) on that function. This is not a global prototype pollution issue. The impact is availability/error handling: applications that validate user-controlled objects with record() and flatten validation errors for API responses can crash the request path with a TypeError instead of returning structured validation errors. This issue has been fixed in version 1.4.2.