Satori CI Vulnerability Disclosure Policy

Last updated: 18 November 2026

Overview

Satori CI follows industry best practices in managing and responding to security vulnerabilities in its products and services. No vendor can guarantee that its software and services are entirely free of vulnerabilities, and Satori CI is no exception. What we can guarantee is a concerted effort at every stage of development to identify and mitigate them, and a clear, predictable process for handling the ones that others find.

Customers run their software and their tests on the Satori CI platform, so a weakness in our systems can affect theirs. This policy explains what is covered, how to report a vulnerability, what you can expect from us, and what we ask of you in return.

Scope

This policy applies to all currently offered products, software and services from Satori CI:

  • The Satori CI platform: the web application at satori.ci, its API, and the infrastructure that executes playbooks, monitors and scans and stores their reports.
  • Satori CI domains: satori.ci and the subdomains operated by Satori CI, including the documentation at docs.satori.ci.
  • The Satori CLI: the satori-ci package and its source at github.com/satorici/satori-cli.
  • The Satori CI GitHub App (github.com/apps/satorici) and its CI integration.
  • Other open-source projects published by Satori CI at github.com/satorici, such as the playbooks marketplace, the playbook validator, the MCP server and the Grafana and Claude plugins.

The policy does not cover systems that belong to our customers, content that users publish on the platform, or third-party services that we use. See Out-of-scope vulnerabilities.

Commitment

Satori CI appreciates and encourages the efforts of researchers who identify and report vulnerabilities in our products, software and services. When you follow this policy, we will, to the best of our abilities:

  • Respond to and verify your report within the timeframes set out below.
  • Keep you informed of our progress and collaborate with you transparently throughout the disclosure process.
  • Agree the disclosure date and the content of any advisory with you, and credit you if you wish.
  • Keep your report and your personal details confidential, and not share them with third parties without your consent.
  • Treat research carried out in good faith under this policy as authorised. We will not pursue or support legal action against you for it, and we will not treat it as a violation of our Acceptable Use Policy.

In return, we expect researchers to:

  • Not disclose a vulnerability before a 90-day period has passed or a mutually agreed date has been reached.
  • Carry out research within legal boundaries and in a way that does not cause harm, expose private data, or compromise the safety of Satori CI, its partners or its customers.
  • Test only with accounts, teams and repositories that you own or have explicit permission to use.
  • Not access, modify or delete data that belongs to other users. If you come across such data, stop, report it to us, and do not keep or share it.
  • Use only the minimum exploitation needed to demonstrate the issue.
  • Not perform denial-of-service testing, social engineering, phishing, spam or physical attacks against Satori CI, its staff or its customers.

Vulnerability management

Satori CI uses the same classification for vulnerabilities in third-party open-source components and for vulnerabilities specific to Satori CI. Vulnerabilities are scored with the Common Vulnerability Scoring System (CVSS) v4.0. Once a vulnerability has been assessed and is eligible for correction, it is prioritised as follows:

Severity CVSS v4.0 score How we resolve it
High / Critical 7.0 – 10.0 We aim to fix the vulnerability before its external disclosure, or no later than 4 weeks after it.
Low / Medium 0.1 – 6.9 These usually require privileged access or have limited impact on confidentiality, integrity or availability. We may resolve them as part of an upcoming scheduled release.

Resolving a vulnerability means either patching the software or mitigating the vulnerability by disabling the affected component or functionality.

For third-party open-source components, we may assess a vulnerability according to its relevance to how Satori CI uses the component. Lead times are usually longer, because we depend on external parties for information, patches and verification.

Supported versions. Fixes to the hosted platform are deployed for all customers and need no action on their part. For the Satori CLI and our other open-source software, fixes are provided in the latest release only, so users should upgrade to it.

Reporting vulnerabilities

If you identify a security vulnerability in a Satori CI product, software or service, please report it immediately. Timely reporting reduces the likelihood that a vulnerability is exploited in practice.

End users, partners, vendors, industry groups and independent researchers can report privately through either of these channels:

Please do not report vulnerabilities in public GitHub issues, on Discord or on social media. Vulnerabilities in open-source components that we use should be addressed directly to the project responsible for them.

Your report should include:

  • Your contact details.
  • The affected product, URL or version.
  • Technical information about the potential vulnerability.
  • Steps to reproduce it.
  • An estimated CVSS score and the resulting vector string (v4.0 or v3.1).
  • A remediation suggestion.
  • Your own vulnerability disclosure policy, if you have one.

We triage reports only when they include a working proof of concept that reproduces the issue and shows a clear, practical impact on Satori CI products or services. Automated scan results and tool-generated reports are not sufficient on their own. Please validate the issue manually and include the technical evidence that supports it.

You can expect the following response times from Satori CI:

  • A first response within 2 business days of receiving your report.
  • The result of our initial verification within 10 business days.

As a token of appreciation, researchers who contribute valid findings may receive public recognition in our security advisories. Satori CI does not currently run a paid bug bounty programme, and this policy does not entitle reporters to compensation.

Disclosing vulnerabilities

Once a reported finding has been investigated and confirmed as a legitimate vulnerability, Satori CI begins the coordinated disclosure process. We collaborate with the researcher on the details, such as the CVSS score and the content of the security advisory, and agree on the external disclosure date.

  • Where a vulnerability affects software that customers install, such as the Satori CLI, we request a CVE ID for it and publish a security advisory in the affected repository.
  • Vulnerabilities in the hosted platform are fixed on our side. We publish an advisory when customers were affected or need to take action, for example to rotate a token.

Public disclosure takes place after the fix has been released. If we cannot resolve a vulnerability within the 90-day period, we will tell you why and propose a new date.

Out-of-scope vulnerabilities

Some vulnerabilities are out of scope for this policy. Please do not submit reports on the following:

  • Command execution inside your own runs. Running arbitrary commands in the containers that Satori CI starts for your own playbooks is how the product works. Escaping a container, reaching another customer's runs or data, or accessing the underlying Satori CI infrastructure is in scope.
  • Vulnerabilities requiring high privileges or social engineering, such as attacks that need administrator access to the target account or team, or that need complex user interaction.
  • Attacks that require a compromised local machine, such as DLL hijacking, DLL sideloading or PATH manipulation affecting the Satori CLI.
  • User misconfigurations that could be prevented by following the Satori CI documentation, such as secrets committed to a public playbook or report.
  • Content created by users or third parties: playbooks, reports and repositories published by customers, and the software that those playbooks test.
  • Misuse of the platform by other users, which is handled under our Acceptable Use Policy.
  • Third-party services that we use, such as GitHub and Discord. Please report these to the provider.
  • Low-impact web issues: self-XSS, CSRF on logout or on actions with no security impact, and clickjacking on pages with no sensitive actions.
  • Any denial-of-service attack, including resource exhaustion through normal API usage with modified parameters, high-frequency API calls or slowloris attacks.
  • Third-party open-source vulnerabilities that are registered with a CVE ID in components or packages used by Satori CI, unless you can demonstrate an exploit against Satori CI.
  • Missing HTTP(S) security headers such as X-Frame-Options, missing cookie flags, and email authentication records, without a demonstrated exploit.
  • Reports generated by automated scanners without manual validation.
  • Unsupported software: releases of the Satori CLI or of our other open-source projects that are older than the latest one.
  • Reports that do not clearly document a real, exploitable issue with security impact, such as mismatched application-level errors and HTTP response codes found when fuzzing the API.