CVE-2026-16017 in clawlet
Summary
by MITRE • 07/17/2026
A security flaw has been discovered in mosaxiv clawlet up to 0.2.10. Impacted is the function list/remove of the file tools/tool_cron.go of the component cron Chat Tool. The manipulation results in missing authorization. The attack may be performed from remote. The exploit has been released to the public and may be used for attacks. The reported GitHub issue was closed with the label "not planned".
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Analysis
by VulDB Data Team • 07/17/2026
The security vulnerability identified in mosaxiv clawlet version 0.2.10 represents a critical authorization bypass flaw within the cron Chat Tool component. This vulnerability specifically affects the list/remove function located in tools/tool_cron.go file, creating a significant exposure that allows unauthorized users to manipulate scheduled tasks without proper authentication credentials. The flaw exists at the core operational level of the application's task management system, where the absence of proper access controls enables malicious actors to execute arbitrary commands through the cron functionality.
The technical implementation of this vulnerability stems from insufficient input validation and authorization checks within the cron tool's remove function. When users attempt to perform list or remove operations on scheduled tasks, the application fails to verify whether the requesting user possesses adequate privileges to execute these actions. This missing authorization mechanism creates a path for remote exploitation where attackers can leverage the exposed interface to modify or delete cron jobs without proper authentication. The vulnerability operates at the application layer and does not require local system access, making it particularly dangerous as it can be exploited from external networks.
The operational impact of this vulnerability extends beyond simple unauthorized access, as it enables potential attackers to manipulate the execution schedule of automated tasks within the system. This could lead to service disruption through deletion of critical scheduled operations, or more maliciously through modification of task parameters to execute harmful commands. The public availability of exploit code significantly amplifies the risk, as it eliminates the need for advanced technical skills to leverage this vulnerability. Attackers can readily deploy these exploits against vulnerable installations without requiring specialized knowledge of the underlying system architecture.
Organizations running affected versions of mosaxiv clawlet face substantial risk exposure from this authorization bypass vulnerability. The combination of remote exploitability and public availability of attack vectors creates an immediate threat landscape where systems can be compromised without extensive reconnaissance or advanced attack techniques. The vulnerability's classification aligns with CWE-285, which addresses improper authorization in software systems, and maps to ATT&CK technique T1078 for valid accounts and T1490 for data destruction through task manipulation. Given that the GitHub issue was closed with "not planned" label, it indicates a lack of official remediation efforts from the maintainers, leaving affected users without official support for addressing this security gap.
The recommended mitigation strategy involves immediate implementation of network-level restrictions and access controls to limit exposure of the vulnerable cron functionality. Organizations should consider applying manual code patches that enforce proper authorization checks before allowing execution of list or remove operations on cron tasks. Additionally, network segmentation and firewall rules should be implemented to restrict access to the affected component from untrusted networks. Regular security monitoring and log analysis should be enhanced to detect potential exploitation attempts through unusual cron job modifications or unauthorized access patterns. The lack of official patch support necessitates proactive defensive measures including code review processes to identify similar authorization gaps in other system components and implementation of additional authentication layers where possible.