Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm

CVE-2022-25759

CRITICALFix: neocotic/convert-svg@7e6031a

CVE-2022-25759 is a critical-severity (CVSS 9.9) Code Injection vulnerability in convert-svg-core. 2 public exploit references exist, so weaponization risk is real. O3 Security confirms whether CVE-2022-25759 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Remote Code Injection

Also known asGHSA-5gxc-fxcr-9326
Published
Jul 22, 2022
Updated
Jul 15, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
2 known

Real-World Exposure

1 pkg affected
📦convert-svg-core

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

The package convert-svg-core before 0.6.2 are vulnerable to Remote Code Injection via sending an SVG file containing the payload.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmconvert-svg-coreall versions0.6.2
Exploits & PoCs
2

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 convert-svg-core. 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. Fix

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

  3. Workarounds

    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 CVE-2022-25759 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 CVE-2022-25759. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The package convert-svg-core before 0.6.2 are vulnerable to Remote Code Injection via sending an SVG file containing the payload.
O3 Security · Impact-Aware SCA

Is CVE-2022-25759 in your dependencies?

O3 detects CVE-2022-25759 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.