GHSA-p799-q2pr-6mxj — v2
Fix: rgst-io/stencil#255GHSA-p799-q2pr-6mxj is a remote code execution vulnerability in go.rgst.io/stencil/v2. A fix is available for go.rgst.io/stencil/v2 — see the affected versions and patch details below.
go.rgst.io/stencil/v2 vulnerable to Path Traversal
Real-World Exposure
go.rgst.io/stencil/v2Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
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".
Patches
Patched in 2.3.0 and above.
Workarounds
No workarounds are present.
References
https://github.com/jaredallard/archives/security/advisories/GHSA-j95m-rcjp-q69h
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | go.rgst.io/stencil/v2 | all versions | 2.3.0go get go.rgst.io/stencil/v2@v2.3.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for go.rgst.io/stencil/v2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update go.rgst.io/stencil/v2 to 2.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p799-q2pr-6mxj is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-p799-q2pr-6mxj can be triaged on real exposure rather than presence alone.
Tailored to GHSA-p799-q2pr-6mxj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-p799-q2pr-6mxj in your dependencies?
O3 Security finds GHSA-p799-q2pr-6mxj across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.