If you've found a security vulnerability in Zammad, please report the vulnerability exclusively via email to [email protected].

To send us a secure message, please use our public key.

We will get back to you as soon as possible and inform you about the next steps. Accepted vulnerabilities will be disclosed via patch level release with accompanying security advisory.

• Potential security issues can be reported via [email protected].
• We evaluate them and provide timely feedback to the reporter.
• There may be security releases created if needed, e.g. https://zammad.com/en/releases/6-3-1.
• We publish security advisories for every acknowledged issue, like https://zammad.com/en/advisories/zaa-2024-04.
• After their publication, we request CVE identifiers to be assigned to the advisories.

Every first reporter of a vulnerability may be credited in the related security advisory.

Zammad does not offer financial compensation through a security bounty program.

Most of our relevant GitLab related configuration related to Ruby security analysis can be seen in .gitlab/ci/lint.yml. With this, you can also locally reproduce the results.

We use renovate bot to keep our Ruby and JS dependencies up-to-date by automatic merge requests in our internal GitLab. This config is not visible in our source code, but you can see frequent commits from it in our history, like this one.

As you can see in the GitLab job linked above, we use bundle-audit to scan for known security issues in Ruby gems.

We use brakeman to scan for insecure Ruby code constructs, along with an ignore file that lists known exceptions.

We use the SonarJS plugin for ESLint for this.