Skip to content

Blue Canvas

Vulnerability disclosure program on Self-hosted bluecanvas.io

Accepting reports Full safe harbor
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
6
Public CVEs
0
Last change
No changes yet

At a glance

What to know before you start testing.

No cash rewards
A disclosure program: you report for credit, not money.
Report by email
[email protected]
Full safe harbor
Good-faith research is authorised; no legal action.
Publish after a fix
Coordinate the timing with the company.

Rewards

What the company's own policy page says it pays.

This program does not pay cash rewards.

Pays cash
No Blue Canvas does not offer financial compensation.
Safe harbor
Full Blue Canvas will not sue you or ask law enforcement to investigate if you comply with these instructions.
Hall of fame
Yes Researchers who reported valid, unique issues will be listed on this page in our Hall of Fame.

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

6 assets you may test, 2 excluded.

Domains 3

  • bluecanvas.io
  • my.bluecanvas.io
  • tools.bluecanvas.io

Wildcard domains 2

  • *.bluecanvas.io No bounty
  • *.my.bluecanvas.io

Products and areas 1

  • Other publicly reachable endpoints on bluecanvas.io subdomains, if they have an A DNSRR
Out of scope (2)
  • status.bluecanvas.io
  • Any third-party hosted service on CNAME subdomains, e.g. status.bluecanvas.io (StatusPage)

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Blue Canvas's policy. "We" in these lines means the program, not this site.

While testing

  • Give us reasonable time to respond before making any information about the security issue public.
  • Do not access or modify user data without permission of the account owner.
  • Act in good faith not to degrade the performance of our services (including denial of service).
  • Report any vulnerability you’ve discovered promptly;
  • Avoid violating the privacy of others, disrupting our systems, destroying data, and/or harming user experience;
  • Use only the Official Channels to discuss vulnerability information with us;
  • Keep the details of any discovered vulnerabilities confidential until they are fixed, according to the Disclosure Policy;
  • Perform testing only on in-scope systems, and respect systems and activities which are out-of-scope;
  • You should only interact with test accounts you own or with explicit permission from the account holder; and

Not accepted

  • Disclosure of known public files or directories, e.g. robots.txt
  • SPF, DKIM, or DMARC configuration suggestions
  • Denial-of-service vulnerabilities
  • Login/logout CSRF

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 5 hours ago.

No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.

Public CVEs

Published vulnerabilities in this vendor's products, from the NVD.

Search NVD

No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.