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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Impact skilo add installs a skill by recursively copying the skill directory into the target skills directory. The copy routine (copydirall) classified each entry with std::fs::DirEntry::filetype() — 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/idrsa 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…

Published by the source

28 Jul 2026, 22:23 UTC

Last modified by the source

28 Jul 2026, 22:30 UTC

Source last checked

26 Oct 2026, 15:43 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-6xx4-9wp6-65p7

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-6xx4-9wp6-65p7

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-6xx4-9wp6-65p7

Advisory: skilo add follows symbolic links, allowing arbitrary local file disclosure from a malicious skill source
IDs: GHSA-6xx4-9wp6-65p7
Record: https://patchnext.com/advisories/ghsa-6xx4-9wp6-65p7 (revision 2, source checked 26 Oct 2026, 15:43 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: skilo 0.11.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io skilo: affected >= 0.5.0, < 0.11.1; fixed in 0.11.1

## Suggested inspection (read-only)
- crates.io skilo: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on skilo.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-6xx4-9wp6-65p7 (OSV record GHSA-6xx4-9wp6-65p7 lists affected ranges: crates.io skilo >=0.5.0 <0.11.1 (fixed))
- Verified: https://github.com/advisories/GHSA-6xx4-9wp6-65p7 (GitHub-reviewed advisory GHSA-6xx4-9wp6-65p7 lists affected ranges: crates.io skilo >=0.5.0 <0.11.1)

Commands are suggestions: review each one before running it.