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

CVE-2020-7649 — snyk-broker

MEDIUMFix: snyk/broker@90e0bac

CVE-2020-7649 is a medium-severity (CVSS 4.9) Path Traversal vulnerability in snyk-broker. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for snyk-broker — see the affected versions and patch details below.

snyk-broker Path Traversal before v4.73.0

Also known asGHSA-gq75-5gc3-rfwg
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Oct 31, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.6%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs76th percentile — riskier than 76% of all scored CVEsHighest risk
0.07%0.75%1.44%2.13%0.6%1.6%May 26Sep 26Oct 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.

1other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
snyk-brokernpm
1Kdownloads / week

Description

This affects the package snyk-broker before 4.73.0. It allows arbitrary file reads for users with access to Snyk's internal network via directory traversal.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmsnyk-brokerall versions4.73.0npm install snyk-broker@4.73.0

Affected Products

1 product · 1 configurations
Application
brokersnyk
< 4.73.0
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.

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Fix

    Update snyk-broker to 4.73.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-7649 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

This affects the package snyk-broker before 4.73.0. It allows arbitrary file reads for users with access to Snyk's internal network via directory traversal.
O3 Security · Impact-Aware SCA

Is CVE-2020-7649 in your dependencies?

Find it across npm, including transitive dependencies.

CVE-2020-7649: snyk-broker — Fixed in 4.73.0