CVE-2026-45223: Crabbox < 0.9.0 Authentication Bypass via Admin Claim Injection
Crabbox before 0.9.0 contains an authentication bypass vulnerability in the coordinator user-token verification path where the verifyUserToken() function fails to reject payloads containing an admin claim, allowing attackers to escalate privileges. An attacker with access to the shared non-admin token can craft a user-token payload with admin: true, sign it using HMAC-SHA256, and present it to admin-only coordinator routes to gain full coordinator admin access including lease visibility, pool state management, and forced release operations.
Security readout for executives and security teams
Plain-English summary
Crabbox versions before 0.9.0 can let someone with a shared non-admin token gain coordinator administrator privileges. That could expose lease and pool state information and allow disruptive administrative actions. The issue is high priority where Crabbox coordinates sensitive or production resources.
Executive priority
Treat this as a near-term remediation item for any production Crabbox use. The business risk is unauthorized administrative control over coordinator state, with potential confidentiality, integrity, and availability impact.
Technical view
The coordinator user-token verification path did not reject payloads containing an admin claim. With access to the shared non-admin token, an attacker could submit a signed user token that is accepted for admin-only coordinator routes. The CVSS 3.1 score is 8.8 with network attack vector, low complexity, and privileges required.
Likely exposure
Exposure is most likely in Crabbox deployments running versions before 0.9.0, especially where coordinator admin routes are reachable and shared non-admin tokens are available to users, jobs, or services.
Exploitation context
The source bundle does not show KEV listing, active exploitation, or a public exploit. Exploitation is still plausible because the CVSS vector indicates network reachability, low complexity, no user interaction, and only low privileges required.
Researcher notes
The key security boundary is the coordinator token verifier. Analysis should focus on whether admin claims are rejected or constrained in user-token handling, and whether all admin-only routes consistently depend on the corrected verification behavior.
Mitigation direction
Upgrade Crabbox to version 0.9.0 or later using vendor release guidance.
Confirm deployed builds include commit 46079f6de7f10cf61bc47efebd0c143a41664898 or a later fix.
Limit coordinator admin route reachability to trusted networks or authenticated control planes.
Rotate shared non-admin tokens where exposure is suspected or token handling is unclear.
Review vendor advisory and PR details before applying compensating controls.
Validation and detection
Inventory all Crabbox coordinator deployments and record their running versions.
Verify no production coordinator is running a version before 0.9.0.
Check whether coordinator admin routes are reachable from untrusted networks.
Review logs for unexpected lease visibility, pool state changes, or forced release operations.
Confirm token storage and distribution do not expose shared non-admin tokens unnecessarily.
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 · low confidence lookup
CWE-290: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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.
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
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical 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-290 · source CWE mapping
Authentication Bypass by Spoofing
Authentication Bypass by Spoofing represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.