CVE-2017-7526: Infoleak

Published Jul 26, 2018
·
Updated

Last updated 25 August 2025

Other sources

libgcrypt before version 1.7.8 is vulnerable to a cache side-channel attack resulting into a complete break of RSA-1024 while using the left-to-right method for computing the sliding-window expansion. The same attack is believed to work on RSA-2048 with moderately more computation. This side-channel requires that attacker can run arbitrary software on the hardware where the private RSA key is used.

Launchpad

Affected Software

9 affected componentsFixes available
gnupg Libgcrypt<1.7.8
Canonical Ubuntu Linux=12.04
Canonical Ubuntu Linux=14.04
Canonical Ubuntu Linux=16.04
Debian Debian Linux=8.0
Debian Debian Linux=9.0
debian/gnupg1
1.4.23-1.11.4.23-3
debian/gnupg2
2.2.27-2+deb11u22.2.40-1.1+deb12u12.4.7-212.4.8-4
debian/libgcrypt20
1.8.7-61.10.1-31.11.0-71.11.2-3

Event History

Jul 26, 2018
CVE Published
via MITRE·01:00 PM
Data Sourced
via MITRE·01:00 PM
DescriptionSeverityWeakness
Jan 11, 2024
Data Sourced
via Launchpad·10:40 PM
Description
Dec 18, 2025
Data Sourced
via Ubuntu·10:18 PM
RemedyDescriptionSeverityAffected Software
Data Sourced
via Debian·10:18 PM
DescriptionAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2017-7526?

CVE-2017-7526 has been classified as a high severity vulnerability due to its potential to allow complete breakage of RSA-1024 and RSA-2048 implementations.

2

How do I fix CVE-2017-7526?

To mitigate CVE-2017-7526, upgrade to libgcrypt version 1.7.8 or later along with relevant updates to affected software packages.

3

Which software is affected by CVE-2017-7526?

CVE-2017-7526 affects libgcrypt versions before 1.7.8, as well as specific versions of gnupg1 and gnupg2 on Debian and Ubuntu distributions.

4

What impact does CVE-2017-7526 have on RSA encryption?

CVE-2017-7526 allows attackers to exploit cache side-channel vulnerabilities that can completely break RSA encryption implementations using affected versions.

5

When was CVE-2017-7526 disclosed?

CVE-2017-7526 was disclosed on July 24, 2024, although the vulnerability itself has existed in libgcrypt versions prior to 1.7.8.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203