Skip to content

Digital Asset

Vulnerability disclosure program on Self-hosted digitalasset.com

Accepting reports Full safe harbor
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
9
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.
Replies within 1 day
As the policy promises.
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 We do not offer a bug bounty program and compensation requests will not be considered in compliance with this Responsible Disclosure Policy.
Response
Within 1 days We will investigate any details you provide and respond as soon as possible, usually one business day.
Safe harbor
Full We won’t take legal action against those who discover and report security vulnerabilities in accordance with this Responsible Disclosure Policy.
Hall of fame
Yes To acknowledge the first person who alerts us to previously unknown vulnerabilities, we will show our gratitude by placing their name in the Acknowledgements list below.

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

Scope

9 assets you may test, 8 excluded.

Source code 5

  • Canton Ledger
  • Daml
  • https://github.com/canton-network/splice No bounty
  • https://github.com/digital-asset/canton No bounty
  • https://github.com/digital-asset/daml No bounty

Domains 1

  • digitalasset.com

Products and areas 3

  • Canton Network and Splice
  • Other Digital Asset Products and Services
  • our website or products
Out of scope (8)
  • EXIF and Geolocation related vulnerabilities
  • Logout Cross-Site Request Forgery
  • Missing DMARC, SPF, DANE and CAA records
  • Missing HTTP security headers or issues related to HTTP headers
  • OAuth Misconfiguration
  • Reports of insecure SSL/TLS ciphers (unless accompanied with working proof of concept)
  • Username/E-mail enumeration
  • Vulnerabilities in Third party SaaS applications and integrations we use

Rules

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

While testing

  • Don’t disclose a bug or vulnerability on public notice boards, mailing lists, or other public forums, prior to Responsible Disclosure and an appropriate opportunity for it to be fixed.
  • Do not utilize an exploit to view data without authorization, or compromise the confidentiality or availability.
  • Do not perform an attack that would impact the reliability/availability of services. DDoS/Spam attacks are not allowed.
  • Don’t use scanners or automated tools to find vulnerabilities. They can have unintended consequences or impact.
  • Never attempt non-technical attacks, such as social engineering, phishing, or physical attacks against our employees or infrastructure.
  • Do not ask for compensation from an affected firm or through any “marketplace” for vulnerabilities.
  • When submitting a vulnerability report, you must now declare whether any AI tools (LLMs, AI assistants, copilots, or automated agents) were used to discover, reproduce, or develop the exploit.
  • Scanning Digital Asset infrastructure or products using automated vulnerability scanners without human verification and contextualisation

Not accepted

  • Vulnerabilities in Third party SaaS applications and integrations we use
  • Username/E-mail enumeration
  • Missing HTTP security headers or issues related to HTTP headers
  • Missing DMARC, SPF, DANE and CAA records
  • OAuth Misconfiguration
  • Logout Cross-Site Request Forgery
  • EXIF and Geolocation related vulnerabilities
  • Reports of insecure SSL/TLS ciphers (unless accompanied with working proof of concept)

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.