When writing data larger than 4GB in a single Write call on an SSH channel, an integer overflow in the internal payload size calculation caused the write loop to spin indefinitely, sending empty packets without making progress. The size comparison now uses int64 to prevent truncation.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Amazon Linux Ami 2 | — | Upgrade containerdUpgrade runfinch-finchUpgrade amazon-ssm-agentUpgrade containerd-debuginfoUpgrade containerd-stressUpgrade amazon-cloudwatch-agentUpgrade nerdctlUpgrade nerdctl-debuginfo | Jun 9, 2026 | Jun 9, 2026 |
| Amazon_linux_2023 | — | Upgrade amazon-ssm-agentUpgrade containerdUpgrade nerdctlUpgrade containerd-debuginfoUpgrade amazon-cloudwatch-agentUpgrade rclone-debuginfoUpgrade runfinch-finchUpgrade containerd-stressUpgrade rclone-debugsourceUpgrade rcloneUpgrade containerd-stress-debuginfoUpgrade containerd-debugsource | Jun 9, 2026 | May 22, 2026 |
| Redhat_linux | — | No solution exists | Oct 16, 2026 | May 22, 2026 |
| Ubuntu | — | Upgrade google-guest-agentUpgrade golang-go.crypto-dev (Ubuntu Pro)Upgrade google-guest-agent (Ubuntu Pro)Upgrade golang-golang-x-crypto-dev (Ubuntu Pro)Upgrade lxd (Ubuntu Pro) | Jun 18, 2026 | Jun 17, 2026 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub