Skip to main content
Vulnerability Database/CVE-2026-111638

CVE-2026-111638: sshportal Auth Bypass Vulnerability

CVE-2026-111638 is an authorization bypass flaw in sshportal that allows non-admin users to obtain decrypted backend SSH keys and bypass ACLs. This post explains its impact, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-111638 Overview

CVE-2026-111638 is a missing authorization vulnerability [CWE-862] in sshportal through version 1.19.5. The flaw resides in the management shell key show command, which fails to enforce administrative access controls. Authenticated non-admin users can request predictable key names such as default or host and receive the decrypted backend private SSH keys in response. With those keys in hand, attackers connect directly to backend hosts, bypassing the ACLs and session recording that sshportal is designed to enforce. The issue breaks the core trust model of the SSH bastion by turning any low-privilege user account into a path to full backend access.

Critical Impact

Any authenticated sshportal user can extract decrypted backend SSH private keys and pivot directly to managed hosts, bypassing bastion ACLs and session logging.

Affected Products

  • sshportal versions up to and including 1.19.5
  • Deployments relying on sshportal-managed SSH keys named with predictable identifiers (for example default, host)
  • Any environment using sshportal as an SSH bastion for backend host access control

Discovery Timeline

  • 2026-10-16 - CVE-2026-111638 published to the National Vulnerability Database
  • 2026-10-16 - Last updated in NVD database

Technical Details for CVE-2026-111638

Vulnerability Analysis

sshportal is a Go-based SSH bastion that stores backend host private keys in an encrypted database and brokers sessions on behalf of authenticated users. Administrators interact with the bastion through a management shell exposed over SSH, which includes a key show command used to inspect stored keys. The implementation of this command in pkg/bastion/shell.go does not verify that the requesting user holds administrative privileges before returning key material. As a result, any user who can reach the management shell receives the decrypted private key when they supply a known key name.

The practical impact is a complete bypass of the bastion's access control model. sshportal normally enforces per-host ACLs and records sessions through its proxy. Once an attacker extracts a backend private key, they connect directly to the target host, leaving no sshportal session record and ignoring ACL restrictions. Because key names such as default and host are predictable defaults in many deployments, exploitation does not require prior knowledge of the environment.

Root Cause

The root cause is a missing authorization check [CWE-862] in the key show command handler. The function retrieves and decrypts the requested key without validating the caller's role. Authentication to the management shell is treated as sufficient, even though key disclosure should be restricted to administrators. See the GitHub sshportal Code Reference for the vulnerable code path.

Attack Vector

An attacker needs valid non-admin credentials to the sshportal management shell. After connecting, they issue a key show command with a predictable key name. sshportal returns the decrypted PEM-encoded private key, which the attacker saves locally and uses with ssh -i to authenticate to the corresponding backend host as the key's owner. For additional technical analysis, see the HackMD Privkey Disclosure Analysis and the VulnCheck Advisory on sshportal.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-111638

Indicators of Compromise

  • Execution of key show commands in sshportal management shell logs by accounts that are not members of the admin role
  • Direct SSH authentications to backend hosts from source IPs that previously only connected through the sshportal bastion
  • Unexpected use of SSH keys whose fingerprints match sshportal-managed backend keys from hosts outside the bastion

Detection Strategies

  • Audit sshportal command history and session logs for any key show invocation, correlating each one against the authenticated user's role.
  • Monitor backend hosts for successful SSH logins that bypass the bastion, using source IP allowlists that normally restrict access to the sshportal IP.
  • Compare fingerprints of keys presented to backend sshd services against the inventory of sshportal-managed keys to detect direct reuse.

Monitoring Recommendations

  • Forward sshportal shell logs and backend sshd authentication logs to a centralized analytics platform for correlation.
  • Alert on any non-admin account executing privileged commands in the management shell, including key show, user, and host subcommands.
  • Track process and network telemetry on backend hosts for SSH sessions originating outside the approved bastion path.

How to Mitigate CVE-2026-111638

Immediate Actions Required

  • Restrict access to the sshportal management shell to trusted administrators only, pending a fixed release.
  • Rotate all backend SSH private keys managed by sshportal, since any key previously exposed through key show must be considered compromised.
  • Review sshportal audit logs for prior key show executions by non-admin users and treat matching keys as leaked.

Patch Information

At the time of publication, the enriched CVE data does not list a fixed sshportal release. Monitor the upstream sshportal repository and the VulnCheck Advisory on sshportal for a patched version that enforces admin-only authorization on the key show command.

Workarounds

  • Limit which user accounts can reach the sshportal management shell, for example by removing shell access from non-admin roles.
  • Enforce network-layer controls so backend hosts only accept SSH connections from the sshportal bastion IP, reducing the value of a leaked key.
  • Replace predictable key names such as default and host with unguessable identifiers to raise the difficulty of blind extraction attempts.
bash
# Example sshd configuration on backend hosts to restrict SSH to the bastion IP
# /etc/ssh/sshd_config.d/99-bastion-only.conf
Match Address !BASTION_IP,*
    DenyUsers *

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.