Skip to content

[kit-layout][Audit 2026-04-14] Security configuration risks in default setup #57

@yanghao1143

Description

@yanghao1143

Summary

go-saas/kit-layout issues are disabled; tracking this audit item in go-saas/kit.

Findings (kit-layout)

  • Critical | confirmed hard-coded JWT secret and security cookie hash.
    • Evidence: kit-layout/configs/config.yaml:41, :43
  • High | probable permissive CORS wildcard.
    • Evidence: kit-layout/configs/config.yaml:7
  • Medium | confirmed container runs as root.
    • Evidence: kit-layout/Dockerfile:8, :24

Suggested Direction

  • Externalize/rotate secrets.
  • Restrict CORS per environment.
  • Run as non-root user.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions