PT-2026-69164 · Crates.Io · Skilo
Published
2026-07-28
·
Updated
2026-07-28
CVSS v3.1
6.5
Medium
| Vector | AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N |
Impact
skilo add installs a skill by recursively copying the skill directory into the
target skills directory. The copy routine (copy dir all) classified each entry
with std::fs::DirEntry::file type() — which does not follow symlinks — and
then copied non-directory entries with std::fs::copy(), which does
dereference symlinks.As a result, a skill containing a symbolic link such as
reference.txt -> /home/<user>/.ssh/id rsa was copied as a regular file whose
contents are the link's target. A malicious skill source — for example a git
repository installed via skilo add github.com/<attacker>/<skills>, or a local
path — could read arbitrary files readable by the user running skilo add (SSH
keys, cloud credentials, .env files, etc.) and place their contents inside the
installed skill directory, where the user or their agent may later read, share,
or sync them.This is arbitrary local file disclosure (CWE-59 / CWE-61, symlink following)
triggered by installing an untrusted skills source.
Patches
Fixed in 0.11.1.
copy dir all now rejects symbolic-link entries at any
recursion depth (failing closed with a dedicated error) instead of dereferencing
them.Workarounds
- Only install skills from sources you trust.
- Inspect a skill source for symbolic links before running
skilo add.
Affected versions
Introduced together with the
skilo add command in 0.5.0 and present through
0.11.0. Releases before 0.5.0 do not include the add command.Fix
Link Following
Found an issue in the description? Have something to add? Feel free to write us 👾
Related Identifiers
Affected Products
Skilo