Potential Plaintext Exposure from Forged Tag in Mirage-Crypto AES/GCM and ChaCha20 Decrypt Functions
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| OCaml | mirage-crypto | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Ocaml | Mirage-crypto-pk |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.107% probability within 30 days)
| Link | Providers |
|---|---|
| https://osv.dev/vulnerability/OSEC-2026-12 |
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Ocaml
Ocaml mirage-crypto-pk |
|
| Vendors & Products |
Ocaml
Ocaml mirage-crypto-pk |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Potential Plaintext Exposure from Forged Tag in Mirage-Crypto AES/GCM and ChaCha20 Decrypt Functions |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Weaknesses | CWE-347 | |
| References |
| |
| Metrics |
cvssV3_1
|