Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…
EPSS 0.1%top 99%

CVE-2026-87733: CWE-295 Improper Certificate Validation in OCaml mirage-crypto-ec

0
Medium
Published: 09/09/2026 (09/09/2026, 04:08:54 UTC)
Source: GCVE Database
Vendor/Project: OCaml
Product: mirage-crypto-ec

Description

An issue was discovered in the mirage-crypto-ec function before 2.2.0 for OCaml. The ECDSA functions {P256,P384,P521}.Dsa.pub_of_octets accept 0x00, the encoding of the point at infinity, as a public key. With that public key, signatures can be forged without a private key.

CVSS v3.1

Score 6.2medium

Attack Vector
Local
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected software

github.com/mirage/mirage-crypto-ec
pkg:golang/github.com/mirage/mirage-crypto-ec
Affected versions
<2.2.0

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 09/09/2026, 13:57:07 UTC

Technical Analysis

The mirage-crypto-ec library versions prior to 2.2.0 contain a cryptographic flaw in the ECDSA implementation. Specifically, the functions pub_of_octets for the P256, P384, and P521 curves accept 0x00, which encodes the point at infinity, as a valid public key. This acceptance enables signature forgery without the need for the corresponding private key, undermining the integrity guarantees of ECDSA signatures.

Potential Impact

An attacker can forge ECDSA signatures without access to the private key, compromising the authenticity and integrity of messages or data signed using the affected library versions. There is no impact on confidentiality or availability reported.

Mitigation Recommendations

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Users should upgrade to mirage-crypto-ec version 2.2.0 or later once available or apply any official fixes provided by the vendor. Until then, avoid using affected versions for critical signature verification.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
GHSA-5v5p-5xxr-9xf8
Osv Schema Version
1.4.0
Aliases
["CVE-2026-87733"]
Ecosystems
[]
Database Specific Severity
MODERATE
Cvss Version
3.1

Threat ID: 6aa15f7bacd9273b4961836a

Added to database: 09/09/2026, 13:30:35 UTC

Last enriched: 09/09/2026, 13:57:07 UTC

Last updated: 09/10/2026, 00:52:02 UTC

Views: 3

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses