UnratedGoPublished
Kahi has privilege-drop and socket/log permission issues
GHSA-55f6-4pr5-c7m5
- Affected
- Go github.com/kahiteam/kahi <= 0.1.0-alpha.8
- Fixed in
- 0.1.0-alpha.9· Vendor fix available
- Issue
- Kahi releases up to and including v0.1.0-alpha.8 contain three privilege/permission issues, all fixed in v0.1.0-alpha.9. They were identified in a full-codebase security review on 2026-05-26. Affected versions All releases <= v0.1.0-alpha.8. Patched version v0.1.0-alpha.9. Details 1. Per-process privilege drop not applied (High) A process configured with user = "uid:gid" had its credential resolved but never attached to the spawned child, so the process ran with the supervisor's inherited privileges (root, when the supervisor runs as root) instead of the configured lower-privilege user. The intended privilege isolation did not occur, and no error was raised. 2. Privilege drop did not reset supplementary groups (Medium) When the daemon dropped privileges it set the primary gid and uid but never called setgroups(2), so the launching user's supplementary groups (for example docker, which is root-equivalent) remained active after the drop and were inherited by child processes. 3. FastCGI…
Recommended action: Upgrade to 0.1.0-alpha.9 (pre-release) or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.