Issue summary: When EVP_PKEY_derive_set_peer() is called with a DHX (X9.42) peer key, the peer key is not properly checked for the subgroup… (CVE-2026-42770)
A vulnerability exists in EVP_PKEY_derive_set_peer() when called with a DHX (X9.42) peer key, where the peer key's subgroup membership is not properly verified. This allows a malicious peer to use crafted domain parameters to leak the victim's private key through a small-subgroup confinement attack. The issue primarily affects deployments using long-lived DHX keys in CMP or bespoke applications. The severity is considered low due to the narrow attack surface.
AI Analysis
Technical Summary
The vulnerability arises because EVP_PKEY_derive_set_peer() performs the subgroup membership check using the peer's q parameter instead of the local key's q, and does not compare the q values between peer and local keys. A malicious peer can present an X9.42 key with the victim's p and g parameters but a forged small prime q, and a public value Y of order r (a small prime factor). This causes the shared secret to leak partial private key information mod r. By repeating this for each small prime factor of the cofactor and combining results via the Chinese Remainder Theorem, the full private key can be recovered. The affected FIPS modules include versions 4.0, 3.6, 3.5, 3.4, and 3.0. The attack surface is limited to specific use cases involving static DHX keys in interactive protocols.
Potential Impact
An attacker who can act as a malicious peer in a key exchange using DHX (X9.42) keys can recover the victim's private key after a small number of attempts by exploiting improper subgroup membership checks. This compromises the confidentiality of the victim's private key in affected deployments. The impact is limited by the narrow attack surface, mainly affecting certain CMP deployments and bespoke applications using static DHX keys.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, avoid using DHX (X9.42) static keys in interactive protocols or long-lived RA/CA DHX keys in CMP deployments. Monitor vendor communications for updates and apply official patches once released.
Issue summary: When EVP_PKEY_derive_set_peer() is called with a DHX (X9.42) peer key, the peer key is not properly checked for the subgroup… (CVE-2026-42770)
Description
A vulnerability exists in EVP_PKEY_derive_set_peer() when called with a DHX (X9.42) peer key, where the peer key's subgroup membership is not properly verified. This allows a malicious peer to use crafted domain parameters to leak the victim's private key through a small-subgroup confinement attack. The issue primarily affects deployments using long-lived DHX keys in CMP or bespoke applications. The severity is considered low due to the narrow attack surface.
CVSS v3.1
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability arises because EVP_PKEY_derive_set_peer() performs the subgroup membership check using the peer's q parameter instead of the local key's q, and does not compare the q values between peer and local keys. A malicious peer can present an X9.42 key with the victim's p and g parameters but a forged small prime q, and a public value Y of order r (a small prime factor). This causes the shared secret to leak partial private key information mod r. By repeating this for each small prime factor of the cofactor and combining results via the Chinese Remainder Theorem, the full private key can be recovered. The affected FIPS modules include versions 4.0, 3.6, 3.5, 3.4, and 3.0. The attack surface is limited to specific use cases involving static DHX keys in interactive protocols.
Potential Impact
An attacker who can act as a malicious peer in a key exchange using DHX (X9.42) keys can recover the victim's private key after a small number of attempts by exploiting improper subgroup membership checks. This compromises the confidentiality of the victim's private key in affected deployments. The impact is limited by the narrow attack surface, mainly affecting certain CMP deployments and bespoke applications using static DHX keys.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, avoid using DHX (X9.42) static keys in interactive protocols or long-lived RA/CA DHX keys in CMP deployments. Monitor vendor communications for updates and apply official patches once released.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-3cxm-476w-ghm2
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-42770"]
- Ecosystems
- []
- Database Specific Severity
- LOW
- Cvss Version
- 3.1
Threat ID: 6a5e79ed2a4a8d59899bb919
Added to database: 07/20/2026, 19:41:33 UTC
Last enriched: 07/20/2026, 19:47:04 UTC
Last updated: 07/21/2026, 09:37:01 UTC
Views: 10
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
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
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.