Security fixes are provided for the latest published 0.1.x release and the current main branch. Older snapshots are not maintained.

Use GitHub private vulnerability reporting. Include the affected version or commit, platform, selected profile, realistic impact, and the smallest reproduction that does not contain credentials or unrelated user data.

Do not open a public issue, discussion, or pull request for an undisclosed vulnerability. If the private reporting link is unavailable, do not publish the details; retry after the private reporting channel becomes available.

fogstack is a local development harness that starts Docker containers, a kind cluster, a local registry and backing services. The full profile adds an AWS-compatible API emulator and OpenSearch. Runtime scripts, Docker/cluster configuration, generated client state, the toolbox, and published host ports are in scope.

The supported deployment is a developer-controlled workstation. fogstack is not an internet service, multi-tenant platform, production environment, or security-equivalent copy of AWS.

The repository checkout and person running fogstack are trusted. Application images, configuration values, API requests, and data handled by local services may be attacker controlled. Docker socket access is a privileged boundary: containers or tools with that socket can control Docker on the host.

Real Kubernetes contexts, real AWS credentials, unrelated Docker resources, and data in fogstack volumes are assets that must be protected from accidental access or deletion.

• Commands must not read or write host ~/.kube or ~/.aws state.
• AWS clients must use repo-local fake credentials and explicit local endpoints; a command must not fall through to a real AWS account.
• Published service ports must remain bound to 127.0.0.1 by default.
• Destructive cleanup and generated-file replacement must require explicit user intent and must not target unrelated resources.
• Secrets, tokens, real credentials, and user runtime state must not be tracked or included in logs, fixtures, reports, or release artifacts.

Violations of these invariants, command injection, unsafe path handling, unintended host/network exposure, or escape from an intended local boundary are reportable findings. Severity depends on realistic reachability and impact to host credentials, unrelated resources, code execution, or persistent data.

The AWS-compatible emulator does not enforce AWS IAM or networking semantics; it must not be used to validate authorization or production security behavior. Security plugins are disabled for local OpenSearch. Default database and AWS values are development-only. The toolbox and emulator can access the Docker socket, so running untrusted repository code or images grants them substantial control over the local Docker environment.

These limitations are part of the documented local trust model, not exclusions for bugs that cross the stated boundaries.