- Top reward
- Not published
- Top severity paid
- Not published
- Assets in scope
- 1
- 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]
- 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.
The policy page has no reward table. Here is what it says, in its own words.
- Pays cash
-
Yes
In certain circumstances, Zoom may grant monetary rewards/bounties to the security researcher who submitted the report.
- Response
-
Within 1 days
We will acknowledge receipt of your report within 1 business day.
- Safe harbor
-
Full
Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
1 asset you may test, 1 excluded.
Products and areas 1
- Zoom’s products, services, and systems
Out of scope (1)
- vendor systems
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Zoom's policy. "We" in these lines means the program, not this site.
While testing
-
Notify us as soon as you discover a potential security vulnerability.
-
Only use or access accounts and information that belong to you.
-
Do not destroy or modify data that is not yours.
-
Do not degrade the performance of Zoom products and services or our users.
-
Do not perform social engineering, physical, or denial of service attacks on Zoom personnel, locations, or assets.
-
Follow HackerOne’s disclosure guidelines , this Vulnerability Disclosure Policy, and all applicable laws.
Not accepted
-
Attacks requiring MITM or physical access to a user's device.
-
Previously known vulnerable libraries without a working Proof of Concept.
-
Clickjacking on pages with no sensitive actions.
-
Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions.
-
Comma Separated Values (CSV) injection without demonstrating a vulnerability.
-
Missing best practices in SSL/TLS configuration.
-
Any activity that could lead to the disruption of our service (DoS).
-
Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS.
-
Rate limiting or bruteforce issues on non-authentication endpoints.
-
Missing best practices in Content Security Policy.
-
Missing HttpOnly or Secure flags on cookies.
-
Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.).
-
Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]
-
Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).
-
Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis.
-
Tabnabbing.
-
Open redirect - unless an additional security impact can be demonstrated.
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.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.