🛡️ OSEC-2026-15 — mirage-crypto-ec
Description
EC public key out of bounds read
The internal Point.of_octets function is missing a length check for compressed
points, and thus is raising an exception when a short buffer is provided. This
affects all NIST curves (P-256, P-384, P-521) and both Dsa.pub_of_octets and
Dh.key_exchange functions.
Fix
The fix is to check the length of the provided buffer.
Timeline
- July 28th 2026: report to security@ocaml.org
- August 7th: release of mirage-crypto-pk 2.3.0 and security advisory
How this vulnerability can be exploited
This issue can be reached over the network, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability low.
Affected software
OSEC-2026-15 is recorded against 1 package.
- mirage-crypto-ec (fixed in 2.3.0)
Timeline and source
Published on 7 August 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.
Details
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| mirage-crypto-ec | — | 2.3.0 |
References
N/ASimilar Threats
- Unknown OSEC-2026-13
More OSEC 2026 advisories
Browse all of OSEC 2026 in the advisory index.
Free Vulnerability Check
Is your site affected by OSEC-2026-15?
BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against OSEC-2026-15 and other known CVE records.
Scan My Site Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.