Authenticated arbitrary file write via sessionFile path
Published Mar 5, 2026 · Updated Mar 5, 2026
Arbitrary file write in OpenClaw before 2026.2.12 allows remote authenticated users to append transcript data outside the sessions directory. The gateway trusts the sessionFile value while resolving a session transcript and writes JSONL records without checking that the resolved path remains under the configured sessions directory. Gateway credentials are required; writable files are limited by the service account's filesystem permissions, but repeated appends can corrupt configuration or interrupt service.
Summary
What happened
Arbitrary file write in OpenClaw before 2026.2.12 allows remote authenticated users to append transcript data outside the sessions directory. The gateway trusts the sessionFile value while resolving a session transcript and writes JSONL records without checking that the resolved path remains under the configured sessions directory. Gateway credentials are required; writable files are limited by the service account's filesystem permissions, but repeated appends can corrupt configuration or interrupt service.
The record
- CVE
- CVE-2026-28459
- Published
- Mar 5, 2026
- Updated
- Mar 5, 2026
- Vendor
- OpenClaw Foundation
- Product
- OpenClaw
- Classifications
- CWE-23, CWE-73, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 5, 2026CVE publishedPublication date reported by the CVE source.
- Mar 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2026.2.12
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo