Severity by source
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Local-only attack requiring low-privilege write access to stage a symlink; read and write integrity impact confirmed but no availability impact described.
Primary rating from Vendor (VulDB).
CVSS VectorVendor: VulDB
Lifecycle Timeline
1DescriptionCVE.org
A vulnerability was detected in mosaxiv clawlet up to 0.2.10. This impacts the function read_file/write_file/edit_file of the file tools/fs_ops.go of the component File Tools. Performing a manipulation results in link following. The attack needs to be approached locally. The reported GitHub issue was closed with the label "not planned".
AnalysisAI
Link-following vulnerability in mosaxiv clawlet up to version 0.2.10 allows local low-privileged attackers to read, write, or modify files outside intended directories by supplying symlinks to the read_file, write_file, and edit_file functions in tools/fs_ops.go. All three file-operation primitives are affected, meaning the attack surface covers both read (information disclosure) and write/edit (integrity impact) paths. No patch is planned - the upstream GitHub issue was explicitly closed as 'not planned', leaving all deployments on affected versions permanently unpatched.
Technical ContextAI
clawlet is a small Go application authored by mosaxiv (CPE: cpe:2.3:a:mosaxiv:clawlet:*:*:*:*:*:*:*:*). The affected component is the file-operations module at tools/fs_ops.go, which implements read_file, write_file, and edit_file helpers. The root cause is CWE-59 (Improper Link Resolution Before File Access - Link Following): the functions resolve user-supplied paths without first checking whether intermediate path components or the final target are symbolic links pointing outside the intended working directory. An attacker who can place a crafted symlink in a location the tool processes can redirect file operations to arbitrary filesystem paths, potentially reading sensitive files or corrupting system or application files.
RemediationAI
No vendor-released patch has been identified at time of analysis, and the upstream GitHub issue was closed with the label 'not planned', indicating no official fix is forthcoming. Organizations using clawlet should consider replacing it with an alternative tool that correctly validates symlink targets, or forking the project to apply a fix that resolves symlinks (e.g., using filepath.EvalSymlinks in Go) before any file operation in fs_ops.go. As a compensating control, restrict the filesystem permissions of the directory tree that clawlet operates on so that unprivileged users cannot create symlinks within it (e.g., set the sticky bit, restrict directory write access). Additionally, run clawlet in a container or sandboxed environment with a read-only or volume-scoped filesystem mount to limit the reach of any symlink traversal. These controls reduce but do not eliminate the risk - a symlink already present in the target directory before the control is applied may still be exploitable.
Missing authorization in mosaxiv clawlet up to version 0.2.10 allows low-privileged remote attackers to list and remove
Server-side request forgery in mosaxiv clawlet up to version 0.2.10 enables authenticated remote attackers to manipulate
Same weakness CWE-59 – Improper Link Resolution Before File Access
View allSame technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-43598
GHSA-9hg3-m3p7-mjm6