/

CVE-2026-73519

Severity:

CRITICAL RISK

(9.8)

Hard-Coded Secret (CWE-798) in WolfStack Management

CVE-2026-73519

Deferred

Vulnerability type

Category:

Use of Hard-Coded Credentials

CWE:

CWE-798

Impact:

Authentication Bypass and Remote Container Command 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

WolfStack before 25.9.2 contains a hard-coded cluster-authentication secret that is embedded in every build and accepted by the management authentication gate. An unauthenticated remote attacker who can reach an affected node's management port may bypass authentication, enumerate containers, and execute commands as root inside containers.

Affected context

The vulnerability occurs in WolfStack management interfaces when:

  • The deployed version contains the compiled-in authentication secret
  • The management port is reachable by an attacker
  • The authentication gate accepts the static value from the X-WolfStack-Secret header

No session, API key, or user account is required when these conditions are present.

Exploit preconditions

  • Attack surface: WolfStack's remotely reachable management port
  • Required access: Network connectivity to an affected node; no authenticated account is required
  • Trigger point: The require_auth() gate processing the X-WolfStack-Secret header
  • Why exploitation is possible: A secret shared across builds is predictable or recoverable from the product and is accepted as sufficient authentication
  • Post-authentication capability: Access to container-management endpoints, including container enumeration and command execution

Why this happens

The underlying flaw is the inclusion of a reusable authentication secret directly in the application build and source code. Because the same static value is trusted by the authentication gate across deployments, possession of or access to that value provides authentication without proving the identity of a specific user, session, or installation.

This maps to CWE-798: Use of Hard-Coded Credentials, where a credential is embedded in software rather than securely provisioned and managed as deployment-specific secret material.

Potential impact

  • Unauthenticated attackers may bypass management-plane authentication
  • Attackers could enumerate Docker and LXC containers on the host
  • Attackers may execute arbitrary commands inside containers
  • Commands could run with root privileges within affected containers
  • A compromised container could be used for data theft, tampering, or further lateral movement
  • Host or cluster security could be weakened depending on container isolation and management permissions

General mitigation guidance

Mitigation generally focuses on removing shared credentials from application binaries and establishing deployment-specific authentication.

Common defensive patterns include:

  • Replacing compiled-in secrets with securely provisioned, installation-specific credentials
  • Using short-lived tokens, mutually authenticated channels, or an external identity provider
  • Ensuring authentication decisions bind credentials to a specific deployment and authorized principal
  • Restricting management-port exposure to trusted networks or administrative gateways
  • Applying least privilege to container-management operations and execution identities
  • Separating container enumeration, execution, and administrative actions into narrowly scoped permissions
  • Rotating any credentials that may have been exposed through builds, repositories, or deployed binaries

How teams detect issues like this

Detection can combine source review, binary inspection, configuration analysis, and network monitoring.

Useful approaches include:

  • Static analysis rules that flag authentication constants, embedded secrets, and comparisons against fixed header values
  • Code review checks for authentication gates that accept a single global credential
  • Secret-scanning and binary-analysis policies covering compiled artifacts and release packages
  • Monitoring management-port access, failed and successful authentication events, and unusual container enumeration
  • Alerting on unexpected requests to container execution endpoints or command activity from management clients
  • Policy enforcement that prevents direct public exposure of administrative interfaces

Automated security review tools may help identify hard-coded credentials, but findings should be validated against deployment-specific controls.

Sources

SourceLink
github.comgithub.com/wolfsoftwaresystemsltd/WolfStack/releases?page=7#release-v25.9.2
github.comgithub.com/wolfsoftwaresystemsltd/WolfStack/security/advisories/GHSA-r3mw-2wmq-j6jg
vulncheck.comvulncheck.com/advisories/wolfstack-hard-coded-secret-authentication-bypass-via-x-wolfstack-secret

Frequently asked

questions

Yes, when an affected WolfStack management port is reachable by the attacker. The described attack does not require a session, API key, or user account.

Network access to the management interface is the primary prerequisite. The attacker does not need legitimate application credentials if the embedded secret is accepted by the authentication gate.

Remove the hard-coded shared secret and use deployment-specific, securely provisioned authentication with narrowly scoped authorization. Management interfaces should also be restricted to trusted administrative networks.

Use secret-management systems, prohibit credentials in source code and binaries, scan release artifacts, review authentication gates for global bypass values, and monitor container-management operations.

Find out what's already
exploitable in your codebase.