OpenClaw up to 2026.2.22 Environment Variable /opt/homebrew/bin SHELL inclusion of functionality from untrusted control sphere
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in OpenClaw up to 2026.2.22. It has been rated as problematic. Impacted is an unknown function of the file /opt/homebrew/bin of the component Environment Variable Handler. Performing a manipulation of the argument SHELL results in inclusion of functionality from untrusted control sphere. This vulnerability is reported as CVE-2026-22217. The attack requires a local approach. No exploit exists. Upgrading the affected component is advised.
Details
A vulnerability classified as problematic has been found in OpenClaw up to 2026.2.22. This affects an unknown function of the file /opt/homebrew/bin of the component Environment Variable Handler. The manipulation of the argument SHELL with an unknown input leads to a inclusion of functionality from untrusted control sphere vulnerability. CWE is classifying the issue as CWE-829. The product imports, requires, or includes executable functionality (such as a library) from a source that is outside of the intended control sphere. This is going to have an impact on integrity, and availability. The summary by CVE is:
OpenClaw version 2026.2.22 prior to 2026.2.23 contains an arbitrary code execution vulnerability in shell-env that allows attackers to execute attacker-controlled binaries by exploiting trusted-prefix fallback logic for the $SHELL variable. An attacker can influence the $SHELL environment variable on systems with writable trusted-prefix directories such as /opt/homebrew/bin to execute arbitrary binaries in the OpenClaw process context.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-22217 since 01/06/2026. The exploitability is told to be difficult. An attack has to be approached locally. Technical details are known, but no exploit is available.
Upgrading to version 2026.2.23 eliminates this vulnerability. Applying the patch ff10fe8b91670044a6bb0cd85deb736a0ec8fb55 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
- 2026.2.0
- 2026.2.1
- 2026.2.2
- 2026.2.3
- 2026.2.4
- 2026.2.5
- 2026.2.6
- 2026.2.7
- 2026.2.8
- 2026.2.9
- 2026.2.10
- 2026.2.11
- 2026.2.12
- 2026.2.13
- 2026.2.14
- 2026.2.15
- 2026.2.16
- 2026.2.17
- 2026.2.18
- 2026.2.19
- 2026.2.20
- 2026.2.21
- 2026.2.22
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 5.8VulDB Meta Temp Score: 5.8
VulDB Base Score: 3.6
VulDB Temp Score: 3.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD Vector: 🔒
CNA Base Score: 6.1
CNA Vector (VulnCheck): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Inclusion of functionality from untrusted control sphereCWE: CWE-829
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: OpenClaw 2026.2.23
Patch: ff10fe8b91670044a6bb0cd85deb736a0ec8fb55
Timeline
01/06/2026 CVE reserved03/18/2026 Advisory disclosed
03/18/2026 VulDB entry created
05/27/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-p4wh-cr8m-gm6c
Status: Confirmed
CVE: CVE-2026-22217 (🔒)
GCVE (CVE): GCVE-0-2026-22217
GCVE (VulDB): GCVE-100-351477
Entry
Created: 03/18/2026 07:07Updated: 05/27/2026 02:25
Changes: 03/18/2026 07:07 (80), 03/22/2026 02:49 (12), 03/26/2026 04:18 (4), 05/27/2026 02:25 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.