CVE-2026-28484
Option Injection in OpenClaw Git Pre-Commit Hook Exposes Ignored Files
Publication date: 2026-03-05
Last updated on: 2026-03-06
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| openclaw | openclaw | to 2026.2.15 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-77 | The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
OpenClaw versions prior to 2026.2.15 have an option injection vulnerability in the git-hooks/pre-commit hook. This vulnerability allows attackers to stage files that are normally ignored by creating maliciously-named files that begin with dashes. Because the pre-commit hook does not use a -- separator when passing filenames through xargs to the git add command, attackers can inject git flags and add sensitive ignored files, such as .env files, into the git history.
How can this vulnerability impact me? :
This vulnerability can lead to the unintended inclusion of sensitive files in the git repository history. Attackers can exploit it to add ignored files containing sensitive information, such as environment variables or credentials, to the git history. This can result in exposure of confidential data, potentially leading to security breaches, data leaks, and unauthorized access.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know