The Envoy AI Gateway maintainers and community take security seriously. We appreciate your efforts to responsibly disclose your findings, and will make every effort to acknowledge your contributions.

Please do not report security vulnerabilities through public GitHub issues, discussions, pull requests, or any other public channel.

Instead, please report vulnerabilities privately using one of the following channels:

1. Preferred: Open a GitHub Security Advisory ("Report a vulnerability" on the repository's Security tab). This allows the maintainers to triage the report and collaborate with you privately, directly on GitHub.
2. Alternative: Email the Envoy AI Gateway security team at envoy-ai-gateway-security@googlegroups.com.

If the vulnerability relates to Envoy Proxy or Envoy Gateway (the components that Envoy AI Gateway is built on top of) rather than Envoy AI Gateway itself, please report it to the relevant upstream project:

• Envoy Proxy: https://github.com/envoyproxy/envoy/security/advisories/new
• Envoy Gateway: email envoy-gateway-security@googlegroups.com (see the Envoy Gateway security policy)

To help us triage and resolve the issue as quickly as possible, please include as much of the following information as you can:

• A description of the vulnerability and its potential impact.
• The affected version(s) of Envoy AI Gateway.
• Steps to reproduce the issue, including any sample configuration, requests, or proof-of-concept code.
• Any known workarounds or suggested remediation.

Note: If your report includes data that has privacy concerns, please sanitize the data prior to sharing it.

After a vulnerability is reported, the maintainers will follow this process:

1. Acknowledgement — We aim to acknowledge receipt of your report within 3 business days.
2. Triage — We will investigate to validate the report, determine the affected versions, and assess the severity and impact.
3. Fix and coordination — We will work on a fix and coordinate a release timeline with you. We aim to resolve or publicly disclose privately reported issues within 90 days of the initial report.
4. Release and disclosure — Once a fix is available, we will publish the patched release and an accompanying security advisory.

We will keep you informed of the progress throughout the process. If you would like to be credited for the discovery, please let us know, and we will include an acknowledgement in the advisory (with your consent).

Please keep the details of any reported vulnerability confidential until a fix has been released and the embargo has been lifted, so that users have a chance to upgrade.

Envoy AI Gateway follows the support policy described in RELEASES.md, aligned with the Envoy Gateway release support policy. Minor releases are cut on a roughly quarterly cadence, and each minor release is supported for 6 months after its release date. In practice this means the two most recent minor releases (the current and the previous v1.x line) are supported at any given time.

Security fixes are developed on the main branch and backported as patch releases to every minor release that is still within its support window. We strongly recommend that all users run a supported, up-to-date v1.x version. Reports against unsupported or end-of-life versions may be addressed by asking you to reproduce the issue on a supported version.

Security patches and advisories are announced through:

• The GitHub Releases page
• The GitHub Security Advisories page

We recommend watching the repository and subscribing to these channels to stay informed about security updates.

To minimize security risks when running Envoy AI Gateway:

• Run the latest supported version and apply patches promptly.
• Follow the principle of least privilege when configuring credentials and BackendSecurityPolicy resources, and store secrets using Kubernetes Secrets (or an external secret manager) rather than in plaintext configuration.
• Restrict network access to the control plane and management interfaces.
• Regularly review the security-related documentation under the project docs.

If you have any general (non-sensitive) questions about this security policy, please reach out to the maintainers listed in MAINTAINERS.md. To report a vulnerability, always use one of the private channels described above — the GitHub Security Advisory flow or the security team at envoy-ai-gateway-security@googlegroups.com — rather than a public channel.

Thank you for helping to keep Envoy AI Gateway and its users secure.