Skip to content

x/crypto/ssh: byte arithmetic causes underflow and panic #79561

Closed
Closed
x/crypto/ssh: byte arithmetic causes underflow and panic#79561
Labels
NeedsFixThe path to resolution is known, but the work has not been done.Securityrelease-blocker
Milestone
Unreleased

Description

@thatnealpatel
thatnealpatel
opened on May 21, 2026

An incorrectly placed cast from bytes to int
allowed for server-side panic in the AES-GCM
packet decoder for well-crafted inputs.

Thanks to Maciej Kawka for reporting this issue.

This is CVE-2026-46597 and Go issue https://go.dev/issue/79561.

This was a PRIVATE track issue, tracked in http://b/504678385.

Activity

  1. thatnealpatel
    added
    Security
    release-blocker
    on May 21, 2026
  2. JunyangShao
    added
    NeedsFixThe path to resolution is known, but the work has not been done.
    on May 21, 2026

  3. gopherbot commented on May 21, 2026

    @gopherbot
    gopherbot
    on May 21, 2026
    Contributor

    Change https://go.dev/cl/781620 mentions this issue: ssh: fix incorrect operator order

  4. gopherbot
    closed this as completedin abbc44don May 22, 2026
  5. thatnealpatel
    changed the title [-]security: fix CVE-2026-46597[/-] [+]ssh: byte arithmetic causes underflow and panic[/+] on May 22, 2026
  6. pull
    added a commit that references this issue on May 22, 2026

    ssh: fix incorrect operator order

    abbc44d
  7. dmitshur
    changed the title [-]ssh: byte arithmetic causes underflow and panic[/-] [+]x/crypto/ssh: byte arithmetic causes underflow and panic[/+] on May 22, 2026
  8. dmitshur
    added this to the Unreleased milestone on May 22, 2026
  9. germanparente
    added a commit that references this issue on Jul 30, 2026

    ssh: fix incorrect operator order

    32eca92
  10. Atharva-Shinde
    added a commit that references this issue on Jul 30, 2026

    ssh: fix incorrect operator order

    1453ff3
  11. wwqgtxx
    added a commit that references this issue on Aug 26, 2026

    ssh: fix incorrect operator order

    be6c13b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    NeedsFixThe path to resolution is known, but the work has not been done.Securityrelease-blocker

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions