Responsible disclosure

How to report a security vulnerability in VeloPhex and what happens after you do.

If you believe you have found a security vulnerability in VeloPhex, please tell us privately so we can fix it before it can be used against our customers. We appreciate the work of everyone who reports issues responsibly.

How to report#

Email security@velophex.com. Please do not report vulnerabilities through the community forum, public issue trackers, social media or general support channels.

If you need to send sensitive material such as a working exploit, say so in your first message and we will agree a secure way to transfer it.

What to include#

A good report lets us reproduce the problem quickly. Include as much of this as you can:

  1. The affected component and version: Studio, Robot, Orchestrator, an activity package, the Python SDK or the documentation site, and the version you tested (for example the Orchestrator image tag or velophex --version).
  2. The deployment shape: on-premises Compose stack, or which environment you were using.
  3. A description of the issue and the impact you believe it has, for example cross-tenant data access, privilege escalation, secret disclosure, or code execution on a Robot.
  4. Steps to reproduce, including requests, payloads, configuration and any non-default settings.
  5. Evidence: logs, screenshots or a proof of concept. Remove any real personal data or other organizations' data.
  6. Correlation ids from API responses (X-Correlation-ID), if you have them. They help us find the exact request.
  7. How to reach you, and whether you would like to be credited.

Scope#

In scope:

  • VeloPhex Studio
  • The VeloPhex Robot, including the Assistant, the User Host and the Browser Host
  • The VeloPhex Orchestrator, its web app and its APIs (REST, Runtime, Robot, package feed and webhooks)
  • VeloPhex activity packages
  • The VeloPhex Python SDK
  • The documentation site (docs.velophex.com)

Out of scope:

  • Findings that need physical access to a machine or an already compromised administrator account.
  • Denial of service through volume alone, social engineering, and spam.
  • Reports from automated scanners with no demonstrated impact.
  • Vulnerabilities in third-party software, unless VeloPhex's use of it makes them exploitable. Please report those to the vendor as well.
  • Your own deployment's configuration choices, for example a weak password you set.

Testing guidelines#

When you research a vulnerability:

  • Test only against systems you own or are authorized to test. For a hosted environment, use only your own tenant.
  • Do not access, modify or delete other people's data. If you encounter it, stop and include only what is needed to show the issue.
  • Do not degrade service for other users.
  • Give us reasonable time to fix the issue before you disclose it publicly.

What to expect#

After you report:

  1. We acknowledge your report.
  2. We investigate, reproduce the issue and assess its severity. We may ask you questions.
  3. We develop and test a fix, and ship it in a release. Where customers need to act, for example by upgrading or rotating a key, we say so in the release notes.
  4. We keep you informed of progress and agree with you on the timing of any public disclosure.

We will not pursue action against researchers who act in good faith and follow these guidelines.

For customers#

If you suspect an active incident in your own deployment rather than a product vulnerability:

Next steps#

How to report

What to include

Scope

Testing guidelines

What to expect

For customers

Next steps