Skip to main content
Public proof of conceptFix available

CVE-2016-2107

A public proof of concept exists; no exploitation attested.

  • Published2016-05-05
  • WeaknessCWE-200 · CWE-310

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a certain padding check, which allows remote attackers to obtain sensitive cleartext information via a padding-oracle attack against an AES CBC session. NOTE: this vulnerability exists because of an incorrect fix for CVE-2013-0169.

Timeline

dates in UTC
  1. 2016-05-0501:59CVE publishedNVD
  2. 2026-10-2319:23First public proof of conceptPoC-in-GitHub
  3. 2026-10-2319:23EPSS crossed 10 %FIRST EPSS

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2016-2107?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2016-2107?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Google android
BranchAffectedFixed in
5.1= 5.1.0no fix published
4.0= 4.0no fix published
4.0= 4.0.1no fix published
4.0= 4.0.2no fix published
4.0= 4.0.3no fix published
4.0= 4.0.4no fix published
4.1= 4.1no fix published
4.1= 4.1.2no fix published
4.2= 4.2no fix published
4.2= 4.2.1no fix published
4.2= 4.2.2no fix published
4.3= 4.3no fix published
OpenSSL
BranchAffectedFixed in
1.0≤ 1.0.1sno fix published
1.0= 1.0.2no fix published
1.0= 1.0.2ano fix published
1.0= 1.0.2bno fix published
1.0= 1.0.2cno fix published
1.0= 1.0.2dno fix published
1.0= 1.0.2eno fix published
1.0= 1.0.2fno fix published
1.0= 1.0.2gno fix published
Node.js
BranchAffectedFixed in
5.x≥ 5.0.0, < 5.11.15.11.1
4.x≥ 4.2.0, < 4.4.44.4.4
0.12≥ 0.12.0, < 0.12.140.12.14
0.10≥ 0.10.0, < 0.10.450.10.45
4.x≥ 4.0.0, ≤ 4.1.2no fix published
6.0= 6.0.0no fix published

12 more products in the sources.

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

Advisories and patches

Detection

read 2026-10-23 19:23 UTC
Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
2 repositories, unverifiedFiloSottile/CVE-2016-2107tmiklas/docker-cve-2016-2107
PoC-in-GitHub

Sources

  • NVDCVSS 3.15.9read 2026-10-23
  • NVDCVSS 2.02.6read 2026-10-23
  • NVDweakness (CWE)CWE-200, CWE-310read 2026-10-23
  • FIRST EPSSEPSS score89.1 %read 2026-10-23
  • PoC-in-GitHubproof of concept2read 2026-10-23

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Published
2016-05-05
Last Modified
2026-06-17
NVD status
Modified

Frequently asked questions

What is CVE-2016-2107?

The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a certain padding check, which allows remote attackers to obtain sensitive cleartext information via a padding-oracle attack against an AES CBC session. NOTE: this vulnerability exists because of an incorrect fix for CVE-2013-0169.

Is CVE-2016-2107 actively exploited?

Active exploitation of CVE-2016-2107 has not been confirmed. Its EPSS score was 89.1% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2016-2107?

CVE-2016-2107 has a CVSS v3 base score of 5.9 (MEDIUM severity), with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, October 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database