Back to Signal Feed
CodeTracked since May 20, 2026

moai-adk P0 security blockers fixed to unblock v2.20.0-rc1

The merged PR resolves the three critical release-blocking security defects in moai-adk by sealing token-file permissions, blocking tmux-based sensitive env leakage paths, and hardening checksum handling for auto-updates, so the v2.20.0-rc1 release can proceed without those P0 stop-ship risks.

CWE-732/552CWE-214CWE-345settings.local.json

What Happened

  • The merged PR resolves the three critical release-blocking security defects in moai-adk by sealing token-file permissions, blocking tmux-based sensitive env leakage paths, and hardening checksum handling for auto-updates, so the v2.20.0-rc1 release can proceed without those P0 stop-ship risks.
  • The merged PR resolves the three critical release-blocking security defects in moai-adk by sealing token-file permissions, blocking tmux-based sensitive env leakage paths, and hardening checksum handling for auto-updates, so the v2.20.0-rc1 release can proceed without those P0 stop-ship risks.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Implemented concrete critical security protections in the release/operational path: changed `.claude/settings.local.json` to restrictive mode (0o600) to prevent local token exposure, rerouted tmux sensitive-environment injection through source-file handling with `ErrTmuxSensitiveInjectFailed` and automatic cleanup, and added mandatory checksum enforcement using `ErrChecksumUnavailable` plus exponential-retry backoff (2s/4s/8s) to prevent silent integrity bypass.

Why Track This

Why It Matters

moai-adk를 운영하는 개발자와 릴리스 담당자는 이제 v2.20.0-rc1를 배포할 때 GLM 토큰 유출, tmux 경유 민감정보 노출, 검증되지 않은 업데이트 적용으로 인한 보안 사고 가능성이 낮아져 실제 운영 손실 위험을 즉시 줄일 수 있으며, 앞으로도 P0-4~P0-8 잔여 항목이 남지 않았는지 추적해야 합니다. Technical follow-up includes validating that the new 0o600 permission behavior remains stable across supported OSes, tmux cleanup is reliably executed under failure paths, and checksum-retry backoff does not mask repeated transport corruption in production update channels.

Impact

moai-adk를 운영하는 개발자와 릴리스 담당자는 이제 v2.20.0-rc1를 배포할 때 GLM 토큰 유출, tmux 경유 민감정보 노출, 검증되지 않은 업데이트 적용으로 인한 보안 사고 가능성이 낮아져 실제 운영 손실 위험을 즉시 줄일 수 있으며, 앞으로도 P0-4~P0-8 잔여 항목이 남지 않았는지 추적해야 합니다. Technical follow-up includes validating that the new 0o600 permission behavior remains stable across supported OSes, tmux cleanup is reliably executed under failure paths, and checksum-retry backoff does not mask repeated transport corruption in production update channels.

What To Watch Next

  • Watch whether CWE-732/552 becomes a repeated pattern.
  • Track follow-up changes around AI Security.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: followup_p0_4_to_p0_8_tracking, checksum_retry_masking_repeat_failures.
Open Topic TimelineOpen Technical EventOpen Original Sourcefollowup_p0_4_to_p0_8_tracking / checksum_retry_masking_repeat_failures / cross_platform_file_permission_regression / tmux_env_cleanup_regression

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

modu-ai/moai-adk PR #1032: feat(SPEC-V3R5-SECURITY-CRIT-001): v2.14.0→HEAD P0 보안 결함 3건 정정 (v0.2.0)

v2.14.0 → HEAD review closed three P0 security issues and cleared the v2.20.0-rc1 merge blocker through file-permission hardening, tmux sensitive-env protection, and mandatory checksum verification.