Skip to content

Security: sushinpv/kube-scope

SECURITY.md

Security policy

KubeScope is an early-stage local desktop application. Security fixes target the latest development branch and latest published release; older versions do not have a separate maintenance schedule.

Report a vulnerability privately

Use GitHub's private vulnerability report when available under Security → Report a vulnerability. Include the affected version, impact, reproduction steps, and a minimal demo or synthetic fixture. Do not include actual kubeconfig, tokens, cloud keys, private certificates, or customer data.

If private reporting is unavailable, open an issue requesting a private security contact without disclosing vulnerability details. Wait for a private channel before sharing the report. Avoid public exploit details while a fix is being prepared. This project does not currently offer a bug bounty or a guaranteed response time.

Relevant boundaries

  • The API is for loopback access only. It uses a session token, Host/Origin checks, and a Content Security Policy. Publishing it through a proxy changes that boundary.
  • Live operations use installed kubectl and the identity in the selected kubeconfig. Trusted kubeconfigs and credential plugins are prerequisites; exec plugins can execute local programs.
  • Packaged apps enable local editing controls by default. Kubernetes RBAC still authorizes every operation; --read-only disables local controls.
  • Users with permission to read a Secret can view its YAML. Redact resource contents, logs, terminal output, screenshots, and diagnostics before sharing them.
  • Demo and automated checks use simulated data or injected runners. Release verification does not establish security or provider compatibility for every real cluster.

See permissions, usage and architecture, and verification scope.

There aren't any published security advisories