Reporting a security vulnerability
How to tell us about a vulnerability in Xolotl, what we do with it and when, and the protection you have when you report in good faith.
How to report
Write to security@xolotl.vet, in French, Dutch or English. Please do not post the issue publicly, and do not contact a practice that uses Xolotl about it.
The same address is published in /.well-known/security.txt on this website and on the Xolotl API, as RFC 9116 describes.
What to include
As much of this as you have:
- the product and version: the app and its platform, the API endpoint, the portal or the website page
- what the vulnerability is, and what an attacker could do with it
- the steps to reproduce it, or a proof of concept
- whether you believe it is already being exploited, and why
- how you would like to be credited, if at all
What we do, and when
| When | What |
|---|---|
| 3 working days | We acknowledge your report and give you a named person to talk to. |
| 10 working days | We tell you whether we confirm it, how severe we think it is, and our plan. |
| Until it is fixed | We keep you informed at least every two weeks. |
| Fix released | We tell you before the advisory is published, and credit you if you wish. |
We aim to fix critical and high-severity issues within 30 days and the others within 90 days.
Disclosure
Once a fix is available we publish what was affected, how severe it was and what users should do, on a date we agree with you.
If a vulnerability is being actively exploited, the EU Cyber Resilience Act (Regulation (EU) 2024/2847, art. 14) requires us to notify the Centre for Cybersecurity Belgium and ENISA within 24 hours and to inform the users affected, so we may have to act before the date we would otherwise agree.
Safe harbour
We will not take legal action against you, or ask anyone else to, for research that follows this policy in good faith. That means:
- you test only what is in scope below, and only as far as needed to show the vulnerability
- you do not access, change, copy or delete data that is not yours beyond the minimum needed to prove the issue, and you stop as soon as you reach real data
- you do not degrade the service: no denial of service, spam, social engineering or physical attacks on our staff or on the practices
- you give us reasonable time to fix the issue before any disclosure
Reporting to the CCB instead
You can also report to the Centre for Cybersecurity Belgium (CCB), Belgium's national CSIRT. Articles 22 and 23 of the Belgian law of 26 April 2024 (the NIS2 law) protect researchers who report through the CCB and meet its conditions: notably a first notice to the CCB and to us within 24 hours of the discovery and a full report within 72 hours, testing kept proportionate, and no publication without the CCB's agreement.
This policy cannot authorise testing of systems we do not own, such as a practice's own network and devices or a third-party service, and cannot waive anyone else's rights.
Scope
In scope:
- the Xolotl practice software in every form we distribute it: web, desktop and native apps
- the Xolotl API and the services behind it
- the client portal that practices offer their clients
- this website, www.xolotl.vet
Out of scope
Vulnerabilities in third-party services we use (please report those to their owner), volumetric denial of service, self-XSS, and missing headers or best-practice remarks with no demonstrable impact.