Security Resilience

CVE-2026-42789

Crypto Weakness in Erlang\/Otp 17.0 – 26.2.5.21

Published
27 May 2026
Modified
26 October 2026
Patch / advisory
CVSS Score v4 7.0
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:H/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0038 32th percentile
Risk Priority 41 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-42789 is a high-severity Improper Certificate Validation (CWE-295) vulnerability in Erlang\/Otp. Its CVSS base score is 7.0 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Masquerading (T1036); ranked at the 32th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-17 (Public Key Infrastructure Certificates) and SC-23 (Session Authenticity) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Improper Following of a Certificate's Chain of Trust vulnerability in Erlang OTP public_key (pubkey_cert module) allows a non-CA certificate to be accepted as an intermediate issuer, enabling certificate chain forgery. In lib/public_key/src/pubkey_cert.erl, pubkey_cert:validate_extensions/7 contains two flaws that together allow a…

more

certificate with basicConstraints cA:false and no keyUsage extension to be used as an intermediate issuer in a chain passed to public_key:pkix_path_validation/3: the cA:false clause recurses into the remaining extensions without rejecting the certificate when it is in issuer position, and the keyUsage check only fires when the extension is present, so a certificate lacking keyUsage entirely bypasses the keyCertSign enforcement. Any party holding an end-entity certificate with basicConstraints cA:false and no keyUsage extension, issued by any CA in the victim's trust store, can use that certificate's private key to sign forged leaf certificates for arbitrary identities. public_key:pkix_path_validation/3 accepts the resulting chain, and by extension every TLS or mTLS endpoint built on the OTP ssl application that relies on the default verifier is affected, including server identity verification on the client side and client certificate verification on mTLS servers. This issue affects OTP from OTP 17.0 before OTP 27.3.4.19, OTP 28.5.0.8, and OTP 29.1.2, corresponding to public_key from 0.22 before 1.17.1.7, 1.20.3.6, and 1.21.8. Whether OTP before OTP 17.0, corresponding to public_key before 0.22, is affected is unknown.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1036 Masquerading Stealth
Adversaries may attempt to manipulate features of their artifacts to make them appear legitimate or benign to users and/or security tools.
T1001.003 Protocol or Service Impersonation Command And Control
Adversaries may impersonate legitimate protocols or web service traffic to disguise command and control activity and thwart analysis efforts.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1195 Supply Chain Compromise Initial Access
Adversaries may manipulate products or product delivery mechanisms prior to receipt by a final consumer for the purpose of data or system compromise.
T1195.002 Compromise Software Supply Chain Initial Access
Adversaries may manipulate application software prior to receipt by a final consumer for the purpose of data or system compromise.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-42791Same product: Erlang Erlang\/Otp
CVE-2026-42790Same product: Erlang Erlang\/Otp
CVE-2026-28810Same product: Erlang Erlang\/Otp
CVE-2026-23941Same product: Erlang Erlang\/Otp
CVE-2026-48856Same product: Erlang Erlang\/Otp
CVE-2026-49759Same product: Erlang Erlang\/Otp
CVE-2026-54890Same product: Erlang Erlang\/Otp
CVE-2026-23942Same product: Erlang Erlang\/Otp
CVE-2026-49760Same product: Erlang Erlang\/Otp
CVE-2026-54886Same product: Erlang Erlang\/Otp

Affected Assets

erlang
erlang\/otp
17.0 — 26.2.5.21 · 27.0 — 27.3.4.12 · 28.0 — 28.5.0.1

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 24 hardening rules · 5 OS baselines
Validate
Prove the fix (OWASP ASVS)

—

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

PKI certificate issuance and acquisition under an approved policy establishes the trusted roots and processes needed for correct validation.

Protecting session authenticity depends on cryptographic mechanisms whose trust depends on correct certificate validation.

Requiring confidentiality and integrity protection of transmitted data drives use of properly validated certificates in protocols such as TLS.

Mitigating Controls (NIST CSF 2.0)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.

PR.AA-03 mostly match
blocks

Certificate-based authentication of users/services/hardware directly depends on correct validation.

PR.DS-02 mostly match
blocks

Proper certificate validation is a core mechanism for protecting data-in-transit confidentiality and integrity.

PR.PS-06 mostly match
blocks

Secure development practices explicitly include implementing correct certificate validation logic.

ID.RA-09 partial match
blocks

Assessing authenticity/integrity of acquired software often relies on code-signing certificate validation.

PR.AA-04 partial match
blocks

Identity assertions conveyed via certificates require validation to be verified.

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

Security testing can detect missing or incorrect certificate chain validation.

blocks

Requiring issuance and validation of public-key certificates under an approved policy reduces the chance that certificates with improper validation will be trusted.

prevents

Secure coding standards address correct certificate chain validation.

finds

A.8.8's reach is DISCLOSURE — it sees only instances that carry a vendor-published flaw. CWE-295 does surface as CVEs (Apple goto fail, Go framework, router firmware, etc.), so the disclosed share is found, but the bulk of certificate-validation defects live in custom first-party code with no published advisory, which is outside A.8.8's reach and belongs to A.8.29.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over our cross-walk; rows rated `none` are excluded, and each rule says how its mapping was checked.

Definition changed on 29 October 2026. Until then this section listed every rule rated above none, partial included. From that date it lists rules whose mapping is rated full or mostly and checked at llm_unverified or higher; partial mappings show when you ask.

Oracle Linux 8 (3 rules)
  • V-248531 OL 8, for PKI-based authentication, must validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor. blocks CWE-295, CWE-296
  • V-248574 YUM must be configured to prevent the installation of patches, service packs, device drivers, or OL 8 system components that have not been digitally signed using a certificate that is recognized and approved by the organization. blocks CWE-295
  • V-248575 OL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. blocks CWE-295
Oracle Linux 9 (1 rule)
  • V-271604 OL 9, for PKI-based authentication, must validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor. blocks CWE-296
RHEL 7 (2 rules)
  • V-204447 The Red Hat Enterprise Linux operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. blocks CWE-295
  • V-204448 The Red Hat Enterprise Linux operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. blocks CWE-295
RHEL 8 (3 rules)
  • V-230229 RHEL 8, for PKI-based authentication, must validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor. blocks CWE-296
  • V-230264 RHEL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. blocks CWE-295
  • V-230265 RHEL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. blocks CWE-295
RHEL 9 (1 rule)
  • V-258131 RHEL 9, for PKI-based authentication, must validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor. blocks CWE-296

References