GHSA-6xx4-9wp6-65p7: Skilo Remote Code Execution Vulnerability

MODERATE
Share
CVSS 6.5
CWE-59 CWE-61
Published
Advisory Summary

GHSA-6xx4-9wp6-65p7 is a MODERATE (CVSS 6.5) remote code execution vulnerability (CWE-59: Improper Link Resolution Before File Access ('Link Following')) affecting Skilo libraries in the crates.io ecosystem. The issue involves skilo add follows symbolic links, allowing arbitrary local file disclosure from a malicious skill source. Remediation is available by upgrading affected packages to version 0.11.1.

GHSA-6xx4-9wp6-65p7 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-6xx4-9wp6-65p7
Severity MODERATE
CVSS v3.1 Base Score 6.5
CWE Classification CWE-59: Improper Link Resolution Before File Access ('Link Following')
Affected Product Skilo
Package Ecosystem crates.io
Published Date
Last Updated

Security Impact

CVSS: 6.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix GHSA-6xx4-9wp6-65p7

To remediate this vulnerability, upgrade all affected Skilo dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

skilo fixed: 0.11.1 
Upgrade skilo to 0.11.1
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for skilo

How to Check if You Are Affected

To determine whether your application is affected by GHSA-6xx4-9wp6-65p7, inspect your project dependencies for Skilo:

inspect dependencies for skilo

Analyze the terminal output to locate any version of Skilo in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.11.1), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-59: Improper Link Resolution Before File Access ('Link Following'), where the product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource. In Skilo, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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.

GHSA-6xx4-9wp6-65p7 Affected Skilo Versions

1 component(s)
Fixed Versions:
0.11.1
Product / Package Ecosystem Affected Versions Fixed Version
skilo
 crates.io
≥ 0.5.0
< 0.11.1
0.11.1

References

GitHub Advisory / Wiki ADVISORY
https://github.com/manuelmauro/skilo/security/advisories/GHSA-6xx4-9wp6-65p7
Skilo Source Repository REPOSITORY
https://github.com/manuelmauro/skilo/pull/11
Security Fix Commit FIX COMMIT
https://github.com/manuelmauro/skilo/commit/c14bdc2eddcf26633ab1dcc0b2d5c0ff42c72a3e
Skilo Source Repository REPOSITORY
https://github.com/manuelmauro/skilo
Skilo Release RELEASE
https://github.com/manuelmauro/skilo/releases/tag/v0.11.1

Frequently Asked Questions

What is GHSA-6xx4-9wp6-65p7?
GHSA-6xx4-9wp6-65p7 is a security vulnerability in Skilo involving skilo add follows symbolic links, allowing arbitrary local file disclosure from a malicious skill source under CWE-59: Improper Link Resolution Before File Access ('Link Following').
Which Skilo versions are affected?
Affected versions include releases prior to 0.11.1 across affected packages: skilo.
What version fixes GHSA-6xx4-9wp6-65p7?
Upgrading to 0.11.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is skilo affected?
Yes, skilo is affected in releases prior to 0.11.1. Upgrade your dependency to 0.11.1 or later.
What is the CVSS score of GHSA-6xx4-9wp6-65p7?
GHSA-6xx4-9wp6-65p7 has a CVSS v3.1 base score of 6.5 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N.
What CWE is associated with GHSA-6xx4-9wp6-65p7?
GHSA-6xx4-9wp6-65p7 is classified under CWE-59: Improper Link Resolution Before File Access ('Link Following') (The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.).
How can I check crates.io dependencies for GHSA-6xx4-9wp6-65p7?
Run the dependency tree command: 'inspect dependencies for skilo'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-6xx4-9wp6-65p7",
  "modified" : "2026-07-28T22:23:48Z",
  "published" : "2026-07-28T22:23:48Z",
  "aliases" : [ ],
  "summary" : "skilo add follows symbolic links, allowing arbitrary local file disclosure from a malicious skill source",
  "details" : "### Impact\n\n`skilo add` installs a skill by recursively copying the skill directory into the\ntarget skills directory. The copy routine (`copy_dir_all`) classified each entry\nwith `std::fs::DirEntry::file_type()` — which does **not** follow symlinks — and\nthen copied non-directory entries with `std::fs::copy()`, which **does**\ndereference symlinks.\n\nAs a result, a skill containing a symbolic link such as\n`reference.txt -> /home/<user>/.ssh/id_rsa` was copied as a regular file whose\ncontents are the link's **target**. A malicious skill source — for example a git\nrepository installed via `skilo add github.com/<attacker>/<skills>`, or a local\npath — could read arbitrary files readable by the user running `skilo add` (SSH\nkeys, cloud credentials, `.env` files, etc.) and place their contents inside the\ninstalled skill directory, where the user or their agent may later read, share,\nor sync them.\n\nThis is arbitrary local file disclosure (CWE-59 / CWE-61, symlink following)\ntriggered by installing an untrusted skills source.\n\n### Patches\n\nFixed in **0.11.1**. `copy_dir_all` now rejects symbolic-link entries at any\nrecursion depth (failing closed with a dedicated error) instead of dereferencing\nthem.\n\n### Workarounds\n\n- Only install skills from sources you trust.\n- Inspect a skill source for symbolic links before running `skilo add`.\n\n### Affected versions\n\nIntroduced together with the `skilo add` command in 0.5.0 and present through\n0.11.0. Releases before 0.5.0 do not include the `add` command.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "skilo"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.5.0"
      }, {
        "fixed" : "0.11.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/manuelmauro/skilo/security/advisories/GHSA-6xx4-9wp6-65p7"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/manuelmauro/skilo/pull/11"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/manuelmauro/skilo/commit/c14bdc2eddcf26633ab1dcc0b2d5c0ff42c72a3e"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/manuelmauro/skilo"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/manuelmauro/skilo/releases/tag/v0.11.1"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-59", "CWE-61" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-07-28T22:23:48Z",
    "nvd_published_at" : null
  }
}