Kerux is in early development. Security fixes are applied to the latest commit on main.

Do not report security vulnerabilities through public GitHub issues.

Instead, report them via:

• GitHub Security Advisories: Report a vulnerability
• Email: Send a PGP-encrypted email to the maintainers (if listed in MAINTAINERS)

You should receive a response within 48 hours. If you don't, please follow up.

• Description of the vulnerability
• Steps to reproduce
• Affected versions/commits
• Potential impact
• Suggested fix (if available)

• Vulnerabilities are disclosed via GitHub Security Advisories after a fix is released.
• We follow coordinated disclosure.
• Credit is given to the reporter unless they request anonymity.

Kerux executes arbitrary shell commands via the terminal tool and arbitrary code via the code_execution tool. These tools:

• Run with the same privileges as the Kerux process
• Do not sandbox or isolate execution
• Accept input from LLM-generated content, which may be manipulated

Mitigation: Run Kerux in a sandboxed environment (container, VM) when processing untrusted input.

• API keys are read from environment variables or config files
• Never commit API keys to the repository
• Config files (kerux.toml) should be excluded from version control via .gitignore

• All dependencies are resolved from crates.io
• Use cargo audit to check for known vulnerabilities in dependencies:

  cargo install cargo-audit
  cargo audit