Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
3.7
OpenSSL FIPS Docker images allow private key recovery
published 2 days ago
Summary
The OpenSSL FIPS libraries in certain Docker hardened images do not correctly verify a key during a Diffie‑Hellman exchange. An attacker who supplies a specially crafted key can eventually discover the private key used by the server. Update to the latest OpenSSL FIPS version or apply the vendor’s patch to fix the verification logic.
What to do
The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| Docker Hardened Images:Alpine:3.23 | docker hardened images | openssl-provider-fips | All versions |
| Docker Hardened Images:Alpine:3.24 | docker hardened images | openssl-provider-fips | All versions |
| Docker Hardened Images:Alpine:3.23 | docker hardened images | openssl | All versions |
| Docker Hardened Images:Alpine:3.24 | docker hardened images | openssl | All versions |
| Docker Hardened Images:Debian:13 | docker hardened images | openssl | All versions |
Original advisory text
Issue summary: When EVP_PKEY_derive_set_peer() is called with a DHX (X9.42)
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 membership.
Impact summary: A malicious peer which presents an X9.42 key carrying the
victim's p and g parameters, a forged q = r (a small prime factor of the
cofactor (p−1)/q_local), and a public value Y of order r can recover the
victim's private key after a small number of key exchange attempts.
When EVP_PKEY_derive_set_peer() is called with a DHX (X9.42) peer key, the
subgroup membership check Y^q ≡ 1 (mod p) is performed using the peer's
own q parameter, not the local key's q. The peer's domain parameters are
then matched against the domain parameters of the private key, but the value
of q is not compared.
A malicious peer who presents an X9.42 key carrying the victim's p, g,
a forged q = r (a small prime factor of the cofactor), and a public
value Y of order r passes all checks. The shared secret then takes only
r distinct values, leaking priv mod r. Repeating for each small-prime
factor of the cofactor and combining via CRT recovers the full private
key (Lim–Lee / small-subgroup-confinement attack).
The realistic attack surface is narrow: principally CMP deployments with
long-lived RA/CA DHX keys and bespoke enterprise or government applications
using X9.42 DHX static keys with interactive protocols and therefore this
issue was assigned Low severity.
The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are affected by this
issue.
peer key, the peer key is not properly checked for the subgroup membership.
Impact summary: A malicious peer which presents an X9.42 key carrying the
victim's p and g parameters, a forged q = r (a small prime factor of the
cofactor (p−1)/q_local), and a public value Y of order r can recover the
victim's private key after a small number of key exchange attempts.
When EVP_PKEY_derive_set_peer() is called with a DHX (X9.42) peer key, the
subgroup membership check Y^q ≡ 1 (mod p) is performed using the peer's
own q parameter, not the local key's q. The peer's domain parameters are
then matched against the domain parameters of the private key, but the value
of q is not compared.
A malicious peer who presents an X9.42 key carrying the victim's p, g,
a forged q = r (a small prime factor of the cofactor), and a public
value Y of order r passes all checks. The shared secret then takes only
r distinct values, leaking priv mod r. Repeating for each small-prime
factor of the cofactor and combining via CRT recovers the full private
key (Lim–Lee / small-subgroup-confinement attack).
The realistic attack surface is narrow: principally CMP deployments with
long-lived RA/CA DHX keys and bespoke enterprise or government applications
using X9.42 DHX static keys with interactive protocols and therefore this
issue was assigned Low severity.
The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are affected by this
issue.
References
- https://scout.docker.com/v/DHI-pmdt-hwsw-p2c3-b4zu Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2026-42770 Vendor Advisory
- https://openssl-library.org/news/secadv/20260609.txt Vendor Advisory
- https://github.com/openssl/openssl/commit/ca2237ab5615641b662183b077f62c08d75e80... Patch
- https://github.com/openssl/openssl/commit/7fbfde7677ed8808828bf00ff01c937ca04bdd... Patch
- https://github.com/openssl/openssl/commit/5f452bba2c681423d8fcffd120a19b757ee42e... Patch
- https://github.com/openssl/openssl/commit/3ddbb7ab50bd93dfc59cbe08e269a67605aeeb... Patch
- https://github.com/openssl/openssl/commit/3da5a516cd2635a320ff748503db2cef7c4b0f... Patch
- https://errata.almalinux.org/9/ALSA-2026-25239.html Vendor Advisory
- https://access.redhat.com/errata/RHSA-2026:25239 Vendor Advisory
- https://security.alpinelinux.org/vuln/CVE-2026-42770 Vendor Advisory
- https://alas.aws.amazon.com/AL2023/ALAS-2026-1853.html Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-9076 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-7383 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-45447 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-45446 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-45445 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-42770 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-42769 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-42768 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-42767 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-42766 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-42764 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-34183 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-34182 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-34181 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-34180 Vendor Advisory
- https://security-tracker.debian.org/tracker/CVE-2026-42770 Vendor Advisory
- https://linux.oracle.com/cve/ELSA-2026-25237.html Vendor Advisory
- https://linux.oracle.com/errata/ELSA-2026-25237.html Vendor Advisory
- https://linux.oracle.com/cve/ELSA-2026-25239.html Vendor Advisory
- https://linux.oracle.com/errata/ELSA-2026-25239.html Vendor Advisory
- https://linux.oracle.com/cve/ELSA-2026-50379.html Vendor Advisory
- https://linux.oracle.com/errata/ELSA-2026-50379.html Vendor Advisory
- https://access.redhat.com/security/cve/CVE-2026-42770 Vendor Advisory
- https://errata.rockylinux.org/RLSA-2026:25237 Vendor Advisory
- https://errata.rockylinux.org/RLSA-2026:25239 Vendor Advisory
- https://ubuntu.com/security/CVE-2026-42770 Vendor Advisory
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2026-42770 Vendor Advisory
Internet-facing
14 days
Internal
60 days
- Not known to be exploited
- Can be exploited automatically (estimated)
- Gives an attacker partial control (estimated)
Timeline
Published20 Nov 2026
Updated20 Nov 2026
First seen20 Nov 2026
Sources
DHI-pmdt-hwsw-p2c3-b4zu · OSV
Track software like this
Free during beta