CVE-2016-2107

MEDIUMNVD 5.99.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 89% probability of exploitation within the next 30 days (top 0.2% of all CVEs). NVD baseline CVSS 5.9 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Trending — 4 sources updated this weekWeaponized
5.9
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 89%
CISA-KEV: Not listedEPSS: 89%CVSS: 5.9Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
5.9
EG Score
9.0(high)
EG Risk
81(Track)
EG Risk 81/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation89% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
99.8%
KEV
Not listed

Published

May 5, 2016

Last Modified

May 6, 2026

References (116)

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuopenssl (1.0.2g-1ubuntu4.1) @ xenial2026-07-22ubuntu
redhatpatch2016-12-15redhat
redhatopenssl-0:1.0.1e-42.el6_7.52016-10-18redhat
redhatopenssl-0:1.0.1e-48.el6_8.12016-05-10redhat
redhatopenssl-1:1.0.1e-51.el7_2.52016-05-09redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(5)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 7× in last 7d / 13× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 14:14 UTCEPSS rescore
  2. 2026-07-23 01:22 UTCEG score recompute
  3. 2026-07-22 21:31 UTCEG score recompute▲ 3.10
  4. 2026-07-22 21:31 UTCVendor advisory
  5. 2026-07-22 21:30 UTCGHSA enrichment
  6. 2026-07-21 15:21 UTCEPSS rescore
  7. 2026-07-21 15:21 UTCEPSS rescore
  8. 2026-07-15 16:54 UTCEPSS rescore
  9. 2026-07-15 16:54 UTCEPSS rescore
  10. 2026-07-12 10:08 UTCOSV refresh
  11. 2026-07-07 13:42 UTCEPSS rescore
  12. 2026-07-01 15:02 UTCEPSS rescore
  13. 2026-06-28 04:53 UTCEPSS rescore
  14. 2026-06-24 14:02 UTCEPSS rescore
  15. 2026-06-24 14:02 UTCEPSS rescore
  16. 2026-06-23 21:30 UTCEPSS rescore
  17. 2026-06-23 15:50 UTCOSV refresh
  18. 2026-06-15 17:45 UTCEPSS rescore
  19. 2026-06-14 23:14 UTCEPSS rescore
  20. 2026-06-13 22:57 UTCEPSS rescore
  21. 2026-06-13 22:57 UTCEPSS rescore
  22. 2026-06-12 23:09 UTCEPSS rescore
  23. 2026-06-12 23:09 UTCEPSS rescore
  24. 2026-06-10 22:15 UTCEPSS rescore
  25. 2026-06-10 13:18 UTCEPSS rescore
Show 29 more
  1. 2026-06-08 14:14 UTCEPSS rescore
  2. 2026-06-07 15:22 UTCEPSS rescore
  3. 2026-06-07 15:22 UTCEPSS rescore
  4. 2026-06-06 20:29 UTCOSV refresh
  5. 2026-06-06 13:45 UTCEPSS rescore
  6. 2026-06-05 06:08 UTCEPSS rescore
  7. 2026-06-05 06:08 UTCEPSS rescore
  8. 2026-06-02 20:10 UTCEPSS rescore
  9. 2026-06-01 13:49 UTCEPSS rescore
  10. 2026-06-01 13:49 UTCEPSS rescore
  11. 2026-05-31 00:14 UTCEPSS rescore
  12. 2026-05-29 13:41 UTCEPSS rescore
  13. 2026-05-27 13:38 UTCEPSS rescore
  14. 2026-05-27 13:38 UTCEPSS rescore
  15. 2026-05-26 13:42 UTCEPSS rescore
  16. 2026-05-26 07:16 UTCEPSS rescore
  17. 2026-05-22 21:15 UTCEPSS rescore
  18. 2026-05-22 21:15 UTCEPSS rescore
  19. 2026-05-22 20:30 UTCEG score recompute
  20. 2026-05-22 20:30 UTCVendor advisory
  21. 2026-05-22 20:30 UTCGHSA enrichment
  22. 2026-05-20 22:37 UTCEPSS rescore
  23. 2026-05-20 22:37 UTCEPSS rescore
  24. 2026-05-20 22:37 UTCEPSS rescore
  25. 2026-05-20 11:21 UTCEPSS rescore
  26. 2026-05-20 11:21 UTCEPSS rescore
  27. 2026-05-20 11:21 UTCEPSS rescore
  28. 2026-05-18 21:30 UTCEPSS rescore
  29. 2026-05-18 21:30 UTCEPSS rescore

Publicly available exploits

(3 references)

Working exploit code is in the public domain (2 GitHub PoCs) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCtmiklas/docker-cve-2016-2107
    First seen Jun 9, 2016

    Docker container implementing tests for CVE-2016-2107 - LuckyNegative20

    Open source ↗
  • Exploit-DBEDB-39768✓ verified
    First seen May 4, 2016

    OpenSSL - Padding Oracle in AES-NI CBC MAC Check

    Open source ↗
  • GitHub PoCFiloSottile/CVE-2016-2107
    First seen May 3, 2016

    Simple test for the May 2016 OpenSSL padding oracle (CVE-2016-2107)

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2016-2107?
CVE-2016-2107 is a medium vulnerability published on May 5, 2016. 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…
When was CVE-2016-2107 disclosed?
CVE-2016-2107 was first published in the National Vulnerability Database on May 5, 2016, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2016-2107 actively exploited?
CVE-2016-2107 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2016-2107?
CVE-2016-2107 has a CVSS v3 base score of 5.9 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2016-2107?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-2107, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2016-2107

Explore →

Is Your Infrastructure Affected by CVE-2016-2107?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs