CVE-2025-69277MediumMicrosoft CVSS 4.5CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N/E:U

Microsoft security update for CVE-2025-69277

Published
January 3, 2026
Last Modified
—

🔗 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-69277. This page also shows what EchelonGraph holds for CVE-2025-69277, 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 products4

  • azl3 libsodium 1.0.19-1 on Azure Linux 3.0
  • azl3 libsodium 1.0.19-2 on Azure Linux 3.0
  • cbl2 libsodium 1.0.18-6 on CBL Mariner 2.0
  • cbl2 libsodium 1.0.18-7 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 articleUpdateFixed build
—Security Update1.0.19-2
—Security Update1.0.18-7

🧭 EchelonGraph on CVE-2025-69277

EchelonGraph score
4.5 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

libsodium before ad3004e, in atypical use cases involving certain custom cryptography or untrusted data to crypto_core_ed25519_is_valid_point, mishandles checks for whether an elliptic curve point is valid because it sometimes allows points that aren't in the main cryptographic group.

Published by MITRE Corporation, the CVE Numbering Authority that assigned CVE-2025-69277, 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).

🔗 References (2)