# CVE-2017-7526: Information disclosure in libgcrypt > A cache side-channel attack in libgcrypt allows local attackers to recover RSA private keys by running arbitrary software on the target hardware. - **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 26 Jul 2018 - **Updated:** 17 Dec 2025 - **Also known as:** ALPINE-CVE-2017-7526, AZL-41702, DEBIAN-CVE-2017-7526, DLA-1015-1, DLA-1080-1, DSA-3901-1, DSA-3960-1, GHSA-f2v5-c455-qhg2, MGASA-2017-0213, MGASA-2017-0235, SUSE-SU-2017:1793-1, SUSE-SU-2017:1794-1, SUSE-SU-2017:1866-1, UBUNTU-CVE-2017-7526, USN-3733-1 ## What is CVE-2017-7526? CVE-2017-7526 is a medium-severity vulnerability in Canonical Ubuntu Linux, published on 26 Jul 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description 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. Weakness: CWE-310, CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) ## Which versions are affected by CVE-2017-7526? It affects 3 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `libgcrypt` | SUSE:Linux Enterprise Desktop 12 SP2 | All versions | 1.6.1-16.42.1 | | `compat-libgcrypt11` | SUSE:Linux Enterprise Module for Legacy 12 | All versions | 1.5.0-0.6.1 | | `libgcrypt` | SUSE:Linux Enterprise Server 11 SP4 | All versions | 1.5.0-0.25.1 | | `libgcrypt` | SUSE:Linux Enterprise Server 12 SP2 | All versions | 1.6.1-16.42.1 | | `libgcrypt` | SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2 | All versions | 1.6.1-16.42.1 | | `libgcrypt` | SUSE:Linux Enterprise Server for SAP Applications 11 SP4 | All versions | 1.5.0-0.25.1 | | `libgcrypt` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 1.6.1-16.42.1 | | `libgcrypt` | SUSE:Linux Enterprise Software Development Kit 11 SP4 | All versions | 1.5.0-0.25.1 | | `libgcrypt` | SUSE:Linux Enterprise Software Development Kit 12 SP2 | All versions | 1.6.1-16.42.1 | Products: Canonical Ubuntu Linux, Debian Debian Linux, Gnupg Libgcrypt. ## How do I fix CVE-2017-7526? Upgrade to a fixed version. ## Is CVE-2017-7526 being exploited? There is no known exploitation of CVE-2017-7526 in the wild and no public exploit code. ## Other vulnerabilities in Canonical Ubuntu Linux - [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild) - [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild) - [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild) - [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild) - [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2017-7526 and fix it if it is affected. What it is: CVE-2017-7526 is a medium-severity vulnerability in Canonical Ubuntu Linux, published on 26 Jul 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2017-7526 in the wild and no public exploit code. Affected product: Canonical Ubuntu Linux. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2017-7526/ (Markdown: https://insights.sbomify.com/CVE-2017-7526/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2017-7526 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-7526 - OSV: https://osv.dev/vulnerability/CVE-2017-7526 --- From sbomify Insights: https://insights.sbomify.com/CVE-2017-7526/ Summaries are generated and may contain mistakes; the official description above is the record.