GHSA-xgh6-8m9v-7xr8: 
Rust vulnerability analysis and mitigation

Fixed in 0.2.0-preview.23; upgrade to it.

Impact

Kule refuses changes to .git/hooks/ (git-hooks, denied, never approved). It matches the folder's name exactly (crates/kule-engine/src/git.rs: ["hooks", ..] => Part::Hook), and a name it does not know counts as config. On a case-insensitive disk (macOS's default), .git/HOOKS/post-commit is the hook git runs, and Kule judges it "config changed", waiting for an approval rather than refused. Needs a repository without a hooks folder (git init --template=, some tools) and a person who approves a config line.

Seen

macOS, a repository made with git init --template=:

(.git/hooks/post-commit)   git: hook post-commit changed …  policy: denied … (git-hooks)
(.git/HOOKS/post-commit)   git: config changed (it can make the next git command run code)  policy: waits for approval

Not run here: approving it; the review run alongside approved it and the hook ran at the next git commit.

Fix

The hooks folder is matched under any case (.git/HOOKS/), at the repository's top and in a submodule's or a worktree's own repository, so such a hook is denied as a hook. Found in the 2026-11-13 review, on main at bbf354f (0.2.0-preview.22). Every value shown is made up; every run used a Kule home and a home of its own in a scratch folder.