How severe is CVE-2016-10693?

No CVSS score has been assigned to CVE-2016-10693 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2016-10693?

CVE-2016-10693 affects the following packages: pm2-kafka (npm). Ecosystems affected: npm.

How do I fix CVE-2016-10693?

No patched version of pm2-kafka has shipped for CVE-2016-10693 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect CVE-2016-10693 in my npm dependencies?

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

How do I mitigate CVE-2016-10693 if there is no patch (or I can't update yet)?

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.

Is CVE-2016-10693 actively exploited in the wild?

No public exploit code has been indexed for CVE-2016-10693 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2016-10693?

CVE-2016-10693 has an EPSS (Exploit Prediction Scoring System) score of 1.8%, placing it in the 77th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2016-10693?

CVE-2016-10693 is classified as CWE-311 (CWE-311), CWE-310 (CWE-310). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2016-10693 published, and has it been updated?

CVE-2016-10693 was published on September 1, 2020 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2016-10693 — pm2-kafka

CVE-2016-10693 is a CWE-311 vulnerability in pm2-kafka. No vendor fix is recorded yet; mitigation options are listed below.

Downloads Resources over HTTP in pm2-kafka

Published

Sep 1, 2020

Updated

Nov 8, 2023

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

Exploitation data as of Oct 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs77th percentile — riskier than 77% of all scored CVEsHighest risk

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

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.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

pm2-kafkanpm

7downloads / week

Description

Affected versions of pm2-kafka insecurely download an executable over an unencrypted HTTP connection.

In scenarios where an attacker has a privileged network position, it is possible to intercept the response and replace the executable with a malicious one, resulting in code execution on the system running pm2-kafka.

Recommendation

No patch is currently available for this vulnerability.

The best mitigation is currently to avoid using this package, using a different package if available.

Alternatively, the risk of exploitation can be reduced by ensuring that this package is not installed while connected to a public network. If the package is installed on a private network, the only people who can exploit this vulnerability are those who have compromised your network or those who have privileged access to your ISP, such as Nation State Actors or Rogue ISP Employees.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`pm2-kafka`	≥ 0.0.0	No fix

Affected Products

1 product · 1 configurations

Application

pm2-kafkapm2-kafka_project

1 version

1.0.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pm2-kafka, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of pm2-kafka has shipped for CVE-2016-10693 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
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.

Frequently Asked Questions

Affected versions of `pm2-kafka` insecurely download an executable over an unencrypted HTTP connection. In scenarios where an attacker has a privileged network position, it is possible to intercept the response and replace the executable with a malicious one, resulting in code execution on the system running `pm2-kafka`. ## Recommendation No patch is currently available for this vulnerability. The best mitigation is currently to avoid using this package, using a different package if available. Alternatively, the risk of exploitation can be reduced by ensuring that this package is not i

O3 Security · Impact-Aware SCA

Is CVE-2016-10693 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works