Uncaught Exception Affecting n8n package, versions <2.35.3-r0
Threat Intelligence
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-N8N-18955502
- published19 Aug 2026
- disclosed8 Jul 2026
Introduced: 8 Jul 2026
CVE-2026-59892 (opens in a new tab)How to fix?
Upgrade Minimos:latest n8n to version 2.35.3-r0 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream n8n package and not the n8n package as distributed by Minimos.
See How to fix? for Minimos:latest relevant fixed versions and status.
OpenTelemetry JavaScript is the OpenTelemetry JavaScript client. Prior to 2.9.0, @opentelemetry/propagator-jaeger decodes incoming uber-trace-id and uberctx-* HTTP header values with decodeURIComponent() without handling decode errors, allowing an unauthenticated remote attacker to send a malformed percent-encoded value that throws an uncaught URIError and terminates a Node.js process using JaegerPropagator as the active propagator. This issue is fixed in version 2.9.0.
References
- https://www.cve.org/CVERecord?id=CVE-2026-59892
- https://github.com/advisories/GHSA-45rx-2jwx-cxfr
- https://osv.dev/vulnerability/MINI-7rx8-mvcg-2fp9
- https://osv.dev/vulnerability/CVE-2026-59892
- https://github.com/open-telemetry/opentelemetry-js/commit/b1c196d49d54caae59741cca0a9d57d101d7ea88
- https://github.com/open-telemetry/opentelemetry-js/releases/tag/v2.9.0
- https://github.com/open-telemetry/opentelemetry-js/security/advisories/GHSA-45rx-2jwx-cxfr