# CVE-2026-89422: TLS 1.3 client skips server authentication when ServerHello carries an unsolicited pre_shared_key extension


- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 22 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** AZL-103428, DEBIAN-CVE-2026-89422, EEF-CVE-2026-89422, GHSA-rgxr-4g4w-j875, UBUNTU-CVE-2026-89422

## What is CVE-2026-89422?

CVE-2026-89422 is a critical vulnerability in Erlang OTP, published on 22 Sep 2026. 

### Official description

Key Exchange without Entity Authentication vulnerability in Erlang/OTP ssl allows a peer that answers a TLS 1.3 client connection to impersonate the intended server. A pre_shared_key extension in the ServerHello that the client never offered causes the client to complete the handshake without validating the server's certificate, so ssl:connect returns {ok, Socket} against a peer holding no certificate, no private key and no prior session.

tls_client_connection_1_3:handle_server_hello/2 passes the received extension to tls_gen_connection_1_3:handle_resumption/2, which sets resumption = true on its mere presence without checking that the client offered a PSK. tls_handshake_1_3:get_pre_shared_key/4 meanwhile falls back to the all-zero "no PSK" value and keys the handshake with the ordinary non-PSK schedule, so the attacker's own ephemeral key suffices. The resumption flag then routes maybe_resumption/1 straight to wait_finished, skipping the certificate-handling states, so certificate path validation, verify_fun, hostname verification, partial_chain, CRL checking and OCSP stapling are all bypassed. The default client configuration is affected; clients restricted to TLS 1.2 are not.

This issue affects OTP from OTP 22.2 before OTP 27.3.4.18, OTP 28.5.0.7, and OTP 29.1.1, corresponding to ssl from 9.5 before 11.2.12.13, 11.6.0.6, and 11.7.7.

Weakness: CWE-322 (Key Exchange without Entity Authentication)

## Which versions are affected by CVE-2026-89422?


## How do I fix CVE-2026-89422?

Upgrade to a fixed version.

## Is CVE-2026-89422 being exploited?

There is no known exploitation of CVE-2026-89422 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-89422 and fix it if it is affected.

What it is: CVE-2026-89422 is a critical vulnerability in Erlang OTP, published on 22 Sep 2026. 
Exploitation: There is no known exploitation of CVE-2026-89422 in the wild and no public exploit code.

Affected product: Erlang OTP. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-89422/ (Markdown: https://insights.sbomify.com/CVE-2026-89422/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-89422
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-89422
- OSV: https://osv.dev/vulnerability/CVE-2026-89422

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-89422/
Summaries are generated and may contain mistakes; the official description above is the record.