Skip to content

Security: xsyetopz/OpenAgentLayer

Security

SECURITY.md

Security Policy

Reporting Vulnerabilities

Report security issues via GitHub Security Advisories (preferred) or email. Do not open public issues for security vulnerabilities.

Security Model

OpenAgentLayer hooks are guardrails, not walls. They catch common mistakes and enforce best practices but are not a security boundary against determined adversaries.

What Hooks Protect Against

Hook Protects against
pre-bash.mjs Broad rm -rf, blanket git add ., DNS exfiltration patterns
post-bash.mjs Accidental secret leaks in command output
post-write.mjs Placeholder/stub code reaching production
subagent-scan.mjs Silent scope reduction by agents

What Hooks Do Not Protect Against

  • Sophisticated prompt injection attacks
  • Adversarial code in untrusted repositories
  • Supply chain attacks via dependencies

Defense in Depth

For production use, combine hooks with:

  1. OS-level sandboxing -- macOS Seatbelt, Linux bubblewrap, or Docker containers
  2. Permission deny rules -- settings template blocks access to ~/.ssh, ~/.aws, credentials
  3. Code review -- @nemesis should review changes before committing; use /cca:git-workflow for Git hygiene
  4. Minimal permissions -- only grant tools each agent needs (enforced via agent frontmatter)

Sandboxing

macOS (Seatbelt)

Use Claude Code's built-in /sandbox command, or run with a custom Seatbelt profile restricting filesystem and network access to the project directory.

Linux (bubblewrap)

bwrap --ro-bind / / --dev /dev --proc /proc --tmpfs /tmp \
  --bind "$PROJECT_DIR" "$PROJECT_DIR" \
  --unshare-net \
  claude

Docker / Devcontainers

Mount only the project directory. Do not mount ~/.ssh, ~/.aws, or other credential stores.

Known CVE Mitigations

CVE Impact Fix
CVE-2025-59536 RCE via malicious project config Fixed in Claude Code v1.0.111
CVE-2026-21852 API key exfiltration Fixed in Claude Code v2.0.65; pre-secrets hook adds extra protection

Always update to the latest Claude Code version.

Skill/Plugin Vetting

Before installing third-party skills or plugins:

  1. Read the SKILL.md or plugin source code
  2. Check for hidden instructions or obfuscated commands
  3. Verify the author's reputation and repository history
  4. Prefer plugins from verified marketplaces with audit trails

There aren’t any published security advisories