CVE-2026-56854VulnerabilityPublished 15 Sep 2026Updated 10 Nov 2026

SUSE · Security update for gh

Affects SUSESource GCVE Database

Compare

Mentioned vulnerabilities

Authoritative record:CVE-2026-56854· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade SUSE ssh to 0.55.0 soon.

Data as of 10 Nov 2026, 20:06 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 0.55.0

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade golang.org/x/crypto/ssh to 0.55.0.

Affected software

Product	Affected	Fixed in
golang.org/x/cryptogolang.org/x/crypto/ssh	Affected <0.55.0	Fixed in 0.55.0
Gogolang.org/x/crypto/ssh`pkg:golang/golang.org/x/crypto/ssh`Other threats	Affected <0.55.0	Fixed in 0.55.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

This update for gh fixes the following issues: Changes in gh: Update to version 2.100.0, fixing two deadlock issues in the vendored golang.org/x/crypto/ssh library reachable via crafted SSH channel messages (CVE-2026-56854, CVE-2026-56855, CVE-2026-78662, bsc#1278604): * Fix gh api telemetry disablement * Bump go-gh to v2.16.0 * Expose per-host API host config * chore: bump toolchain to go1.26.8 * chore: bump golang.org/x/crypto to 0.56.0 * Record attachment invocation telemetry * Add webhook as an official extension * Merge pull request #14318 from cli/issue-triage-improvements * Refine GHES support wording * Use version-neutral GHES support link * Clarify supported GHES versions * Bump go-gh to v2.15.0 * Remove redundant searcher comment * Remove unnecessary 204 on release edit * Remove redundant comment in gist create * Comment api command api_host usage * Comment missing api-client-rollout todo * Document when telemetry disabling is overzealous * Refactor AddAuthTokenHeader * Rename tokenGetter to config * build(deps): bump go-gh to rebased per-host api_host branch * refactor(attachments): send uploads through api.Client.DoRequest * test(internal/attachments): add new method required by interface * fix(api): compare request hostname without port when attaching auth token * test(acceptance): fix scriptfilter table field alignment * build(deps): bump go-gh to per-host api_host branch * chore(codeql): cover api.Client.Request in SafeURL path query * fix(auth/shared): route GetScopes path through safeurl * test(config): add coverage for APIHostForHost * test(config): cover deterministic api_host collision resolution * test(api): assert DoRequest preserves an explicit ContentLength * test(acceptance): cover selecting multiple scripts in one directory * refactor(api): use errors.AsType for HTTP error checks * fix(config): resolve api_host collisions deterministically * docs(api): clarify redirect method-rewriting in comments * Send release asset uploads and downloads through api.Client * Let callers set headers on a shared client request * Let a caller stop a request following redirects * Let a caller name the scopes an endpoint needs * Add a raw response request surface to api.Client * Send RenameRepo to a relative path * Make gh api honour api_host for relative paths * Send a host's token to its configured api_host * Add the api_host gateway harness * Let GH_ACCEPTANCE_SCRIPT name several scripts * Wait longer for the search index in the issues script * Add acceptance coverage for gist * Fix discussion acceptance test flags * Resolve aliases to their target when rendering full help on error * Print full help on command misuse for invoking agents Update to version 2.99.0: * Add repeatable --attach flag to upload local images/videos to issues, pull requests, and comments (max 50 files per call) * Add worktree checkout support to gh issue develop --checkout --worktree * Fix repo sync to avoid corrupting a linked worktree and to explain when the target branch is checked out elsewhere * Fix pr merge --delete-branch to safely handle linked worktrees * Reject --comments combined with --json on view commands

References

Community reviews

Loading reviews…