AgentMBX is alpha software. Security reports are welcome and are handled privately.
Report vulnerabilities privately through GitHub's private vulnerability reporting:
- Open the repository's Security tab: https://github.com/kryptobaseddev/agentmbx/security.
- Choose Report a vulnerability and fill in the advisory form.
This works only while private vulnerability reporting is enabled for the repository (Settings → Code security → Private vulnerability reporting). If the Report a vulnerability button is missing, open a public issue that asks for a private contact channel, and leave out every detail of the vulnerability.
Please do not report vulnerabilities in public issues, pull requests, discussions or AgentMBX messages.
- the AgentMBX version (
agentmbx --version) and the platform (macOS or Linux, Node version) - the component: CLI, MCP server, daemon, LAN pairing or delivery, relay, owner key, identity leases, wake adapters, setup
- steps to reproduce, and what an attacker gains
- whether the issue needs a paired host, a same-user local process, a relay operator or a network position
The trust boundaries are in docs/THREAT-MODEL.md and docs/SPEC.md. Some limits are documented and are not vulnerabilities by themselves:
- Processes running as the same OS user can read the local store and keys (D001).
- Envelope metadata (addresses, subject, thread, refs, tags, sizes, timing) is visible on the LAN and to a relay operator. Only bodies are sealed.
- Agent names are labels. A signature proves the sending host, not which agent on it wrote the message.
A way around any of these documented protections is in scope: signatures, body sealing, key pinning, owner grants, identity leases, wake limits, or the rule that message content never changes permissions.
Current audit and remediation status consolidates historical findings, shipped fixes, accepted risks and remaining work. It separates published npm code, merged changes and cloud deployment evidence; it is not a new penetration test. The roadmap tracks implementation and live acceptance gates.
Fixes go into the release selected by the npm agentmbx@latest dist-tag. Use the install guide to install or update from the published npm package; repository versions and GitHub tags may be ahead of that artifact. Older versions do not receive backports.