Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
HIGH severity

GHSA-2rq5-699j-x7p6

HIGH

GHSA-2rq5-699j-x7p6 is a high-severity (CVSS 7.5) Path Traversal vulnerability in swig-templates. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-2rq5-699j-x7p6 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Arbitrary local file read vulnerability during template rendering

Also known asCVE-2023-25345
Published
Mar 15, 2023
Updated
Nov 8, 2023
Affected
2 pkgs
Patched
None yet
Exploits
1 known
Exploitation data as of Nov 8, 2023 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected
📦swig-templates📦swig

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

Directory traversal vulnerability in swig-templates thru 2.0.4 and swig thru 1.4.2, allows attackers to read arbitrary files via the include or extends tags.

Affected Packages

2 total
EcosystemPackageVulnerable rangeFix
📦npmswig-templatesall versionsNo fix
📦npmswigall versionsNo fix
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for swig-templates. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Remediation status

    No patched version of swig-templates has shipped for GHSA-2rq5-699j-x7p6 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-2rq5-699j-x7p6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-2rq5-699j-x7p6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Directory traversal vulnerability in swig-templates thru 2.0.4 and swig thru 1.4.2, allows attackers to read arbitrary files via the include or extends tags.
O3 Security · Impact-Aware SCA

Is GHSA-2rq5-699j-x7p6 in your dependencies?

O3 detects GHSA-2rq5-699j-x7p6 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-2rq5-699j-x7p6: swig-templates Path… | O3 Security