# Security Policy

## Supported versions

Security fixes are provided for the latest tagged release and the current default branch.

## Report a vulnerability

Please use GitHub's [private vulnerability reporting](https://github.com/LeemanCheung/dsh-image-gen/security/advisories/new). Do not open a public issue for a vulnerability.

Include the affected version or commit, DSH version, operating system, reproduction steps, and impact. Remove API keys, private prompts, generated private images, filesystem paths, and unrelated logs before submitting.

If private vulnerability reporting is temporarily unavailable, open a public issue that requests a private contact channel without disclosing technical details.

## Credential and data expectations

- Codex subscription mode resolves the refreshable OAuth credential through `dsh-codex-connect`; API-key mode resolves the configured DSH credential reference. The plugin never persists or logs either resolved secret.
- OAuth credentials are accepted only for the fixed first-party `https://chatgpt.com/backend-api/codex` origin. API-key requests default to HTTPS, with plain HTTP limited to loopback development hosts.
- Every credential-bearing provider request rejects redirects.
- Final-image RPC reads are loopback-only and authorized against the exact session and call record.
- Partial image bytes are bounded, kept only during an active call, and never written to session history.
- Completed images are validated and stored by DSH's attachment service.
- A local reference image is read only after the DSH approval service grants that exact `image_gen` call. The approval names the file and configured upload origin; `approval: never` and missing answerers fail closed.
- Reference bytes are validated without persistence, sent only through the API-key edit route, and committed as an attachment only after the Provider succeeds. The private Codex subscription endpoint is never used for reference uploads.