Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🛡️
Not in CISA KEV
HIGH severity

CVE-2016-2183 — node

HIGH

CVE-2016-2183 is a high-severity (CVSS 7.5) Information Exposure vulnerability. EPSS puts its 30-day exploitation probability at 94.7% (100th percentile). A fix is available — see the affected versions and patch details below.

Also known asPSF-2016-4
Published
Updated
Affected
9 products
Patched
See advisory
Exploits
None indexed
Exploitation data as of Oct 26, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

  • CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA’s SSVC triage for CVE-2016-2183.

EPSS Exploitation Probability

via FIRST.org ↗
94.7%probability of exploitation in next 30 days
Very High Risk0.00%
Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk
20.4%46.9%73.5%100.0%41.0%94.7%Apr 26Aug 26Oct 26

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

How urgent is this, really

CVE-2016-2183 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).

Where this sits among everything scored

Of 397,508 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Counts from FIRST.org, log-scaled.

Description

The DES and Triple DES ciphers, as used in the TLS, SSH, and IPSec protocols and other protocols and products, have a birthday bound of approximately four billion blocks, which makes it easier for remote attackers to obtain cleartext data via a birthday attack against a long-duration encrypted session, as demonstrated by an HTTPS session using Triple DES in CBC mode, aka a "Sweet32" attack.

Affected Products

9 products · 45 configurations
Application
content security management appliancecisco
2 versions
9.6.6-0689.7.0-006
Application
node.jsnodejs
≥ 6.0.0 && < 6.7.0
range
Application
opensslopenssl
26 versions
1.0.1a1.0.1b1.0.1c1.0.1d1.0.1e1.0.1f1.0.1g1.0.1h1.0.1i1.0.1j1.0.1k1.0.1l
Application
databaseoracle
2 versions
11.2.0.412.1.0.2
Application
pythonpython
≥ 3.5.0 && < 3.5.3
range
OS
enterprise linuxredhat
3 versions
5.06.07.0

Detection & mitigation playbook

Vulnerability
  1. Detect

    Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

  2. Fix

    Upgrade the affected component to the fixed release for CVE-2016-2183, or apply your distribution's backported patch — distro builds are often patched at an older version number, so check your vendor's advisory rather than the upstream version alone.

  3. 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.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

OpenSSL security update RHSA-2016:1940 mitigates this issue by lowering priority of DES cipher suites so they are not preferred over cipher suites using AES. For compatibility reasons, DES cipher suites remain enabled by default and included in the set of cipher suites identified by the HIGH cipher string. Future…

Workaround published by Red Hat
1.SSL/TLS configurations should prefer AES over DES. Versions of OpenSSL shipped with Red Hat Enterprise Linux 6 and 7 already do so. In the version of OpenSSL shipped with Red Hat Enterprise Linux 5, 3DES is listed below the AES-256 cipher and above the AES-128 cipher, therefore AES-256 based ciphersuite should not be disabled on the server. 2. Servers using OpenSSL, should not disable AES-128 and AES-256 ciphersuites. Versions of Apache shipped with Red Hat Enterprise Linux use the default cipher string, in which AES is preferred over DES/3DES based ciphersuites. For JBoss Middleware, and Java mitigations, please review this knowledge base…
Source: Red Hat security advisory for CVE-2016-2183 (CC BY 4.0)
ProductFixed inAdvisory
JBoss Core Services on RHEL 6jbcs-httpd24-httpd-0:2.4.23-122.jbcs.el6RHSA-2017:2710
JBoss Core Services on RHEL 7jbcs-httpd24-httpd-0:2.4.23-122.jbcs.el7RHSA-2017:2709
Red Hat Enterprise Linux 5 Supplementaryjava-1.7.0-ibm-1:1.7.0.10.1-1jpp.1.el5_11RHSA-2017:0337
Red Hat Enterprise Linux 5 Supplementaryjava-1.6.0-ibm-1:1.6.0.16.41-1jpp.1.el5_11RHSA-2017:0338
Red Hat Enterprise Linux 6openssl-0:1.0.1e-48.el6_8.3RHSA-2016:1940
Red Hat Enterprise Linux 6 Supplementaryjava-1.7.1-ibm-1:1.7.1.4.1-1jpp.1.el6_8RHSA-2017:0336
Red Hat Enterprise Linux 6 Supplementaryjava-1.8.0-ibm-1:1.8.0.4.1-1jpp.1.el6_8RHSA-2017:0462
Red Hat Enterprise Linux 7python-0:2.7.5-69.el7_5RHSA-2018:2123

Frequently Asked Questions

The DES and Triple DES ciphers, as used in the TLS, SSH, and IPSec protocols and other protocols and products, have a birthday bound of approximately four billion blocks, which makes it easier for remote attackers to obtain cleartext data via a birthday attack against a long-duration encrypted session, as demonstrated by an HTTPS session using Triple DES in CBC mode, aka a "Sweet32" attack.
O3 Security · Impact-Aware SCA

Is CVE-2016-2183 in your dependencies?

Find it across , including transitive dependencies.

CVE-2016-2183: node (High 7.5)