# PYSEC-2026-4009: Path traversal and arbitrary directory deletion/overwrite via agent profile import in local-operator


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 5 Sep 2026
- **Also known as:** GHSA-22mg-8gw7-636x

## What is PYSEC-2026-4009?

PYSEC-2026-4009 is a vulnerability in local-operator, published on 5 Sep 2026. 

### Official description

The `/v1/agents/import` endpoint and `AgentRegistry.import_agent()` in local-operator versions before 0.47.5 trust the `id` field inside `agent.yml` of an uploaded agent profile archive when constructing the destination directory. A crafted `id` containing directory traversal sequences makes `shutil.rmtree` and `shutil.copy2` operate outside the agent registry, allowing an unauthenticated client with network access to the API to recursively delete arbitrary directories and write files with the privileges of the server process. Even without traversal, an imported archive could overwrite or delete existing local agent profiles.

Version 0.47.5 assigns a fresh server-generated identifier to every imported profile, never derives a filesystem path from archive metadata, creates destination directories exclusively, and binds `lop serve` to 127.0.0.1 by default.

## Which versions are affected by PYSEC-2026-4009?

1 open source package ship an affected version, including local-operator.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `local-operator` | PyPI | All versions | 0.47.5 |

## How do I fix PYSEC-2026-4009?

Upgrade local-operator to 0.47.5 or later.

## Is PYSEC-2026-4009 being exploited?

There is no known exploitation of PYSEC-2026-4009 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for PYSEC-2026-4009 and fix it if it is affected.

What it is: PYSEC-2026-4009 is a vulnerability in local-operator, published on 5 Sep 2026. 
Exploitation: There is no known exploitation of PYSEC-2026-4009 in the wild and no public exploit code.

Affected packages and fixed versions:
- local-operator (PyPI): affected all versions; fixed in 0.47.5

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/PYSEC-2026-4009/ (Markdown: https://insights.sbomify.com/PYSEC-2026-4009/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/PYSEC-2026-4009

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