CVE-2020-7654 — snyk-broker
HIGHCVE-2020-7654 is a high-severity (CVSS 7.5) CWE-532 vulnerability in snyk-broker. A fix is available for snyk-broker — see the affected versions and patch details below.
Information Exposure in Snyk Broker
EPSS Exploitation Probability
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
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.
snyk-brokernpmDescription
All versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | snyk-broker | all versions | 4.73.1npm install snyk-broker@4.73.1 |
Affected Products
brokersynkDetection & mitigation playbook
Open-source dependencyDetect
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.
Fix
Update snyk-broker to 4.73.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-7654 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Frequently Asked Questions
Is CVE-2020-7654 in your dependencies?
Find it across npm, including transitive dependencies.