# CVE-2026-57062: Other in GnuPG > GnuPG's gpgsm incorrectly accepts short AES-GCM integrity tags, potentially allowing attackers to bypass cryptographic integrity checks. - **Severity:** Low 2.9 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N`) - **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 Jun 2026 - **Updated:** 23 Jun 2026 - **Also known as:** AZL-91170, BELL-CVE-2026-57062, CLSA-2026-1785557084, CLSA-2026-1786609750, DEBIAN-CVE-2026-57062, ECHO-89c6-c3e9-d8d2, GHSA-m6x2-4hhh-669j, JLSEC-2026-1084, OESA-2026-2858, OESA-2026-2859, OESA-2026-2860, RHSA-2026:82418, SUSE-SU-2026:22757-1, SUSE-SU-2026:22825-1, SUSE-SU-2026:22923-1, SUSE-SU-2026:23007-1, SUSE-SU-2026:3243-1, UBUNTU-CVE-2026-57062, USN-8720-1, openSUSE-SU-2026:11213-1, openSUSE-SU-2026:21385-1 ## What is CVE-2026-57062? CVE-2026-57062 is a low-severity vulnerability in GnuPG, published on 23 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description CMS (Cryptographic Message Syntax) parsing in gpgsm in GnuPG through 2.5.20 mishandles the CMS format for AES-GCM because aes-ICVlen is supposed to be 12 bytes but 4 bytes is accepted. NOTE: this is related to CVE-2026-34182. Weakness: CWE-1284 (Improper Validation of Specified Quantity in Input) ## Which versions are affected by CVE-2026-57062? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `gnupg2` | Red Hat:hummingbird:1 | All versions | 0:2.4.9-18.3.hum1 | | `gnupg2-dirmngr` | Red Hat:hummingbird:1 | All versions | 0:2.4.9-18.3.hum1 | | `gnupg2-g13` | Red Hat:hummingbird:1 | All versions | 0:2.4.9-18.3.hum1 | | `gnupg2-gpg-agent` | Red Hat:hummingbird:1 | All versions | 0:2.4.9-18.3.hum1 | | `gnupg2-gpgconf` | Red Hat:hummingbird:1 | All versions | 0:2.4.9-18.3.hum1 | | `gnupg2-keyboxd` | Red Hat:hummingbird:1 | All versions | 0:2.4.9-18.3.hum1 | | `gnupg2-scdaemon` | Red Hat:hummingbird:1 | All versions | 0:2.4.9-18.3.hum1 | | `gnupg2-smime` | Red Hat:hummingbird:1 | All versions | 0:2.4.9-18.3.hum1 | | `gnupg2-utils` | Red Hat:hummingbird:1 | All versions | 0:2.4.9-18.3.hum1 | | `gnupg2-verify` | Red Hat:hummingbird:1 | All versions | 0:2.4.9-18.3.hum1 | | `gnupg2-wks` | Red Hat:hummingbird:1 | All versions | 0:2.4.9-18.3.hum1 | | `gpg2` | SUSE:Linux Enterprise Module for Basesystem 15 SP7 | All versions | 2.4.4-150600.3.18.1 | | `gpg2` | SUSE:Linux Enterprise Server 16.0 | All versions | 2.5.5-160000.6.1 | | `gpg2` | SUSE:Linux Enterprise Server for SAP applications 16.0 | All versions | 2.5.5-160000.6.1 | | `gpg2` | SUSE:Linux Micro 6.0 | All versions | 2.4.4-9.1 | | `gpg2` | SUSE:Linux Micro 6.1 | All versions | 2.4.4-slfo.1.1_9.1 | | `gpg2` | SUSE:Linux Micro 6.2 | All versions | 2.5.5-160000.6.1 | | `gpg2` | openSUSE:Leap 16.0 | All versions | 2.5.5-160000.6.1 | | `gpg2` | openSUSE:Tumbleweed | All versions | 2.5.21-1.1 | ## How do I fix CVE-2026-57062? Upgrade to a fixed version. ## Is CVE-2026-57062 being exploited? There is no known exploitation of CVE-2026-57062 in the wild and no public exploit code. Public exploit code: - gpgsm CVE-2026-57062 exploit POC (github_poc): https://github.com/goldendivider/gpgsm-cve-2026-57062-cms-gcm-short-tag ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-57062 and fix it if it is affected. What it is: CVE-2026-57062 is a low-severity vulnerability in GnuPG, published on 23 Jun 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-57062 in the wild and no public exploit code. Affected product: GnuPG. 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-57062/ (Markdown: https://insights.sbomify.com/CVE-2026-57062/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-57062 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-57062 - OSV: https://osv.dev/vulnerability/CVE-2026-57062 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-57062/ Summaries are generated and may contain mistakes; the official description above is the record.