Microsoft security update for CVE-2025-68972
🔗 CVE IDs covered (1)
📋 Microsoft's advisory
EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-68972. This page also shows what EchelonGraph holds for CVE-2025-68972, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.
🎯 Affected products5
- azl3 gnupg2 2.4.7-1 on Azure Linux 3.0
- cbl2 gnupg2 2.4.0-2 on CBL Mariner 2.0
- cbl2 gnupg2 2.4.0-3
- cbl2 gnupg2 2.4.0-3 on CBL Mariner 2.0
- cbl2 gnupg2 2.4.0-3 on CBL-Mariner 2.0
✅ Updates Microsoft lists: 2 updates
2 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.
| KB article | Update | Fixed build |
|---|---|---|
| — | Security Update | 2.4.9-1 |
| — | Security Update | — |
🧭 EchelonGraph on CVE-2025-68972
- EchelonGraph score
- 5.9 MEDIUM
- CISA KEV
- Not listed
- Fix status
- A fix is available — apply it.
Description from the CVE record (CVE.org), as published by its numbering authority
In GnuPG through 2.4.8, if a signed message has \f at the end of a plaintext line, an adversary can construct a modified message that places additional text after the signed material, such that signature verification of the modified message succeeds (although an "invalid armor" message is printed during verification). This is related to use of \f as a marker to denote truncation of a long plaintext line.
Published by MITRE Corporation, the CVE Numbering Authority that assigned CVE-2025-68972, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).