Summary
go.rgst.io/stencil/v2 vulnerable to Path Traversal
Workarounds
No workarounds are present.
References
https://github.com/jaredallard/archives/security/advisories/GHSA-j95m-rcjp-q69h
Impact
The library used to extract archives (github.com/jaredallard/archives) was vulnerable to the "zip slip" vulnerability. This is used to extract native extension archives and repository source archives. A native extension or repository archive could be crafted in such a way where a remote code execution or modification/reading of a file is possible using the user who is running stencil.
The severity is marked as "medium" because native extensions have always considered to be "unsafe" to run when not trusted. Native extensions are arbitrary code being ran, which could always do this same exploit with less steps. The medium severity is to reflect that this could be done even when a user is not using a native extension, for example a repository source archive. However, one would need to mutate the archives provided by Github or perform some hackery with links, which may not be possible. Thus, "medium" is used out of an abundance of caution where I would've labeled this as "low".
Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Patched in 2.3.0 and above.
Frequently Asked Questions
- What is GHSA-P799-Q2PR-6MXJ? GHSA-P799-Q2PR-6MXJ is a medium-severity path traversal vulnerability in go.rgst.io/stencil/v2 (go), affecting versions < 2.3.0. It is fixed in 2.3.0. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
- Which versions of go.rgst.io/stencil/v2 are affected by GHSA-P799-Q2PR-6MXJ? go.rgst.io/stencil/v2 (go) versions < 2.3.0 is affected.
- Is there a fix for GHSA-P799-Q2PR-6MXJ? Yes. GHSA-P799-Q2PR-6MXJ is fixed in 2.3.0. Upgrade to this version or later.
- Is GHSA-P799-Q2PR-6MXJ exploitable, and should I be worried? Whether GHSA-P799-Q2PR-6MXJ 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
- What actually determines whether GHSA-P799-Q2PR-6MXJ 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.
- How do I fix GHSA-P799-Q2PR-6MXJ? Upgrade
go.rgst.io/stencil/v2to 2.3.0 or later.