- 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 through their form
- github.com/coder/coder/security/advisories/new
- Full safe harbor
- Good-faith research is authorised; no legal action.
- 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
We offer bounties at our discretion based on the relevance, impact, and severity of the issue.
- Safe harbor
-
Full
Authorized concerning any applicable anti-hacking laws, and we will not initiate or support legal action against you for accidental, good-faith violations of this policy;
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, 2 excluded.
Products and areas 1
- any digital assets owned, operated, or maintained by Coder
Out of scope (2)
- Assets or other equipment not owned by parties participating in this policy.
- https://github.com/coder/coder/security/advisories/new
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Coder's policy. "We" in these lines means the program, not this site.
While testing
-
Play by the rules, including following this policy and any other relevant agreements.
-
Report any vulnerability you've discovered promptly;
-
Avoid violating the privacy of others, disrupting our systems, destroying data, and/or harming user experience;
-
Use only the Official Channels to discuss vulnerability information with us;
-
Provide us a reasonable amount of time (at least 90 days from the initial report) to resolve the issue before you disclose it publicly;
-
Perform testing only on in-scope systems, and respect systems and activities which are out-of-scope;
-
Limit the amount of data you access to the minimum required for effectively demonstrating a Proof of Concept;
-
You should only interact with test accounts you own or with explicit permission from the account holder; and
-
Do not engage in extortion.
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.