Quick answers
- Is CVE-2026-16016 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-16016 being exploited in the wild.
- How severe is CVE-2026-16016?
- High severity, with a CVSS score of 7.3, published 17 July 2026.
- Which products and versions are affected?
- Poco-Ai Claw <= 0.5.4.
- Is there a fix for CVE-2026-16016?
- 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-16016 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-16016?
- Check whether you run Poco-Ai Claw 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 Server-Side Request Forgery (SSRF) vulnerability exists in the `run_task` function within `executor/app/api/v1/task.py`. The application accepts an untrusted `callback_url` via a POST request to `/v1/tasks/execute` and subsequently performs an HTTP POST to that destination using `CallbackClient` without validating the URL against an allowlist or blocking internal/loopback addresses. An unauthenticated remote attacker can exploit this to use the executor host as a proxy to scan internal networks, access cloud metadata services, or intercept callback data containing session metadata. As of the advisory date, the GitHub issue was closed due to inactivity without a formal patch.
Affected products
- poco-ai poco-claw <= 0.5.4
Timeline
- 2026-06-12: disclosed: GitHub issue #138 opened describing the SSRF vulnerability
- 2026-07-17: advisory: CVE-2026-16016 published via VulDB/NVD