How severe is CVE-2014-6321?

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

Which packages are affected by CVE-2014-6321?

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

How do I fix CVE-2014-6321?

No fixed version has been published for CVE-2014-6321 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2014-6321 actively exploited in the wild?

Yes. There are 3 known exploit references for CVE-2014-6321, including 3 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-6321?

CVE-2014-6321 has an EPSS (Exploit Prediction Scoring System) score of 93.5%, 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-6321?

CVE-2014-6321 is classified as Code Injection (CWE-94). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Which products and versions are affected by CVE-2014-6321?

CVE-2014-6321 affects microsoft windows 7; microsoft windows 8; microsoft windows 8.1; microsoft windows rt, and 5 more product(s). Check the affected-products list on this page against your deployed version to confirm exposure.

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

CVE-2014-6321 was published on November 11, 2014 and was last updated on May 6, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2014-6321

Schannel in Microsoft Windows Server 2003 SP2, Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2012 Gold and R2, and Windows…

Published

Nov 11, 2014

Updated

May 6, 2026

Affected

0 pkgs

Patched

None yet

Exploits

3 known

EPSS Exploitation Probability

via FIRST.org ↗

93.5%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

Schannel in Microsoft Windows Server 2003 SP2, Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2012 Gold and R2, and Windows RT Gold and 8.1 allows remote attackers to execute arbitrary code via crafted packets, aka "Microsoft Schannel Remote Code Execution Vulnerability."

Affected Products

9 products · 12 configurations

windows 7microsoft

all

windows 8microsoft

all

windows 8.1microsoft

all

windows rtmicrosoft

all

windows rt 8.1microsoft

all

windows server 2003microsoft

all

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.

Schannel in Microsoft Windows Server 2003 SP2, Windows Vista SP2, Window…

blog.beyondtrust.comNVDOct 2019

Schannel in Microsoft Windows Server 2003 SP2, Windows Vista SP2, Window…

securitysift.comNVDOct 2019

Schannel in Microsoft Windows Server 2003 SP2, Windows Vista SP2, Window…

marc.infoNVDOct 2019

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2014-6321 in your stack?

O3 detects CVE-2014-6321 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works