# CVE-2026-41990: Memory corruption in Libgcrypt

> Libgcrypt mishandles Dilithium signing with unchecked static array writes, potentially causing crashes or memory corruption.

- **Severity:** Medium 4.0 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Apr 2026
- **Updated:** 23 Apr 2026
- **Also known as:** BELL-CVE-2026-41990, DEBIAN-CVE-2026-41990, GHSA-78pv-qq8x-94px, JLSEC-2026-497, SUSE-SU-2026:22270-1, SUSE-SU-2026:22355-1, UBUNTU-CVE-2026-41990, openSUSE-SU-2026:21047-1

## What is CVE-2026-41990?

CVE-2026-41990 is a medium-severity memory corruption vulnerability in gnupg Libgcrypt, published on 23 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Libgcrypt before 1.12.2 mishandles Dilithium signing. Writes to a static array lack a bounds check but do not use attacker-controlled data.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2026-41990?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libgcrypt` | SUSE:Linux Enterprise Server 16.0 | All versions | 1.12.1-160000.2.1 |
| `libgcrypt` | SUSE:Linux Enterprise Server for SAP applications 16.0 | All versions | 1.12.1-160000.2.1 |
| `libgcrypt` | SUSE:Linux Micro 6.2 | All versions | 1.12.1-160000.2.1 |
| `libgcrypt` | openSUSE:Leap 16.0 | All versions | 1.12.1-160000.2.1 |

Products: Gnupg Libgcrypt.

## How do I fix CVE-2026-41990?

Upgrade to a fixed version.

## Is CVE-2026-41990 being exploited?

There is no known exploitation of CVE-2026-41990 in the wild and no public exploit code.

## Other vulnerabilities in gnupg Libgcrypt

- [CVE-2021-3345](https://insights.sbomify.com/CVE-2021-3345/): Memory corruption in n/a (high 7.8)
- [CVE-2018-6829](https://insights.sbomify.com/CVE-2018-6829/): Weak cryptography in n/a (high 7.5)
- [CVE-2026-41989](https://insights.sbomify.com/CVE-2026-41989/): Memory corruption in Libgcrypt (medium 6.7)
- [CVE-2021-40528](https://insights.sbomify.com/CVE-2021-40528/): Weak cryptography in n/a (medium 5.9)
- [CVE-2019-12904](https://insights.sbomify.com/CVE-2019-12904/): Information disclosure in n/a (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-41990 and fix it if it is affected.

What it is: CVE-2026-41990 is a medium-severity memory corruption vulnerability in gnupg Libgcrypt, published on 23 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-41990 in the wild and no public exploit code.

Affected product: gnupg Libgcrypt. 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-2026-41990/ (Markdown: https://insights.sbomify.com/CVE-2026-41990/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41990
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41990
- OSV: https://osv.dev/vulnerability/CVE-2026-41990

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-41990/
Summaries are generated and may contain mistakes; the official description above is the record.