/

CVE-2026-67614

Severity:

CRITICAL RISK

(9.8)

Hard-Coded JWT Secret (CWE-798) in CyberPanel WebTerminal

CVE-2026-67614

Deferred

Vulnerability type

Category:

Hard-Coded Credentials

CWE:

CWE-798

Impact:

Unauthenticated Remote Code Execution

Severity:

CRITICAL RISK

(9.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

CyberPanel versions before 3.0.0 use a hard-coded secret to sign JWTs for the WebTerminal FastAPI SSH service. An unauthenticated remote attacker may forge authentication tokens and obtain an interactive root shell through the WebSocket service exposed on port 8888.

Affected context

The vulnerability occurs in CyberPanel deployments before version 3.0.0 where the WebTerminal FastAPI SSH service uses a secret embedded in the application for JWT signing. When the service is reachable over the network and trusts tokens signed with that fixed secret, attackers may bypass normal authentication and access the terminal with elevated privileges.

Exploit preconditions

  • Attack surface: WebTerminal WebSocket service exposed on port 8888
  • Required access: Network connectivity to the service; no valid user credentials are required
  • Trigger point: JWT authentication performed when establishing a WebSocket terminal session
  • Why exploitation is possible: The service uses a predictable, hard-coded signing secret and accepts attacker-controlled authentication claims, allowing forged tokens to be treated as valid

Why this happens

The underlying flaw is the embedding and reuse of a security-sensitive JWT signing secret in application code or otherwise fixed deployment logic. This maps to CWE-798: Use of Hard-coded Credentials, because knowledge of the static secret can enable authentication bypass across affected installations. Trusting forged identity and privilege claims after signature validation further increases the impact when those claims can select a root-level terminal session.

Potential impact

  • An unauthenticated attacker may obtain an interactive root shell
  • Attackers could execute arbitrary commands on the CyberPanel host
  • Sensitive files, credentials, and hosted application data may be accessed
  • System configuration and hosted services may be altered or disrupted
  • The host could be used for lateral movement or additional compromise

General mitigation guidance

Mitigation generally focuses on removing hard-coded authentication material and strengthening the token trust boundary.

Common defensive patterns include:

  • Generate unique, high-entropy signing keys per deployment and store them in protected secret-management systems
  • Rotate signing keys and invalidate tokens issued under compromised or obsolete keys
  • Enforce strict validation of token issuer, audience, algorithm, expiration, and privilege claims
  • Avoid allowing client-controlled claims to select privileged operating-system identities
  • Restrict WebTerminal exposure to trusted management networks or authenticated gateways
  • Run terminal services with the minimum operating-system privileges required
  • Monitor and limit administrative WebSocket access

How teams detect issues like this

Organizations can identify related weaknesses through:

  • Static analysis searches for JWT signing keys, passwords, or credential-like constants embedded in source code
  • Code review checks for fixed secrets, weak secret-generation practices, and unrestricted privilege claims
  • Dependency and configuration policy rules requiring external secret storage and key rotation
  • Runtime monitoring for unexpected WebSocket connections to administrative terminal services
  • Authentication telemetry identifying token validation anomalies, unusual administrative sessions, or access from untrusted networks

Automated security review tools may help flag hard-coded credentials and insecure authentication patterns, but findings should be validated against deployment configuration.

Sources

SourceLink
cyberpanel.netcyberpanel.net/KnowledgeBase/home/change-logs/
github.comgithub.com/usmannasir/cyberpanel/issues/1858
vulncheck.comvulncheck.com/advisories/cyberpanel-hard-coded-jwt-secret-authentication-bypass-via-webterminal

Frequently asked

questions

Yes. If the WebTerminal service is network-reachable, exploitation may occur remotely without valid CyberPanel credentials.

The attacker generally needs network access to the WebTerminal WebSocket service. The flaw does not require prior authentication when the service accepts tokens signed with the exposed secret.

Replace fixed signing material with unique, high-entropy deployment secrets stored outside application code, rotate potentially exposed keys, and enforce strict validation of token claims and privileges.

Use centralized secret management, prohibit credentials in source code, apply least privilege to terminal processes, restrict administrative service exposure, and continuously scan code and configurations for embedded secrets.

Find out what's already
exploitable in your codebase.