NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
HIGH severity

CVE-2022-24278 — convert-svg-core

HIGHFix: neocotic/convert-svg@2bbc498

CVE-2022-24278 is a high-severity (CVSS 7.5) Path Traversal vulnerability in convert-svg-core. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for convert-svg-core — see the affected versions and patch details below.

Directory Traversal

Also known asGHSA-5f47-rcg5-9m24SNYK-JS-CONVERTSVGCORE-2859830
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Nov 12, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs83th percentile — riskier than 83% of all scored CVEsHighest risk
0.23%1.06%1.89%2.71%0.7%2.2%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

5other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
convert-svg-corenpm
10Kdownloads / week

Description

The package convert-svg-core before 0.6.4 are vulnerable to Directory Traversal due to improper sanitization of SVG tags. Exploiting this vulnerability is possible by using a specially crafted SVG file.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmconvert-svg-coreall versions0.6.4npm install convert-svg-core@0.6.4

Affected Products

1 product · 1 configurations
Application
convert-svgconvert-svg_project
< 0.6.4
range
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.

The package convert-svg-core before 0.6.4 are vulnerable to Directory Tr…

github.comNVDJun 2022

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for convert-svg-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update convert-svg-core to 0.6.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-24278 is resolved across your whole dependency graph.

  3. Workarounds

    Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

The package convert-svg-core before 0.6.4 are vulnerable to Directory Traversal due to improper sanitization of SVG tags. Exploiting this vulnerability is possible by using a specially crafted SVG file.
O3 Security · Impact-Aware SCA

Is CVE-2022-24278 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2022-24278: convert-svg — Fixed in 0.6.4