Hyve5 Inc DBA Leantime
Vulnerability disclosure program on Self-hosted leantime.io
- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 3
- 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 through their form
- github.com/Leantime/leantime/security/advisories/new
- Full safe harbor
- Good-faith research is authorised; no legal action.
- Replies within 3 days
- As the policy promises.
- No public write-ups
- Keep findings private.
Rewards
What the company's own policy page says it pays.
This program does not pay cash rewards.
- Pays cash
-
No
Please refrain from requesting compensation for reporting vulnerabilities.
- Response
-
Within 3 days
We will respond to your report within 3 business days with our evaluation of the report and an expected resolution date.
- Safe harbor
-
Full
If you have followed the instructions above, we will not take any legal action against you in regard to the report.
- Hall of fame
-
Yes
The following people have responsibly disclosed vulnerabilities to us in the past:
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
3 assets you may test, 1 excluded.
Domains 2
- accounts.leantime.io
- leantime.io
Wildcard domains 1
- *.leantime.io
Out of scope (1)
- leantime.io
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Hyve5 Inc DBA Leantime's policy. "We" in these lines means the program, not this site.
While testing
-
Do not take advantage of the vulnerability you have discovered, for example by downloading more data than is necessary to demonstrate the vulnerability.
-
Do not read, modify or delete data that isn’t you own.
-
We ask that you do not to disclosure the problem to third parties until it has been resolved.
-
please do not try to test physical security or attempt phishing attacks against our employees, and so on.
-
please do not attempt to carry out DoS attacks, leverage black hat SEO techniques, spam people, and do other similarly questionable things.
-
We also discourage the use of any vulnerability testing tools that automatically generate significant volumes of traffic.
Not accepted
-
physical security
-
phishing attacks against our employees
-
DoS attacks
-
black hat SEO techniques
-
spam people
-
vulnerability testing tools that automatically generate significant volumes of traffic
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.