- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 16
- 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]
- Partial safe harbor
- Some legal protection; read the terms.
- 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.
- Response
-
Within 3 days
After submission, the Checkmk security team will contact you within a few business days.
- Safe harbor
-
Partial
Not pursue any claims against reporting parties provided that:
- Hall of fame
-
Yes
We would like to give credit to the reporting parties. If you want your name/email/social media handle to be associated with the finding(s), please let us know .
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
16 assets you may test, 20 excluded.
Source code 4
- https://github.com/Checkmk/grafana-checkmk-datasource No bounty
- https://github.com/tribe29/checkmk No bounty
- https://github.com/tribe29/checkmk_kube_agent No bounty
- The Checkmk codebase
Domains 3
- checkmk.com
- the checkmk website and its subdomains No bounty
- tribe29.com
Web 2
- checkmk.com website and its subdomains
- tribe29.com website and its subdomains
Hardware and IoT 1
- The Checkmk appliance
Products and areas 6
- Checkmk appliance
- Checkmk codebase
- Checkmk Grafana datasource
- Checkmk K8s cluster collector
- The Checkmk Grafana datasource
- The Checkmk K8s cluster collector
Out of scope (20)
- Anything related to email spoofing, SPF, DMARC or DKIM
- Arbitrary file upload without proof of the existence of the uploaded file
- Best practices violations (password complexity, expiration, re-use, etc.), with low or no impact
- Blind SSRF without proven business impact (DNS pingback only is not sufficient)
- Clickjacking attacks with low or no impact
- Disclosed and/or misconfigured API keys without proven business impact
- (Distributed) Denial of service (DDoS) attacks against the aforementioned domains, machines running Checkmk, or the Checkmk appliances
- Email bombing
- HTTP Host headers manipulation without a proven business impact
- HTTP Request smuggling without any proven business impact
- Installation of malicious software on machines running Checkmk or on the Checkmk appliances
- Lack of HSTS enforcement for Checkmk web applications
- Missing Cookie flags without a PoC on how this can be exploited
- Missing security headers without a PoC on how this can be exploited
- Physical attacks against the Checkmk appliances
- Self-XSS that cannot be exploited against other users
- Side-channel attacks
- Social engineering attacks against Checkmk’s employees, partners, or customers (e.g., phishing, vishing, waterholing, typosquatting, homograph attacks, etc.)
- Verbose error and log messages that do not reveal personal data or secrets
- Weak SSL configurations and SSL/TLS scan reports
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Checkmk's policy. "We" in these lines means the program, not this site.
While testing
-
Avoid violating the privacy of others, disrupting our systems, or destroying data
-
Do not hold back any vulnerabilities you identified
-
Redact any sensitive information you would prefer is not stored by Checkmk before submitting your report
-
Stick to the scope outlined below
-
Do not engage in extortion
Not accepted
-
Self-XSS that cannot be exploited against other users
-
Lack of HSTS enforcement for Checkmk web applications
-
Missing Cookie flags without a PoC on how this can be exploited
-
Missing security headers without a PoC on how this can be exploited
-
HTTP Request smuggling without any proven business impact
-
Blind SSRF without proven business impact (DNS pingback only is not sufficient)
-
HTTP Host headers manipulation without a proven business impact
-
Disclosed and/or misconfigured API keys without proven business impact
-
Verbose error and log messages that do not reveal personal data or secrets
-
Clickjacking attacks with low or no impact
-
Weak SSL configurations and SSL/TLS scan reports
-
Arbitrary file upload without proof of the existence of the uploaded file
-
Best practices violations (password complexity, expiration, re-use, etc.), with low or no impact
-
Installation of malicious software on machines running Checkmk or on the Checkmk appliances
-
Physical attacks against the Checkmk appliances
-
Social engineering attacks against Checkmk’s employees, partners, or customers (e.g., phishing, vishing, waterholing, typosquatting, homograph attacks, etc.)
-
Anything related to email spoofing, SPF, DMARC or DKIM
-
Email bombing
-
Side-channel attacks
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.