# CVE-2026-16015: poco-ai poco-claw executor_manager API tasks.py create_task missing authentication

> Attackers can create tasks via the executor_manager API without authentication, potentially leading to unauthorized actions or code execution.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jul 2026
- **Updated:** 17 Jul 2026
- **Also known as:** GHSA-28fj-c9jc-xpp3

## What is CVE-2026-16015?

CVE-2026-16015 is a medium-severity missing authorization vulnerability in poco-ai poco-claw, published on 17 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was determined in poco-ai poco-claw up to 0.5.4. This vulnerability affects the function create_task of the file executor_manager/app/api/v1/tasks.py of the component executor_manager API. Executing a manipulation can lead to missing authentication. The exploit has been publicly disclosed and may be utilized. Upgrading to version 0.5.7 is able to resolve this issue. This patch is called 67fcc88505c57f77d3fcf04eb5b89425b10cbf48. It is recommended to upgrade the affected component.

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-16015?


## How do I fix CVE-2026-16015?

No fix has been published for CVE-2026-16015 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-16015 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-16015 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-16015 and fix it if it is affected.

What it is: CVE-2026-16015 is a medium-severity missing authorization vulnerability in poco-ai poco-claw, published on 17 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-16015 exists.

Affected product: poco-ai poco-claw. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-16015/ (Markdown: https://insights.sbomify.com/CVE-2026-16015/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-16015
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-16015
- OSV: https://osv.dev/vulnerability/CVE-2026-16015

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-16015/
Summaries are generated and may contain mistakes; the official description above is the record.