Vulnerability disclosure

Report it

Email security@devbyte.ai. If you can, include what you did, what happened, and what you expected — a reproduction beats a scanner report. Please do not open a public issue first.

We will acknowledge a report and tell you what we are doing about it. We will credit you if you want the credit and not if you do not.

In scope

• The application and its API.
• The control plane and the MCP server.
• The per-Task Session confinement: an escape from a pod, a route to the internet from inside a Session, or a way to reach another organisation's data.
• Anything that lets a repository change what the platform is permitted to do — for example, a tracked file that widens an agent's permissions. Factory configuration is deliberately held in the platform rather than in a repository, so a way around that is a finding.
• Anything that lets Untrusted Content act as instruction rather than as data.

Out of scope

• Reports from an automated scanner with no demonstrated impact.
• Denial of service by volume.
• Findings in a third party listed on the subprocessors page — report those to them, and tell us so we can follow it.
• Social engineering of our people or our customers.

What we ask

Give us a reasonable period to fix an issue before publishing it, do not access data that is not yours, and stop as soon as you have demonstrated the problem.

What is still missing

A written safe-harbour commitment — the clause that tells a researcher they will not be pursued for testing within this policy — is the part that needs counsel, and it is not drafted. Until it is, we will say what we can say plainly: we have never pursued anyone for a good-faith report, and we will tell you before this page changes.

Enterprise · Legal