Improper Verification of Cryptographic Signature Affecting ocaml-mirage-crypto package, versions <2.2.0-1


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.11% (2nd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-DEBIANUNSTABLE-OCAMLMIRAGECRYPTO-19654151
  • published9 Sept 2026
  • disclosed9 Sept 2026

Introduced: 9 Sep 2026

CVE-2026-87732  (opens in a new tab)
CWE-347  (opens in a new tab)

How to fix?

Upgrade Debian:unstable ocaml-mirage-crypto to version 2.2.0-1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream ocaml-mirage-crypto package and not the ocaml-mirage-crypto package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

An issue was discovered in the mirage-crypto package before 2.2.0 for OCaml. The AES.GCM.authenticate_decrypt_into and Chacha20.authenticate_decrypt_into functions write the decrypted plaintext into a caller-provided buffer and only then compares the tag. On a forged tag, the functions returns false, but the destination buffer already holds the full plaintext.