CVE-2026-87732

MEDIUMPre-NVD 6.26.2—
EchelonGraph scoreHIGH confidence

Score 6.2 from GitHub Security Advisory published 2026-09-09. a secondary CVSS source baseline 6.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
6.2EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.2Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.2
EG Score
6.2(high)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity62% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
0%
KEV
Not listed

Published

September 9, 2026

Last Modified

September 9, 2026

Advisory Details (1)

Auto-updated Sep 9, 2026
No patch confirmed yet.
generic

OSV - Open Source Vulnerabilities

https://osv.dev/vulnerability/OSEC-2026-12

Vendor Advisories for CVE-2026-87732(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 16× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 17:27 UTCEG score recompute
  2. 2026-09-19 17:27 UTCGHSA enrichment
  3. 2026-09-18 19:31 UTCEG score recompute
  4. 2026-09-18 19:31 UTCGHSA enrichment
  5. 2026-09-18 19:28 UTCEPSS rescore
  6. 2026-09-17 21:32 UTCEG score recompute
  7. 2026-09-17 21:32 UTCGHSA enrichment
  8. 2026-09-17 19:32 UTCEPSS rescore
  9. 2026-09-16 23:36 UTCEG score recompute
  10. 2026-09-16 23:36 UTCGHSA enrichment
  11. 2026-09-16 14:09 UTCEPSS rescore
  12. 2026-09-16 05:15 UTCEPSS rescore
  13. 2026-09-16 01:40 UTCGHSA enrichment
  14. 2026-09-15 03:44 UTCGHSA enrichment
  15. 2026-09-14 05:48 UTCGHSA enrichment
  16. 2026-09-13 07:52 UTCGHSA enrichment
  17. 2026-09-12 09:57 UTCEG score recompute
  18. 2026-09-12 09:57 UTCGHSA enrichment
  19. 2026-09-11 14:53 UTCEPSS rescore
  20. 2026-09-11 14:53 UTCEPSS rescore
  21. 2026-09-11 12:01 UTCGHSA enrichment
  22. 2026-09-10 14:04 UTCEG score recompute
  23. 2026-09-10 14:04 UTCGHSA enrichment
  24. 2026-09-09 16:08 UTCGHSA enrichment
  25. 2026-09-09 14:28 UTCEG score recompute
Show 6 more
  1. 2026-09-09 14:28 UTCGHSA enrichment
  2. 2026-09-09 13:37 UTCEG score recompute
  3. 2026-09-09 13:36 UTCGHSA enrichment
  4. 2026-09-09 05:25 UTCEG score recompute
  5. 2026-09-09 04:26 UTCEG score recompute
  6. 2026-09-09 04:26 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-87732?
CVE-2026-87732 is a medium vulnerability published on September 9, 2026. An issue was discovered in the mirage-crypto package before 2.2.0 for OCaml. The AES.GCM.authenticatedecryptinto and Chacha20.authenticatedecryptinto functions write the decrypted plaintext into a caller-provided buffer and only then compares the tag. On a forged tag, the functions returns false,…
When was CVE-2026-87732 disclosed?
CVE-2026-87732 was first published in the National Vulnerability Database on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-87732 actively exploited?
CVE-2026-87732 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 99.9% of all scored CVEs.
What is the CVSS score of CVE-2026-87732?
CVE-2026-87732 has a CVSS v3 base score of 6.2 (NVD).
How do I remediate CVE-2026-87732?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-87732, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-87732

Explore →

Is Your Infrastructure Affected by CVE-2026-87732?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs