Security readout for executives and security teams
Plain-English summary
Crabbox versions before v0.12.0 can leak local environment secrets when used with a malicious or compromised repository. A repo-local Crabbox configuration can cause API tokens, cloud credentials, or broker tokens from a user’s machine to be forwarded into a remote command environment.
Executive priority
Treat as urgent for teams using Crabbox with cloud, API, or broker credentials. Prioritize upgrade, credential exposure review, and secret rotation where affected repositories were processed.
Technical view
The issue is overly permissive environment variable allowlisting in repo-local Crabbox configuration. Prior to v0.12.0, sensitive local environment variables can be serialized into remote command execution. The source bundle lists CVSS 9.3, CVSS v4.0, and CWE-94.
Likely exposure
Exposure is most likely for developers, CI jobs, or automation running affected Crabbox versions against untrusted, malicious, or compromised repositories while sensitive secrets are present in local environment variables.
Exploitation context
The bundle does not show CISA KEV listing or confirmed active exploitation. Practical abuse requires a malicious or compromised repository that can influence repo-local Crabbox configuration and a victim environment containing valuable secrets.
Researcher notes
The affected range is stated as prior to v0.12.0, with a patch commit and release reference supplied. No CPEs are listed. The provided evidence supports high impact secret exposure but not active exploitation.
Mitigation direction
- Upgrade Crabbox to v0.12.0 or later.
- Review vendor release notes and patch guidance for configuration changes.
- Audit repo-local Crabbox configuration for broad environment allowlists.
- Rotate credentials that may have been exposed to remote command environments.
- Limit sensitive environment variables when running Crabbox on untrusted repositories.
Validation and detection
- Inventory Crabbox versions in developer machines and automation runners.
- Identify repositories containing repo-local Crabbox configuration.
- Review allowlists for sensitive names, wildcards, or broad patterns.
- Check remote execution logs for unexpected secret variable exposure.
- Confirm any affected tokens were revoked and replaced.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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.
Open ATT&CK lookupCVE-2026-8634 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.3 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N——VulnCheckCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N3.95.2VulnCheckVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Base CVSS 3.1 score
9.1CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/openclaw/crabbox/releases/tag/v0.12.0CVE reference, VulnCheck · release-notes
- https://github.com/openclaw/crabbox/pull/78CVE reference, VulnCheck · issue-tracking
- https://github.com/openclaw/crabbox/commit/eaae40ae4ce009e60633f16f7f19600c74557f6fCVE reference, VulnCheck · patch
- https://www.vulncheck.com/advisories/crabbox-environment-variable-information-disclosureCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.