LiveActive security incident?Get immediate response
CVE Record

CVE-2022-37026: In Erlang/OTP before 23.3.4.15, 24.x before 24.3.4.2, and 25.x before 25.0.2, there is a Client Authenticat...

In Erlang/OTP before 23.3.4.15, 24.x before 24.3.4.2, and 25.x before 25.0.2, there is a Client Authentication Bypass in certain client-certification situations for SSL, TLS, and DTLS.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This is a critical authentication bypass in Erlang/OTP SSL, TLS, and DTLS handling. In some client-certificate authentication situations, an unauthorized client may be accepted as trusted. Organizations using Erlang-based services for mutual TLS should treat this as urgent, especially for internet-facing or partner-facing systems.

Executive priority

Make this a high-priority remediation item for any Erlang-backed service using client certificates. The business risk is unauthorized access through a trust boundary, with potentially severe data and service impact if exposed systems depend on mutual TLS.

Technical view

CVE-2022-37026 affects Erlang/OTP before 23.3.4.15, 24.x before 24.3.4.2, and 25.x before 25.0.2. The issue is a client authentication bypass in certain SSL/TLS/DTLS client-certificate cases. The CVSS 3.1 score is 9.8, with network attack vector and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely where Erlang/OTP SSL, TLS, or DTLS is used with client certificates for authentication. Risk is higher for externally reachable services, APIs, gateways, brokers, or internal control planes that rely on mutual TLS trust decisions.

Exploitation context

The provided sources do not show CISA KEV listing or confirmed active exploitation. The CVSS vector indicates remote, unauthenticated exploitability under affected configurations, but the source bundle only states the bypass occurs in certain client-certificate situations.

Researcher notes

Evidence is sufficient for affected version boundaries and vulnerability class, but limited on the exact certificate-validation edge case. Avoid broad product assumptions beyond Erlang/OTP SSL/TLS/DTLS users. No source in the bundle confirms exploitation in the wild.

Mitigation direction

  • Upgrade Erlang/OTP to 23.3.4.15, 24.3.4.2, 25.0.2, or later.
  • Apply distribution security updates where Erlang is managed by the operating system.
  • Prioritize systems using SSL/TLS/DTLS client-certificate authentication.
  • Check Erlang/OTP and OS vendor advisories for environment-specific guidance.
  • Reduce exposure of affected mutual TLS endpoints until fixed.

Validation and detection

  • Inventory Erlang/OTP versions across applications, containers, and hosts.
  • Confirm deployed versions meet or exceed the fixed release levels.
  • Identify services using Erlang/OTP SSL, TLS, or DTLS client certificates.
  • Verify operating system packages include the relevant security update.
  • Review access logs for unexpected successful client-certificate authentications.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-37026 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2022-37026Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.