Grob ships fixes only on the latest released minor version. Older releases are not patched; upgrade to the latest release from https://github.com/azerozero/grob/releases before reporting an issue.

Do not open a public GitHub issue for security problems.

Report vulnerabilities privately through either channel:

1. GitHub's private vulnerability reporting — https://github.com/azerozero/grob/security/advisories/new.
2. Email security@a00.fr.

Please include:

• A description of the issue and its impact.
• The grob version (grob --version) and build (binary, container, or source).
• A minimal reproduction — TOML config, request payload, and the observed behaviour. Redact API keys, OAuth tokens, and any personally identifiable data before sending.
• Your suggested severity (informational, low, medium, high, critical) and whether a CVE should be requested.

We credit reporters in the release notes and the associated GitHub Security Advisory unless you request anonymity.

In scope:

• The grob binary and its default configuration.
• The routing, dispatch, DLP, OAuth, and policy pipelines.
• The HTTP surfaces exposed by grob start (Anthropic-native, OpenAI Chat Completions, OpenAI Responses, management endpoints).
• Supply-chain metadata shipped by the release pipeline: GitHub Releases artefacts, the container image at ghcr.io/azerozero/grob, and the Homebrew formula at azerozero/tap/grob.

Out of scope:

• Denial-of-service via provider-side rate limits (we cannot fix upstream quotas).
• Issues that require a compromised local user account with filesystem access to ~/.grob/.
• Third-party providers themselves (Anthropic, OpenAI, Gemini, etc.). Report those to the upstream vendor.
• Experimental or opt-in feature flags not enabled in the default build.

Grob touches API keys, OAuth refresh tokens, and request payloads that may contain secrets or PII. When reproducing an issue:

• Redact keys and tokens before sharing logs or configs.
• Prefer a synthetic reproduction over copying a production payload.
• When you must share real data, encrypt it with our PGP key or use GitHub's private vulnerability reporting, which is end-to-end to the maintainers.

A PGP key for security@a00.fr is published at https://a00.fr/pgp.asc. Fingerprint is announced in release notes when rotated. If no PGP key is available, GitHub private vulnerability reporting is the recommended channel.

Good-faith security research that follows this policy is welcome. We will not pursue legal action against researchers who:

• Give us a reasonable time to remediate before public disclosure.
• Avoid privacy violations, destruction of data, and service degradation during testing.
• Do not exfiltrate data beyond what is needed to prove the vulnerability.