← Back to results
Vulnerability record · public intelligence
CVE-2026-57062
LOW

CVE-2026-57062

Published Jun 23, 2026 · Updated Nov 3, 2026

Severity · CVSSLOW · Not scored
Known exploitationNot listed
EPSS / likelihood0.15%
QFinch risk scoreNot available

Original summary

Normalized public record · Updated Nov 3, 2026

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.

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

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.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

FIRST-EPSSCVE-LIST-V5
SSVC priority
LOW
Confidence
Not available
Aliases
None reported

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. blog.calif.io ↗
  2. www.gnupg.org ↗

Record history

Published Jun 23, 2026 · Last refreshed Nov 3, 2026