CVE-2026-73519: WolfStack < 25.9.2 Hard-coded Secret Authentication Bypass via X-WolfStack-Secret
WolfStack before 25.9.2 contains a hard-coded cluster-authentication secret compiled into every build and published as a constant in src/auth/mod.rs, allowing remote unauthenticated attackers to bypass authentication by supplying this value in the X-WolfStack-Secret header to the require_auth() gate without any session, API key, or user account. Attackers can reach an affected node's management port to enumerate all Docker and LXC containers on the host and execute arbitrary commands as root inside any container via the POST /api/containers/{runtime}/{id}/exec endpoint.
Security readout for executives and security teams
Plain-English summary
WolfStack versions before 25.9.2 share a publicly disclosed authentication secret. Anyone who can reach an affected management port could impersonate a trusted cluster request, view hosted containers, and run commands with root privileges inside them. Compromise could expose sensitive container data, disrupt services, or enable further intrusion.
Executive priority
Treat this as an immediate remediation priority. A reachable vulnerable node can expose every managed container to unauthenticated administrative command execution. Isolate exposed management interfaces, upgrade promptly, and initiate incident review where suspicious access or container activity appears.
Technical view
The require_auth() gate accepts a hard-coded value through the X-WolfStack-Secret header without requiring a session, API key, or account. Because the constant was compiled into every affected build and publicly available in source, a remote unauthenticated attacker reaching the management interface could enumerate Docker and LXC containers and invoke the container execution API as container root.
Likely exposure
Exposure is highest for WolfStack nodes earlier than 25.9.2 whose management ports are reachable from untrusted networks. Internally reachable nodes also remain at risk from compromised systems or malicious insiders. The source bundle does not quantify deployed instances or internet exposure.
Exploitation context
The vulnerability has low attack complexity and requires neither credentials nor user interaction. The supplied record is not listed in KEV, and the provided sources do not establish active exploitation. Absence from KEV is not evidence that exploitation has not occurred.
Researcher notes
CVE-2026-73519 is categorized as CWE-798 with CVSS 3.1 score 9.8. The supplied affected-version metadata includes an ambiguous “0,” while the title and advisory scope state versions before 25.9.2. Validate exact package versions against the vendor advisory. Evidence establishes container-root execution, not automatic host-root compromise.
Mitigation direction
Upgrade all WolfStack deployments earlier than 25.9.2 according to the vendor release guidance.
Until upgraded, restrict management-port access to explicitly trusted administrative systems and networks.
Prioritize internet-accessible and business-critical nodes for immediate containment and remediation.
Check current vendor guidance for any additional secret-handling or post-compromise actions.
Validation and detection
Inventory WolfStack nodes and confirm each installed version is 25.9.2 or later.
Verify management ports are not reachable from untrusted or unnecessary network segments.
Review available access logs for unexpected authentication-header use and container execution requests.
Investigate unexplained container commands, configuration changes, new processes, or access to sensitive data.
After upgrading, confirm normal administration works and applicable authentication controls remain enforced.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-798: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
3Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-798 · source CWE mapping
Use of Hard-coded Credentials
Use of Hard-coded Credentials represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.