Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5amended

@rhinostone/swig: arbitrary local file read via include/extends path traversal

GHSA-2mf3-mr2r-r4vf

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@rhinostone/swig-jinja2 2.7.1; @rhinostone/swig-django 2.7.1; @rhinostone/swig-twig 2.7.1; @rhinostone/swig 2.7.1; @rhinostone/swig-core 2.7.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
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Overview @rhinostone/swig is a maintained fork of the abandoned swig template engine and inherited the directory-traversal vulnerability tracked upstream as CVE-2023-25345 / GHSA-2rq5-699j-x7p6. The {% include %}, {% extends %}, and {% import %} tags resolve their target path through the filesystem loader without confining the result to the configured template root. A path that traverses upward (../) escapes the root and reads an arbitrary file from the host filesystem, whose contents are emitted into the rendered output. Attack scenario The dangerous case does not require the attacker to control template source — only template data (the locals passed at render time). An application that renders a trusted template whose include / extends path is variable-driven is exposed: Setting ?partial=../../../../etc/passwd makes the loader resolve and read that file, and its contents are rendered into the response. A literal in trusted source is equally affected: {% include…

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

    Amended from ghsa record GHSA-2mf3-mr2r-r4vf

  2. Revision 1 · created ·

    Published from osv record GHSA-2mf3-mr2r-r4vf

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-2mf3-mr2r-r4vf

Advisory: @rhinostone/swig: arbitrary local file read via include/extends path traversal
IDs: GHSA-2mf3-mr2r-r4vf
Record: https://patchnext.com/advisories/ghsa-2mf3-mr2r-r4vf (revision 2, source checked 26 Oct 2026, 13:01 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @rhinostone/swig-jinja2 2.7.1; @rhinostone/swig-django 2.7.1; @rhinostone/swig-twig 2.7.1; @rhinostone/swig 2.7.1; @rhinostone/swig-core 2.7.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @rhinostone/swig-jinja2: affected < 2.7.1; fixed in 2.7.1
- npm @rhinostone/swig-django: affected < 2.7.1; fixed in 2.7.1
- npm @rhinostone/swig-twig: affected < 2.7.1; fixed in 2.7.1
- npm @rhinostone/swig: affected < 2.7.1; fixed in 2.7.1
- npm @rhinostone/swig-core: affected < 2.7.1; fixed in 2.7.1

## Suggested inspection (read-only)
- `npm ls @rhinostone/swig-jinja2 --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls @rhinostone/swig-django --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls @rhinostone/swig-twig --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls @rhinostone/swig --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls @rhinostone/swig-core --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 @rhinostone/swig-jinja2, @rhinostone/swig-django, @rhinostone/swig-twig, @rhinostone/swig, @rhinostone/swig-core.
- 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-2mf3-mr2r-r4vf (OSV record GHSA-2mf3-mr2r-r4vf lists affected ranges: npm @rhinostone/swig >=0 =0 =0 =0 =0 <2.7.1 (fixed))
- Verified: https://github.com/advisories/GHSA-2mf3-mr2r-r4vf (GitHub-reviewed advisory GHSA-2mf3-mr2r-r4vf lists affected ranges: npm @rhinostone/swig >=0 =0 =0 =0 =0 <2.7.1)

Commands are suggestions: review each one before running it.

Loading voting…