Skip to content

Security: DROOdotFOO/raxol

SECURITY.md

Security policy

Reporting a vulnerability

Report suspected vulnerabilities privately through GitHub security advisories: Report a vulnerability.

Do not open a public issue for anything you believe is exploitable. You can expect an acknowledgement within a few days; please include a reproduction and the commit or release you tested.

Supported versions

Only the latest published release line and master receive security fixes. No specific number is named here on purpose: the previous revision said 2.7.x, which was not on Hex, and by exclusion withdrew support from the only versions that were. Check Hex for what is published.

The agent packages (raxol_agent, raxol_payments and the rest) live in raxol-agent; report their vulnerabilities through its form: Report a vulnerability.

Scope worth knowing about

  • The SSH server (Raxol.SSH.Server) is fail-closed by design (no anonymous access unless explicitly configured); configuration-dependent findings are still welcome.
  • mix mcp.server (and raxol mcp, which embeds it) serves Raxol apps as MCP tools over stdio to the client that spawned it (OMP), so its boundary is that OS process: whoever can write its stdin can call every tool it lists. It starts only modules on the startable list (the playground demos unless configured), refuses raxol_start's path argument (starting from a path compiles the file), and serves resources/read only for the sessions it runs and the journals of the agents its agent_* tools act on; every other read is denied. With raxol_agent loaded, its agent_* tools start only the modules on config :raxol_agent, :mcp_spawnable_apps (a reference counter unless configured) and act only on agents this process started, or those listed in :mcp_exposed_agents (none unless configured). stdout is the JSON-RPC wire and carries nothing else. Anything that runs code a client chose beyond those modules, reads outside those sessions and journals, reaches an agent that is neither started by this process nor exposed, or puts a non-JSON-RPC byte on stdout is in scope.

Dependency scanning

CI runs dependency and vulnerability scanning on every push (.github/workflows/security.yml); reports for third-party advisories are better filed upstream unless Raxol's usage is what makes them exploitable.

There aren't any published security advisories