How severe is CVE-2014-3566?

CVE-2014-3566 has a CVSS score of 3.4/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2014-3566?

Affected package information for CVE-2014-3566 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2014-3566?

No fixed release is recorded for CVE-2014-3566 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2014-3566 in my code and dependencies?

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`).

How do I mitigate CVE-2014-3566 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-2014-3566 actively exploited in the wild?

Yes. There are 6 known exploit references for CVE-2014-3566, including 4 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2014-3566?

CVE-2014-3566 has an EPSS (Exploit Prediction Scoring System) score of 100.0%, placing it in the 100th 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. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2014-3566?

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

Is there exploit tooling available for CVE-2014-3566?

2 Metasploit modules reference CVE-2014-3566, which lowers the barrier to weaponization. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2014-3566 published, and has it been updated?

CVE-2014-3566 was published on October 15, 2014 and was last updated on April 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🛡️

Not in CISA KEV

LOW severity

CVE-2014-3566 — Node.js

LOW

CVE-2014-3566 is a low-severity (CVSS 3.4) CWE-310 vulnerability. 6 public exploit references exist, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.

Published

Oct 15, 2014

Updated

Apr 16, 2026

Affected

20 products

Patched

See advisory

Exploits

6 known

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

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2014-3566.

EPSS Exploitation Probability

via FIRST.org ↗

100.0%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

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

How urgent is this, really

CVE-2014-3566 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

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

Description

The SSL protocol 3.0, as used in OpenSSL through 1.0.1i and other products, uses nondeterministic CBC padding, which makes it easier for man-in-the-middle attackers to obtain cleartext data via a padding-oracle attack, aka the "POODLE" issue.

Affected Products

20 products · 147 configurations

mac os xapple

≤ 10.10.1

range

debian linuxdebian

2 versions

7.08.0

fedorafedoraproject

3 versions

192021

aixibm

3 versions

5.36.17.1

Application

viosibm

24 versions

2.2.0.102.2.0.112.2.0.122.2.0.132.2.1.02.2.1.12.2.1.32.2.1.42.2.1.52.2.1.62.2.1.72.2.1.8

mageiamageia

2 versions

3.04.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

The SSL protocol 3.0, as used in OpenSSL through 1.0.1i and other produc…

github.comMetasploitJan 2021

The SSL protocol 3.0, as used in OpenSSL through 1.0.1i and other produc…

github.comGithubFeb 2015

The SSL protocol 3.0, as used in OpenSSL through 1.0.1i and other produc…

github.comGithubOct 2014

The SSL protocol 3.0, as used in OpenSSL through 1.0.1i and other produc…

github.comMetasploitNov 2022

Detection & mitigation playbook

Vulnerability

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`).
Remediation status
No fixed release is recorded for CVE-2014-3566 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
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.

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 HatImportant

This issue affects the version of openssl as shipped with Red Hat Enterprise Linux 5, 6 and 7, Red Hat JBoss Enterprise Application Platform 5 and 6, and Red Hat JBoss Web Server 1 and 2, Red Hat Enterprise Virtualization Hypervisor 6.5, and Red Hat Storage 2.1. This issue affects the version of nss as shipped with…

Product	Fixed in	Advisory
Oracle Java for Red Hat Enterprise Linux 5	`java-1.7.0-oracle-1:1.7.0.75-1jpp.1.el5_11`	RHSA-2015:0079
Oracle Java for Red Hat Enterprise Linux 5	`java-1.6.0-sun-1:1.6.0.91-1jpp.1.el5_11`	RHSA-2015:0086
Oracle Java for Red Hat Enterprise Linux 6	`java-1.8.0-oracle-1:1.8.0.31-1jpp.1.el6`	RHSA-2015:0080
Red Hat Enterprise Linux 5	`java-1.7.0-openjdk-1:1.7.0.75-2.5.4.0.el5_11`	RHSA-2015:0068
Red Hat Enterprise Linux 5	`java-1.6.0-openjdk-1:1.6.0.34-1.13.6.1.el5_11`	RHSA-2015:0085
Red Hat Enterprise Linux 5 Supplementary	`java-1.7.0-ibm-1:1.7.0.8.0-1jpp.1.el5`	RHSA-2014:1876
Red Hat Enterprise Linux 5 Supplementary	`java-1.6.0-ibm-1:1.6.0.16.2-1jpp.1.el5`	RHSA-2014:1877
Red Hat Enterprise Linux 5 Supplementary	`java-1.5.0-ibm-1:1.5.0.16.8-1jpp.1.el5`	RHSA-2014:1881

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2014-3566 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2014-3566 — Node.js

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Description

Affected Products

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2014-3566 in your dependencies?