- Top reward
- No cash rewards
- Top severity paid
- Critical
- Assets in scope
- 6
- Public CVEs
- 0
- Last change
At a glance
What to know before you start testing.
- No cash rewards
- A disclosure program: you report for credit, not money.
- Report on HackerOne
- Submit through the program page.
Rewards
What HackerOne lists as the payout for each severity.
This program does not pay cash rewards.
Scope
6 assets you may test, 1 excluded.
Source code 5
- https://github.com/WeblateOrg/docker Critical No bounty
- https://github.com/WeblateOrg/translation-finder Critical No bounty
- https://github.com/WeblateOrg/weblate Critical No bounty
- https://github.com/WeblateOrg/website Critical No bounty
- https://github.com/WeblateOrg/wlc Critical No bounty
Web 1
- hosted.weblate.org Critical No bounty
Out of scope (1)
- hg.weblate.org
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Weblate (via HackerOne)'s policy. "We" in these lines means the program, not this site.
While testing
-
Report high- and critical-severity vulnerabilities privately through this program.
-
Report low and medium severity issues publicly in the affected repository's GitHub issue tracker.
-
If unsure of severity, you may start privately.
-
Follow our security research and testing rules:
-
Follow our guidance on disclosure of AI use and independent verification:
Summarised with AI from the program policy on HackerOne, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 30 minutes ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Before we tracked it
Scope and reward changes recorded before this page started tracking it.
-
Scope removed
github.com (out of scope)
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.
Original policy
Copied from hackerone.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
Reporting security issues
Report high- and critical-severity vulnerabilities privately through this program. Report low and medium severity issues publicly in the affected repository's GitHub issue tracker. If unsure of severity, you may start privately.
Our reporting and disclosure policy: https://docs.weblate.org/en/latest/security/issues.html
Scope and testing
Eligible assets and asset-specific instructions are listed in the Scope tab.
Follow our security research and testing rules: https://docs.weblate.org/en/latest/security/issues.html#security-research
For security properties, assumptions, and known non-findings, consult the threat model for the affected release: https://docs.weblate.org/en/latest/security/threat-model.html
AI-assisted reports
Follow our guidance on disclosure of AI use and independent verification: https://docs.weblate.org/en/latest/contributing/issues.html#ai-issues