| Version | Supported |
|---|---|
| 1.2.x | ✅ |
| 1.1.x | ✅ |
| 1.0.x | ✅ |
| 0.1.x | ✅ |
Security fixes are published for the latest 1.2.x release. Upgrade via
pip install -U inter-agent-guard.
If you discover a security vulnerability in AgentGuard, please report it responsibly.
- Do not open a public GitHub issue for exploitable vulnerabilities.
- Open a private security advisory on GitHub, or email nizba06@users.noreply.github.com with the details below.
- Include:
- A description of the issue and affected components (Message Inspector, Trust Verifier, Capability Enforcer)
- Steps to reproduce, including sample messages or manifests if applicable
- Impact assessment (bypass, false negative, false positive, audit tampering)
- Your suggested fix, if any
We aim to acknowledge reports within 5 business days and provide a remediation timeline within 14 business days for confirmed issues.
In scope:
- Runtime bypass of
AgentGuard.inspect_message, trust verification, or capability enforcement - Audit log hash-chain integrity failures
- ONNX model integrity bypass
- Adapter integration issues that allow unsigned or over-privileged agent actions
Out of scope:
- Vulnerabilities in upstream LLM providers or agent frameworks themselves
- Attacks requiring full compromise of the host operating system outside AgentGuard's control
- Issues in training datasets not shipped with the runtime package
Good-faith security research that follows this policy will not be pursued as a terms-of-service violation. Do not access data you do not own, disrupt production systems, or exfiltrate user data when testing.
- Threat model
- OWASP ASI mapping
- Known limitations
- Reviewer packet — repro steps for security review