Skip to content

Security reporting

CGP is pre-alpha and must not yet be treated as a complete production security or compliance boundary.

Use GitHub private vulnerability reporting.

Do not create a public issue for vulnerabilities involving:

  • context or tenant leakage;
  • unsafe provider routing;
  • receipt or provenance forgery;
  • prompt-injection authority escalation;
  • privacy-detector bypass;
  • vault-key exposure;
  • malicious document parsing;
  • credential or personal-data exposure.

Use synthetic data in every reproduction.

CGP aims to make the following boundaries explicit:

  • original documents remain local under local-only privacy policies;
  • unsupported documents fail closed under fail-closed policies;
  • untrusted context cannot increase its own authority;
  • provider routing must respect declared policy capabilities;
  • receipts must be integrity-protected;
  • sensitive values must not enter logs or telemetry.

Several of these controls remain roadmap work and are not production guarantees.

Read the complete Security Policy.