Skip to content

Mailstrom

By 410 Labs Vulnerability disclosure program on Self-hosted mailstrom.co

Accepting reports Full safe harbor
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
2
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 2 days
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.

Response
Within 2 days A timely response to your email (within 2 business days).
Safe harbor
Full 410 Labs Corp will not engage in legal action against individuals who submit vulnerability reports through our Vulnerability Reporting Form.
Hall of fame
Yes Researchers who submit a vulnerability report to us will be given full credit on our website once the submission has been accepted and validated by our product security team.

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

Scope

2 assets you may test.

Domains 1

  • mailstrom.co

Products and areas 1

  • mailstrom

Rules

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

While testing

  • Engage in testing of systems/research without harming 410 Labs or its customers.
  • Engage in vulnerability testing within the scope of our vulnerability disclosure program.
  • Test on products without affecting customers, or receive permission/consent from customers before engaging in vulnerability testing against their devices/software, etc.
  • Adhere to the laws of their location and the location of 410 Labs.
  • Refrain from disclosing vulnerability details to the public before a mutually agreed-upon timeframe expires.
  • Please include how you found the bug, the impact, and any potential remediation.
  • Please include any plans or intentions for public disclosure.

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.