How severe is GHSA-p799-q2pr-6mxj?

No CVSS score has been assigned to GHSA-p799-q2pr-6mxj yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-p799-q2pr-6mxj?

GHSA-p799-q2pr-6mxj affects the following packages: go.rgst.io/stencil/v2 (Go). Ecosystems affected: Go.

How do I fix GHSA-p799-q2pr-6mxj?

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.

How do I detect GHSA-p799-q2pr-6mxj in my Go dependencies?

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.

How do I mitigate GHSA-p799-q2pr-6mxj if there is no patch (or I can't update yet)?

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.

Is GHSA-p799-q2pr-6mxj actively exploited in the wild?

No public exploit code has been indexed for GHSA-p799-q2pr-6mxj yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-p799-q2pr-6mxj published, and has it been updated?

GHSA-p799-q2pr-6mxj was published on March 29, 2025 and was last updated on April 1, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

go.rgst.io/stencil/v2 vulnerable to Path TraversalGHSA-p799-q2pr-6mxj

Fix: rgst-io/stencil#255

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

Also known asGO-2025-3584

Published

Mar 29, 2025

Updated

Apr 1, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Apr 1, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐹go.rgst.io/stencil/v2

Real-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

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`go.rgst.io/stencil/v2`	all versions	2.3.0`go get go.rgst.io/stencil/v2@v2.3.0`

Detection & mitigation playbook

Open-source dependency

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

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is GHSA-p799-q2pr-6mxj in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works