GHSA-xxg2-76qg-7vj6: 
Rust vulnerability analysis and mitigation

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

Impact

To show what changed in a source file, Kule outlines it (crates/kule-entities/src/code.rs). Each entity's shown name is its parent's whole name plus its own (qualified = format!("{}{}{name}", p.name, lang.separator(), …)), and only an entity's own name is cut (tidy, MAX_NAME), never the qualified one. In modules (or namespaces) nested d deep, the names add up to about d²/2 times a name's length, and grouping and sorting compare those long strings. The caps allow it: 1 MiB per file (MAX_BYTES), 20,000 entities (MAX_ENTITIES); the time limit in outline.rs is checked only between files. An agent that writes such a file makes the daemon, outside the sandbox, take memory and CPU far beyond the file's size, with nothing for the person to do: the daemon's background scan outlines changed files, and every status, review and sync does it again. The class of GHSA-xjhq-rqpx-mvw8, through a path its fix does not cap.

Seen

macOS, debug build, kule status on a copy holding one file of Rust modules nested d deep (mod mmm…{ with 45-letter names):

depth 1000   54 KB    0.8 s     69 MB peak
depth 2000  109 KB    2.9 s    211 MB peak
depth 4000  219 KB   11.2 s    704 MB peak
control: 4000 modules side by side, 251 KB    0.3 s    31 MB peak

The review run alongside measured 2.37 GB and 44 s at depth 8000 (408 KB). The caps allow depth 20,000 in 1 MiB; not run.

Fix

Outlining stops at 64 nested entities (a deeper file is shown without its outline), and a shown name keeps the last 512 characters of its parents' names and its own. Found in the 2026-11-13 review, on main at bbf354f (0.2.0-preview.22).