# CVE-2026-19019: poco-ai poco-agent Claude File workspace.py WorkspaceManager._setup_session_persistence cleanup

> Incomplete session cleanup in poco-agent allows potential data leakage or state persistence issues, requiring complex remote exploitation.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Aug 2026
- **Updated:** 6 Aug 2026
- **Also known as:** GHSA-j255-r942-27q8

## What is CVE-2026-19019?

CVE-2026-19019 is a medium-severity vulnerability in poco-ai poco-agent, published on 6 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A security flaw has been discovered in poco-ai poco-agent up to 0.5.4. Affected is the function WorkspaceManager._setup_session_persistence of the file executor/app/core/workspace.py of the component Claude File Handler. The manipulation results in incomplete cleanup. The attack may be performed from remote. Attacks of this nature are highly complex. The exploitability is told to be difficult. The exploit has been released to the public and may be used for attacks.

Weakness: CWE-459 (Incomplete Cleanup)

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


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

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

## Is CVE-2026-19019 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19019 is a medium-severity vulnerability in poco-ai poco-agent, published on 6 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19019 exists.

Affected product: poco-ai poco-agent. 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-19019/ (Markdown: https://insights.sbomify.com/CVE-2026-19019/index.md)
```

## Sources

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

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