{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-41990 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-41990 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-41990 in the wild and no public exploit code.\n\nAffected product: gnupg Libgcrypt. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-41990/ (Markdown: https://insights.sbomify.com/CVE-2026-41990/index.md)","id":"CVE-2026-41990","markdown":"https://insights.sbomify.com/CVE-2026-41990/index.md","name":"CVE-2026-41990","record":{"aliases":["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"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Libgcrypt crypto library","requires_auth":"none","summary":"Libgcrypt mishandles Dilithium signing with unchecked static array writes, potentially causing crashes or memory corruption.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"libgcrypt","vendor":"gnupg"}],"cvss":{"score":4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"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.","ecosystems":["SUSE:Linux Enterprise Server 16.0","SUSE:Linux Enterprise Server for SAP applications 16.0","SUSE:Linux Micro 6.2","openSUSE:Leap 16.0"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Memory corruption in Libgcrypt","id":"CVE-2026-41990","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":4,"n_references":3,"next":{"headline":"Predictable Temporary File in GNU gzip","id":"CVE-2026-41991"},"packages":[{"ecosystem":"SUSE:Linux Enterprise Server 16.0","fixed":["1.12.1-160000.2.1"],"introduced":["0"],"last_affected":[],"package":"libgcrypt","purl":"pkg:rpm/suse/libgcrypt\u0026distro=SUSE%20Linux%20Enterprise%20Server%2016.0","source":"SUSE-SU-2026:22355-1"},{"ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","fixed":["1.12.1-160000.2.1"],"introduced":["0"],"last_affected":[],"package":"libgcrypt","purl":"pkg:rpm/suse/libgcrypt\u0026distro=SUSE%20Linux%20Enterprise%20Server%20for%20SAP%20applications%2016.0","source":"SUSE-SU-2026:22355-1"},{"ecosystem":"SUSE:Linux Micro 6.2","fixed":["1.12.1-160000.2.1"],"introduced":["0"],"last_affected":[],"package":"libgcrypt","purl":"pkg:rpm/suse/libgcrypt\u0026distro=SUSE%20Linux%20Micro%206.2","source":"SUSE-SU-2026:22270-1"},{"ecosystem":"openSUSE:Leap 16.0","fixed":["1.12.1-160000.2.1"],"introduced":["0"],"last_affected":[],"package":"libgcrypt","purl":"pkg:rpm/opensuse/libgcrypt\u0026distro=openSUSE%20Leap%2016.0","source":"openSUSE-SU-2026:21047-1"}],"prev":{"headline":"Memory corruption in Libgcrypt","id":"CVE-2026-41989"},"products":["Libgcrypt"],"published":"2026-04-23","related":[{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2021-3345","kev_date_added":null,"published":"2021-01-29"},{"cvss_score":7.5,"headline":"Weak cryptography in n/a","id":"CVE-2018-6829","kev_date_added":null,"published":"2018-02-07"},{"cvss_score":6.7,"headline":"Memory corruption in Libgcrypt","id":"CVE-2026-41989","kev_date_added":null,"published":"2026-04-23"},{"cvss_score":5.9,"headline":"Weak cryptography in n/a","id":"CVE-2021-40528","kev_date_added":null,"published":"2021-09-06"},{"cvss_score":5.9,"headline":"Information disclosure in n/a","id":"CVE-2019-12904","kev_date_added":null,"published":"2019-06-19"},{"cvss_score":5.9,"headline":"Information disclosure in n/a","id":"CVE-2017-9526","kev_date_added":null,"published":"2017-06-11"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"SUSE"},{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-23","vendors":["gnupg"]},"summary":"Libgcrypt mishandles Dilithium signing with unchecked static array writes, potentially causing crashes or memory corruption.","url":"https://insights.sbomify.com/CVE-2026-41990/"}