CVE-2016-7055

MEDIUMNVD 5.95.9—
EchelonGraph scoreMEDIUM confidence

Score 5.9 from GitHub Security Advisory published 2022-05-14. NVD baseline CVSS 5.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
5.9
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 14%CVSS: 5.9Exploit: NoneExposed: 0

A fix is available — apply it.

There is a carry propagating bug in the Broadwell-specific Montgomery multiplication procedure in OpenSSL 1.0.2 and 1.1.0 before 1.1.0c that handles input lengths divisible by, but longer than 256 bits. Analysis suggests that attacks against RSA, DSA and DH private keys are impossible. This is because the subroutine in question is not used in operations with the private key itself and an input of the attacker's direct choice. Otherwise the bug can manifest itself as transient authentication and key negotiation failures or reproducible erroneous outcome of public-key operations with specially crafted input. Among EC algorithms only Brainpool P-512 curves are affected and one presumably can attack ECDH key negotiation. Impact was not analyzed in detail, because pre-requisites for attack are considered unlikely. Namely multiple clients have to choose the curve in question and the server has to share the private key among them, neither of which is default behaviour. Even then only clients that chose the curve will be affected.

CVSS v3
5.9
EG Score
5.9(medium)
EPSS
96.2%
KEV
Not listed

Published

May 4, 2017

Last Modified

May 13, 2026

References (30)

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibssl1.0.0 (1.0.2g-1ubuntu9.1) @ yakkety2026-05-22ubuntu
redhatjbcs-httpd24-openssl-1:1.0.2n-11.jbcs.el62018-07-12redhat
redhatjbcs-httpd24-openssl-1:1.0.2n-11.jbcs.el72018-07-12redhat
redhatpatch2018-07-12redhat

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.

All Vendor Advisories

(4)

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 6× in last 7d / 32× 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-07 13:42 UTCEPSS rescore
  2. 2026-07-06 02:20 UTCEPSS rescore
  3. 2026-07-06 02:20 UTCEPSS rescore
  4. 2026-07-05 02:27 UTCEPSS rescore
  5. 2026-07-04 06:28 UTCEPSS rescore
  6. 2026-07-01 15:02 UTCEPSS rescore
  7. 2026-06-29 14:03 UTCEPSS rescore
  8. 2026-06-28 04:53 UTCEPSS rescore
  9. 2026-06-27 03:05 UTCEPSS rescore
  10. 2026-06-25 13:47 UTCEPSS rescore
  11. 2026-06-24 14:02 UTCEPSS rescore
  12. 2026-06-23 21:30 UTCEPSS rescore
  13. 2026-06-23 06:00 UTCOSV refresh
  14. 2026-06-21 14:54 UTCEPSS rescore
  15. 2026-06-21 14:54 UTCEPSS rescore
  16. 2026-06-21 01:57 UTCEPSS rescore
  17. 2026-06-21 01:57 UTCEPSS rescore
  18. 2026-06-18 17:50 UTCEPSS rescore
  19. 2026-06-18 17:50 UTCEPSS rescore
  20. 2026-06-17 17:50 UTCEPSS rescore
  21. 2026-06-17 17:50 UTCEPSS rescore
  22. 2026-06-16 17:50 UTCEPSS rescore
  23. 2026-06-15 17:45 UTCEPSS rescore
  24. 2026-06-14 23:14 UTCEPSS rescore
  25. 2026-06-14 23:14 UTCEPSS rescore
Show 39 more
  1. 2026-06-13 22:57 UTCEPSS rescore
  2. 2026-06-13 22:57 UTCEPSS rescore
  3. 2026-06-12 23:09 UTCEPSS rescore
  4. 2026-06-11 13:57 UTCEPSS rescore
  5. 2026-06-08 14:14 UTCEPSS rescore
  6. 2026-06-07 15:22 UTCEPSS rescore
  7. 2026-06-07 15:22 UTCEPSS rescore
  8. 2026-06-06 13:45 UTCEPSS rescore
  9. 2026-06-06 13:45 UTCEPSS rescore
  10. 2026-06-06 04:22 UTCOSV refresh
  11. 2026-06-05 22:44 UTCEPSS rescore
  12. 2026-06-05 06:08 UTCEPSS rescore
  13. 2026-06-05 06:08 UTCEPSS rescore
  14. 2026-06-04 13:10 UTCEPSS rescore
  15. 2026-06-04 13:10 UTCEPSS rescore
  16. 2026-06-02 20:10 UTCEPSS rescore
  17. 2026-06-01 13:49 UTCEPSS rescore
  18. 2026-06-01 13:49 UTCEPSS rescore
  19. 2026-05-31 00:14 UTCEPSS rescore
  20. 2026-05-29 13:41 UTCEPSS rescore
  21. 2026-05-28 13:42 UTCEPSS rescore
  22. 2026-05-28 13:42 UTCEPSS rescore
  23. 2026-05-27 13:38 UTCEPSS rescore
  24. 2026-05-27 13:38 UTCEPSS rescore
  25. 2026-05-26 13:42 UTCEPSS rescore
  26. 2026-05-26 13:42 UTCEPSS rescore
  27. 2026-05-26 07:17 UTCEPSS rescore
  28. 2026-05-24 16:44 UTCEPSS rescore
  29. 2026-05-22 13:37 UTCEG score recompute
  30. 2026-05-22 13:37 UTCVendor advisory
  31. 2026-05-22 13:37 UTCGHSA enrichment
  32. 2026-05-20 22:37 UTCEPSS rescore
  33. 2026-05-20 22:37 UTCEPSS rescore
  34. 2026-05-20 22:37 UTCEPSS rescore
  35. 2026-05-20 11:21 UTCEPSS rescore
  36. 2026-05-20 11:21 UTCEPSS rescore
  37. 2026-05-18 21:30 UTCEPSS rescore
  38. 2026-05-18 21:30 UTCEPSS rescore
  39. 2026-05-18 21:30 UTCEPSS rescore

Frequently asked(5)

What is CVE-2016-7055?
CVE-2016-7055 is a medium vulnerability published on May 4, 2017. There is a carry propagating bug in the Broadwell-specific Montgomery multiplication procedure in OpenSSL 1.0.2 and 1.1.0 before 1.1.0c that handles input lengths divisible by, but longer than 256 bits. Analysis suggests that attacks against RSA, DSA and DH private keys are impossible. This is…
When was CVE-2016-7055 disclosed?
CVE-2016-7055 was first published in the National Vulnerability Database on May 4, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2016-7055 actively exploited?
CVE-2016-7055 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 96.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2016-7055?
CVE-2016-7055 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2016-7055?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-7055, 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-7055

Explore →

Is Your Infrastructure Affected by CVE-2016-7055?

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

Start Free Scan →Browse All CVEs