Quick answers
- Is CVE-2026-16017 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-16017 being exploited in the wild.
- How severe is CVE-2026-16017?
- Medium severity, with a CVSS score of 6.3, published 17 July 2026.
- Which products and versions are affected?
- Mosaxiv Clawlet up to 0.2.10.
- Is there a fix for CVE-2026-16017?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-16017 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-16017?
- Check whether you run Mosaxiv Clawlet at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A missing authorization vulnerability exists in the `list` and `remove` functions within `tools/tool_cron.go` of mosaxiv clawlet. While the application correctly records ownership metadata (channel and chat ID) when a cron job is created, it fails to validate these ownership fields during management operations. An authenticated attacker can remotely invoke the `list` command to enumerate all scheduled jobs in the shared store and subsequently use the `remove` command with a leaked job ID to delete tasks belonging to other users. The issue is present in version 0.2.10 and earlier; as of the advisory date, the maintainer has labeled the issue as 'not planned' for fixing.
Affected products
- mosaxiv clawlet up to 0.2.10
Timeline
- 2026-07-17: advisory: NVD and VulDB published the vulnerability details.
- 2026-07-17: disclosed: Public exploit details and PoC released.