Komputer is early software and should not yet be treated as a hardened multi-party isolation boundary.

Please report suspected vulnerabilities privately through GitHub's security advisory interface for s2-streamstore/komputer. Do not open a public issue until maintainers have had a reasonable opportunity to investigate.

Include:

• The affected revision, exact gVisor release or fork commit, platform, and host architecture.
• The OCI image reference and relevant runsc configuration.
• Whether guest isolation, S2 fencing or epoch authority, checkpoint-object integrity, credential isolation, or durable-format validation was bypassed.
• A minimal reproducer or deterministic fault sequence when possible.
• Any evidence of restoring a non-authoritative checkpoint or externally visible duplicate, reordered, invented, or unjournaled I/O.

The current vertical slice does not attach sandbox networking. The stable network anchor and Sentry attachment must be treated as part of the security and durability boundary before untrusted workloads receive external connectivity.