CVE-2026-78662 Affecting argo-events package, versions <1.9.11-r10


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.32% (24th 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-CHAINGUARDLATEST-ARGOEVENTS-19539232
  • published5 Sept 2026
  • disclosed2 Sept 2026

Introduced: 2 Sep 2026

NewCVE-2026-78662  (opens in a new tab)

How to fix?

Upgrade Chainguard argo-events to version 1.9.11-r10 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream argo-events package and not the argo-events package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

Previously, a channel registered in the mux's chanList is not usable until it is established. A malicious peer was able flood the channel's incomingRequests, deadlocking the entire connection. Now, we add an atomic established state, set when a channel becomes usable. Until such a time, handlePacket drops every packet other than the open confirmation/failure, without blocking and without tearing down the connection.

CVSS Base Scores

version 3.1