Skip to main content
CVE-2022-37026VulnerabilityPublished Updated

CVE-2022-37026: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical · fixed in 25.0.2 : patch affected systems as a priority.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.4% chance of exploitation in 30 days – higher than 73% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 25.0.2, 24.3.4.2, 23.3.4.15
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Sep 2022

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Upgrade erlang/otp to 25.0.2, 24.3.4.2 or 23.3.4.15.

Affected software

ProductAffectedFixed in
GitHuberlang/otppkg:github/erlang/otpOther threatsAffected
  • <23.3.4.15
  • <24.3.4.2
  • <25.0.2
Fixed in
  • 23.3.4.15
  • 24.3.4.2
  • 25.0.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediate upgrade to Erlang/OTP versions 23.3.4.15, 24.3.4.2, 25.0.2 or later where the vulnerability is patched. 2. Review and audit all systems using Erlang/OTP for SSL/TLS/DTLS client authentication configurations to identify affected deployments. 3. Implement network-level controls such as strict firewall rules and segmentation to limit exposure of Erlang-based services to untrusted networks. 4. Employ additional authentication layers or mutual TLS verification where possible to mitigate risks until patches are applied. 5. Monitor network traffic and logs for anomalous client authentication attempts or unexpected connections. 6. Coordinate with vendors and service providers to ensure timely patch deployment and confirm no residual vulnerabilities remain. 7. Conduct penetration testing and vulnerability assessments post-patching to validate remediation effectiveness. 8. Educate security teams about the specific nature of this bypass to improve incident detection and response capabilities.

Description

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.

References

Community reviews

Loading reviews…