GHSA-2MF3-MR2R-R4VF

GHSA-2MF3-MR2R-R4VF is a high-severity path traversal vulnerability in @rhinostone/swig (npm), affecting versions < 2.7.1. It is fixed in 2.7.1.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

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

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:

// application code, a configured filesystem loader with a basepath
swig.renderFile('page.html', { partial: req.query.partial });

{# page.html, trusted template #}
{% include partial %}

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 "../../../etc/passwd" %}.

Affected & patched

Every published version up to and including 2.7.0 is affected, @rhinostone/swig, and the shared @rhinostone/swig-core loader, hence @rhinostone/swig-twig, @rhinostone/swig-jinja2, and @rhinostone/swig-django as well.

Fixed in 2.7.1: the filesystem loader now rejects any include / extends / import path that resolves outside the configured basepath root, including paths supplied through an untrusted runtime variable. A new allowOutsideRoot loader option is available for the rare case of intentionally reading files from outside the root.

Upgrade to 2.7.2 or later: 2.7.1 fixed the vulnerability but introduced a regression, a relative basepath wrongly rejected every in-root template path. 2.7.2 resolves the basepath to an absolute path before the check and restores correct in-root resolution.

Workarounds

  • Upgrade to 2.7.2 (or later).
  • If you cannot upgrade immediately: configure the filesystem loader with an explicit basepath, and never pass untrusted data into an {% include %} / {% extends %} / {% import %} path.

References

Impact

Arbitrary local file disclosure (confidentiality). An attacker able to influence an include / extends / import path, directly, or via untrusted locals, can read files outside the template directory: application configuration, credentials, source code, /etc/passwd, and so on. There is no integrity or availability impact.

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.

GHSA-2MF3-MR2R-R4VF has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.7.1); upgrading removes the vulnerable code path.

Affected versions

@rhinostone/swig (< 2.7.1) @rhinostone/swig-core (< 2.7.1) @rhinostone/swig-twig (< 2.7.1) @rhinostone/swig-jinja2 (< 2.7.1) @rhinostone/swig-django (< 2.7.1)

Security releases

@rhinostone/swig → 2.7.1 (npm) @rhinostone/swig-core → 2.7.1 (npm) @rhinostone/swig-twig → 2.7.1 (npm) @rhinostone/swig-jinja2 → 2.7.1 (npm) @rhinostone/swig-django → 2.7.1 (npm)

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

Upgrade the following packages to resolve this vulnerability:

@rhinostone/swig to 2.7.1 or later; @rhinostone/swig-core to 2.7.1 or later; @rhinostone/swig-twig to 2.7.1 or later; @rhinostone/swig-jinja2 to 2.7.1 or later; @rhinostone/swig-django to 2.7.1 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is GHSA-2MF3-MR2R-R4VF? GHSA-2MF3-MR2R-R4VF is a high-severity path traversal vulnerability in @rhinostone/swig (npm), affecting versions < 2.7.1. It is fixed in 2.7.1. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
  2. How severe is GHSA-2MF3-MR2R-R4VF? GHSA-2MF3-MR2R-R4VF has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which packages are affected by GHSA-2MF3-MR2R-R4VF?
    • @rhinostone/swig (npm) (versions < 2.7.1)
    • @rhinostone/swig-core (npm) (versions < 2.7.1)
    • @rhinostone/swig-twig (npm) (versions < 2.7.1)
    • @rhinostone/swig-jinja2 (npm) (versions < 2.7.1)
    • @rhinostone/swig-django (npm) (versions < 2.7.1)
  4. Is there a fix for GHSA-2MF3-MR2R-R4VF? Yes. GHSA-2MF3-MR2R-R4VF is fixed in 2.7.1. Upgrade to this version or later.
  5. Is GHSA-2MF3-MR2R-R4VF exploitable, and should I be worried? Whether GHSA-2MF3-MR2R-R4VF 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
  6. What actually determines whether GHSA-2MF3-MR2R-R4VF 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.
  7. How do I fix GHSA-2MF3-MR2R-R4VF?
    • Upgrade @rhinostone/swig to 2.7.1 or later
    • Upgrade @rhinostone/swig-core to 2.7.1 or later
    • Upgrade @rhinostone/swig-twig to 2.7.1 or later
    • Upgrade @rhinostone/swig-jinja2 to 2.7.1 or later
    • Upgrade @rhinostone/swig-django to 2.7.1 or later

Stop the waste.
Protect your environment with Kodem.

Get a personalized demo
Get a personalized demo