- Top reward
- Not published
- 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.
- Pays cash
- Amounts are not published; ask before you invest time.
- Report by email
- [email protected]
- Publish after a fix
- Coordinate the timing with the company.
Rewards
What the company's own policy page says it pays.
The policy page has no reward table. Here is what it says, in its own words.
- Pays cash
-
Yes
Rewards are offered at our discretion based on how critical each vulnerability is.
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, 5 excluded.
Domains 1
- missiveapp.com
Products and areas 1
- our websites and apps
Out of scope (5)
- canny.io
- canny.io/security
- feedback.missiveapp.com
- status.missiveapp.com
- missiveapp.com (root domain)
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Missive's policy. "We" in these lines means the program, not this site.
While testing
-
We kindly ask that you not publicly disclose any information regarding vulnerabilities until we fix them.
-
To be considered valid, a submission must demonstrate real, exploitable impact on Missive's in-scope services.
-
Reports must demonstrate impact beyond what the reporter’s own privileges allow .
-
Every report must include one of the following: A working demonstration against your own test account
-
Include the email address(es) of the account(s) used during testing.
-
Reports that claim a protection is missing without verifying — if you report that the application doesn't do X, you must demonstrate that X is actually absent.
Not accepted
-
DMARC, SPF, and DKIM email policies on Missive domains
-
Unstripped EXIF metadata in uploaded images
-
Missing DNSSEC implementation
-
Password reset links not invalidated after new requests
-
Issues affecting feedback.missiveapp.com ; these should be reported to Canny.io
-
Issues affecting status.missiveapp.com ; these should be reported to PagerDuty
-
Issues affecting missiveapp.com (root domain); these should be reported to Webflow
-
Raw output from automated scanners without manual verification and demonstrated impact
-
Theoretical or speculative vulnerabilities without a working proof of concept
-
Informational findings such as version disclosure, missing security headers, or configuration suggestions that don't lead to a concrete exploit
-
Social engineering or phishing attacks against Missive employees
-
Denial-of-service (DoS/DDoS) attacks
-
Reports that do not include reproduction steps
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 12 Nov 2026. Last checked 2 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.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.