Security
This page explains how to report a security problem in Open Canvas, what the maintainer will do with your report, and how the editor limits what it exposes on your machine.
Report a vulnerability
Use the private vulnerability report form on GitHub. It sends your report to the maintainer without making it public. Please do not open a public issue for a vulnerability.
For hardening ideas that are not sensitive, a public issue is fine.
What to include
- The Open Canvas version, taken from the changelog or from your release tag.
- Your operating system.
- Steps to reproduce the problem.
- The impact you believe it has.
- A proof of concept, if you have one.
Use synthetic content in your report, not private artwork or real project files.
What happens next
The maintainer acknowledges the report, investigates it, and works on a fix. Fixes ship in a new release and are noted in the changelog. If you want credit for the report, say so and it will be given. There is no paid bug bounty, and no response time is promised.
Supported versions
Fixes go into the latest release. To get them, run open-canvas update; the update guide describes the steps. You can also see published versions on the releases page.
Scope
In scope:
- The editor.
- The local workspace service and the MCP broker.
- The installer scripts,
/install.shand/install.ps1. - Release archives and their checksums.
- This website.
Out of scope:
- Issues in third party MCP clients or model providers.
- Attacks that need an already compromised machine or a malicious trusted local process.
- Social engineering.
- Volumetric denial of service against the website.
How Open Canvas limits exposure
- The editor and the MCP broker bind to loopback addresses on your machine. The broker is not an unauthenticated network API.
- Workspace data is stored locally under
~/.open-canvas/data/. - An MCP client runs as a local process and can act with your access to Open Canvas. Connect only clients you trust. This is why a malicious local process is out of scope.
- Choose File → Pause agent access to stop MCP access to the selected workspace and its canvas.
- The updater downloads the matching archive, verifies its checksum and version, and switches the launcher only after verification.
See Sessions, security and limits and the MCP guide for details. For what the website itself collects, read the privacy policy.
Good faith research
Please test only against your own installation and your own data, avoid accessing or changing anything that belongs to other people, and give the maintainer a reasonable chance to fix the problem before you disclose it publicly. Research done in good faith under these terms is welcome.