Unverified plaintext processing via late tag validation
Published Sep 9, 2026 · Updated Sep 9, 2026
Improper verification in OCaml mirage-crypto before 2.2.0 allows local users to place unverified plaintext in output buffers. The affected AES GCM, AES CCM16, and ChaCha20 decrypt-into functions write decrypted data to the destination before validating the AEAD tag. Reachability requires a caller to invoke an affected API with forged input and consume the destination despite a false result, allowing unauthenticated data to enter later processing.
Summary
What happened
Improper verification in OCaml mirage-crypto before 2.2.0 allows local users to place unverified plaintext in output buffers. The affected AES GCM, AES CCM16, and ChaCha20 decrypt-into functions write decrypted data to the destination before validating the AEAD tag. Reachability requires a caller to invoke an affected API with forged input and consume the destination despite a false result, allowing unauthenticated data to enter later processing.
The record
- CVE
- CVE-2026-87732
- Published
- Sep 9, 2026
- Updated
- Sep 9, 2026
- Vendor
- OCaml
- Product
- mirage-crypto
- Classifications
- CWE-347
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 9, 2026CVE publishedPublication date reported by the CVE source.
- Sep 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2.2.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- OSEC-2026-12 AEAD forged-tag reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo