> For the complete documentation index, see [llms.txt](https://docs.tomorrowx.com/cap/vZHo2144m1e79o3WX0RU/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tomorrowx.com/cap/vZHo2144m1e79o3WX0RU/legal/security-vulnerability-reporting.md).

# Security Vulnerability Reporting

How to report a security vulnerability in TomorrowX products, what to include, and what to expect after you report.

TomorrowX welcomes reports of suspected security vulnerabilities in any TomorrowX product or service, including the Composable Agentic Platform (CAP), its Console, extensions, and published cloud images.

## How to report

Email **<notices@tomorrowx.com>** with:

* A description of the issue and where you found it (product, version or build number, deployment channel).
* Steps to reproduce, proof-of-concept code, or captured requests and responses where applicable.
* Any assessment of impact you have made.

Please do not disclose the issue publicly before we have had a reasonable opportunity to investigate and remediate.

## What to expect

* We acknowledge reports within 5 business days.
* We investigate all reports and keep you informed of progress and outcome.
* Fixes for confirmed vulnerabilities are delivered through our standard release channels: Console update packages, extension updates, and refreshed cloud marketplace images.
* We will credit reporters who wish to be credited when a fix is published.

## Scope notes

* This page covers TomorrowX products. For issues concerning the TomorrowX website, and for our responsible disclosure conduct guidelines, see [Security and Responsible Disclosure](https://tomorrowx.com/legal-security) on tomorrowx.com.
* Reports concerning third-party open source components we ship are in scope; we coordinate with upstream projects where appropriate. Component inventory is available in the SBOM shipped with each Console distribution.
* This process covers good-faith security research. It is not a bug bounty programme and no monetary reward is implied.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.tomorrowx.com/cap/vZHo2144m1e79o3WX0RU/legal/security-vulnerability-reporting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
