OpenTremor

Security

Report a vulnerability privately.

If you find a security problem in OpenTremor, email [email protected]. Do not open a public issue. We will work with you on a fix and when to disclose it.

Email [email protected]. Do not open a public issue.

Response times
Acknowledgement
3 business daysafter your report reaches us
First assessment
10 business daysto determine whether it is a vulnerability and how severe it is
Public disclosure
90 daysby default, or earlier once a fix ships. We agree on the date with you.
Business days in France. We do not pay bounties.

What to send

Enough for us to reproduce it.

Write in English or French.

  • The product surface or repository, and the release or commit you tested
  • The steps to reproduce it, or a proof of concept
  • What an attacker gains: data read, data changed, access to another organization
  • Whether you want credit in the advisory, and under which name

Scope

The code we ship and the service we run.

In scope
  • OpenTremor Cloud: app.opentremor.dev, api.opentremor.dev, mcp.opentremor.dev, docs.opentremor.dev and this site
  • The source code in every repository of the opentremor GitHub organization
  • The container images and the Helm chart we publish
Out of scope
  • Denial of service and load testing
  • Social engineering and physical attacks
  • Third-party services we depend on, such as GitHub, GitLab and LLM providers: report to them
  • Scanner output with no working impact, such as a missing header or a version banner

Testing rules

Test on your own data.

  • Use only accounts and organizations you created.
  • Do not read, change or delete another organization's data. If you reach it by accident, stop and tell us what you saw.
  • Do not degrade the service for others.
  • Keep the details private until we agree on a disclosure date.

What happens next

From report to advisory.

  1. 1We acknowledge your report and give you a contact for the rest of the exchange.
  2. 2We confirm the issue and rate its severity with CVSS.
  3. 3We fix it on every supported release and ship a patch release.
  4. 4We publish an advisory and credit you if you want.

Safe harbour

Good-faith research is welcome.

If you follow this policy, we consider your research authorized. We will not take legal action against you for it, and we will not ask anyone else to.

Supported versions

Security fixes for 12 months.

Security fixes go to every release published in the last 12 months.

Releases and Support

Found something?

Email us the details. We answer within 3 business days.