Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.9amended

skilleton has improper input handling in repository/path processing

GHSA-5g3j-89fr-r2vp

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (skilleton 0.3.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
6.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N · score source
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Summary skilleton versions prior to 0.3.1 include security-related weaknesses in repository normalization and path handling logic. Version 0.3.1 contains fixes and additional test coverage for these issues. Affected Versions <0.3.1 Patched Versions =0.3.1 Impact In affected versions, crafted input could trigger unsafe or inefficient behavior in repository/path processing code paths. 0.3.1 mitigates this by: - replacing vulnerable parsing behavior with deterministic logic, - validating subpaths earlier before allocating git worktree resources, - adding stricter and broader regression tests around these flows. Severity Low to Moderate (project-maintainer assessed) Mitigation Upgrade to 0.3.1 or later. Workarounds No complete workaround is recommended other than upgrading. References - Branch: fix/security-code-scanning-alerts - Commits: - fix(security): harden git arg handling and path validation - fix(security): use while loop in normalizeRepoUrl instead of regex - Security Policy:…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-5g3j-89fr-r2vp

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-5g3j-89fr-r2vp

Agent brief

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

# Patch Next advisory brief: GHSA-5g3j-89fr-r2vp

Advisory: skilleton has improper input handling in repository/path processing
IDs: GHSA-5g3j-89fr-r2vp
Record: https://patchnext.com/advisories/ghsa-5g3j-89fr-r2vp (revision 3, source checked 26 Oct 2026, 12:47 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: skilleton 0.3.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm skilleton: affected < 0.3.1; fixed in 0.3.1

## Suggested inspection (read-only)
- `npm ls skilleton --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## 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 skilleton.
- 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-5g3j-89fr-r2vp (OSV record GHSA-5g3j-89fr-r2vp lists affected ranges: npm skilleton >=0 <0.3.1 (fixed))
- Verified: https://github.com/advisories/GHSA-5g3j-89fr-r2vp (GitHub-reviewed advisory GHSA-5g3j-89fr-r2vp lists affected ranges: npm skilleton >=0 <0.3.1)

Commands are suggestions: review each one before running it.

Loading voting…