npm package report

Is @rhinostone/swig safe?

1 known vulnerability, worst severity HIGH.

cvss
7.5

how bad it is if exploited, out of 10

epss
not scored

chance of exploitation in the next 30 days

xyz score
3.3

CyberXYZ composite, out of 10

fig. 01 — GHSA-2mf3-mr2r-r4vf, the advisory selected below

// advisories

GHSA-2mf3-mr2r-r4vf

HIGH

@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 (../) escap

Affected
>=0, <2.7.1, < 2.7.1
Fixed in
2.7.1
Weakness
CWE-22
Published
2026-08-18
Source
osv

OSV


// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.


Checked 2026-09-22 at 02:47 UTC. The most recent advisory here was published 2026-08-18. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Think a verdict here is wrong? Tell us — we respond within 2 business days.
Is @rhinostone/swig safe? npm package security report | CyberXYZ