Security
Last updated 16 November 2026
Busrider is published by A2DEV, in France. This page says how to report a vulnerability, what happens then, and how security fixes reach you.
In short
- Report a vulnerability to [email protected], never in a public issue.
- We acknowledge it within 3 working days.
- Fixes come as Microsoft Store updates. For a security reason, Busrider can require the update.
Report a vulnerability
Write to [email protected], in English or French. Please don't open a public issue, and don't post about it before a fix is out.
Say what you can of:
- the version (Settings › About) and where you installed it from (the Microsoft Store);
- what an attacker needs (local access, a message on a broker, a network position…) and what they get;
- the steps to reproduce it, or a proof of concept.
Never send real connection strings, passwords, sign-in tokens or message contents: a test namespace or a local broker is enough.
What happens next
| Step | When |
|---|---|
| Acknowledgement | Within 3 working days |
| First assessment: confirmed or not, severity (CVSS 4.0) | Within 10 working days |
| Fix released | Critical: as fast as possible, 7 days as a target. High: 30 days. Medium and low: the next release, 90 days at most |
| Public advisory | Once the fix is out, with credit to you if you want it |
Coordinated disclosure
We follow coordinated disclosure: 90 days from the report by default, sooner once the fix is out, later only by agreement. Research done in good faith, on your own data and test brokers, without harming others or their data, will not be pursued.
Scope
- In scope: the Busrider desktop app, with the relay AI assistants start (busrider-mcp) and the emulator of its local brokers; the Busrider service it calls (feedback, ratings, updates); and the busrider.app website.
- Out of scope: the message brokers and Azure services themselves (such as Azure Service Bus, Azure Storage or Microsoft Entra ID), the AI assistants, and attacks that already need full control of the user's Windows account.
What Busrider opens on your computer
- Signing in with Microsoft Entra ID: Microsoft's page opens in your browser (authorization code with PKCE), and Busrider waits for the answer on 127.0.0.1, on a port the system picks, accepting only the answer to its own request. It stops listening once you are signed in, on Cancel, or after 5 minutes. The tokens are kept encrypted with Windows' keystore, never in clear on disk.
- Local brokers: each one listens on 127.0.0.1, on its own port (from 5680; with TLS on, 10,000 above it), unless its settings open it to Docker containers and other computers, which makes Windows ask to let it through the firewall. Its root key is a public development key, and its data is kept unencrypted in its folder: open one to your network only if you trust it.
- AI assistants, when you turn them on: a named pipe for their relay, which must first give a key Busrider writes at each start to a file only your Windows account can read.
How fixes reach you
Updates come from the Microsoft Store, which installs them by itself. Security updates are free, and are released apart from new features where possible. They come in the latest version: with an older version, update to it.
When a version must no longer be used, for instance because of a security flaw, Busrider says so itself: first a banner, then, from a given date, a screen that asks for the update before anything else and leads to the Microsoft Store. Saved connections and settings are kept, and nothing running is stopped.
If a flaw is exploited
Users are told, with what they can do meanwhile. A personal data breach is notified to the CNIL within 72 hours, and to the people concerned when the risk to them is high.
Components and dependencies
- Every version has a bill of materials (a CycloneDX SBOM): the packages Busrider is built from, and Electron with its Chromium and Node. It is kept for every version.
- Dependabot proposes dependency updates every week. New versions wait 7 days before they are proposed; security updates don't wait.
- Electron stays on a version that still receives Chromium's security fixes.
- Before every release, the packages the app is built from are checked for known vulnerabilities.
Contact
Vulnerabilities: [email protected] (also in security.txt). Personal data: see the privacy policy. Anything else: Support.