GHSA-6XX4-9WP6-65P7

skilo add follows symbolic links, allowing arbitrary local file disclosure from a malicious skill source

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.

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.

GHSA-6XX4-9WP6-65P7 has a CVSS score of 6.5 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.11.1); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

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.

1. What is GHSA-6XX4-9WP6-65P7? GHSA-6XX4-9WP6-65P7 is a medium-severity security vulnerability in skilo (rust), affecting versions >= 0.5.0, < 0.11.1. It is fixed in 0.11.1.
2. How severe is GHSA-6XX4-9WP6-65P7? GHSA-6XX4-9WP6-65P7 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of skilo are affected by GHSA-6XX4-9WP6-65P7? skilo (rust) versions >= 0.5.0, < 0.11.1 is affected.
4. Is there a fix for GHSA-6XX4-9WP6-65P7? Yes. GHSA-6XX4-9WP6-65P7 is fixed in 0.11.1. Upgrade to this version or later.
5. Is GHSA-6XX4-9WP6-65P7 exploitable, and should I be worried? Whether GHSA-6XX4-9WP6-65P7 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-6XX4-9WP6-65P7 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-6XX4-9WP6-65P7? Upgrade skilo to 0.11.1 or later.