- Top reward
- No cash rewards
- 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.
- 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 3 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.
- Pays cash
-
No
The reward offered varies (no cash though), depending on the seriousness of the security problem and the quality of the report.
- Response
-
Within 3 days
We respond within three working days to a report with an assessment of the report and an expected date for a solution.
- Safe harbor
-
Full
If you comply with the conditions above when reporting the observed vulnerability in one of our ICT systems, we will not attach any legal consequences to this report.
- Hall of fame
-
Yes
In mutual consultation, we can, if you desire, mention your name as the discoverer of the reported vulnerability.
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.
Products and areas 1
- ICT systems within our network
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Fuga's policy. "We" in these lines means the program, not this site.
While testing
-
Handle the knowledge on the security problem with care by not performing any acts other than those necessary to reveal the security problem.
-
Do not share the information on the security problem with others until the problem has been solved.
-
Do not utilize attacks on physical security, social engineering, distributed denial of service attacks, spam or third party applications.
-
Report the vulnerability as quickly as possible after its discovery.
-
Provide sufficient information to reproduce the problem so that we can solve the problem as quickly as possible.
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.