CVE-2026-55962 TLS 1.3 post-handshake authentication: server accepts Finished without client Certificate/CertificateVerify
- Published
- Updated
- Exploit status
- No public exploit known
- CISA SSVC
- No known exploitation · automatable: no · technical impact: partial
- Technology
- MariaDBUbuntuDebian
Description
TLS 1.3 post-handshake authentication (PHA) issue where a server could accept a client's Finished message without the client having sent a Certificate and CertificateVerify. The post-handshake-auth exemption that allows an empty/absent peer certificate was only intended for the initial handshake, but it was also being applied while a post-handshake CertificateRequest was still outstanding. The check is now scoped to the initial handshake only: on the server, once a post-handshake CertificateRequest has been sent (certReqCtx is set), a peer certificate and a valid CertificateVerify are required again before the Finished is accepted, with empty-certificate handling following the configured verify mode (FAIL_IF_NO_PEER_CERT) just as during first-handshake client authentication. Only affects TLS 1.3 servers built with post-handshake authentication support (WOLFSSL_POST_HANDSHAKE_AUTH / --enable-postauth, included in --enable-all) that enable WOLFSSL_VERIFY_POST_HANDSHAKE and request a client certificate after the handshake via wolfSSL_request_certificate(). Clients, and servers that do not use post-handshake authentication, are unaffected.
Upgrade path
9 packages: 4 fixed, 5 with no fix yet.
| Package | Affected | Fixed in | Status |
|---|---|---|---|
| MariaDB Server(Azure Linux 3.0) | All versions | No fix listed | No fix yet |
| ubuntu/wolfssl(Ubuntu 22.04) | All versions | No fix listed | No fix yet |
| ubuntu/wolfssl(Ubuntu 24.04) | All versions | No fix listed | No fix yet |
| ubuntu/wolfssl(Ubuntu 26.04) | All versions | No fix listed | No fix yet |
| ubuntu/wolfssl(Ubuntu 26.10) | All versions | No fix listed | No fix yet |
| alpine/wolfssl(Alpine v3.24) | >= 5.5.4, < 5.9.2-r0 | 5.9.2-r0 | Fixed |
| debian/wolfssl(Debian 12) | < 5.5.4-2+deb12u3; = 5.5.4-2; = 5.5.4-2+deb12u1; = 5.5.4-2+deb12u2 | 5.5.4-2+deb12u3 | Fixed |
| debian/wolfssl(Debian 13) | < 5.7.2-0.1+deb13u2; = 5.7.2-0.1; = 5.7.2-0.1+deb13u1 | 5.7.2-0.1+deb13u2 | Fixed |
| wolfSSL | >= 5.5.4, < 5.9.2; >= 5.5.4, <= 5.9.1 | 5.9.2 | Fixed |
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| wolfSSL | >= 5.5.4, <= 5.9.1 | No fix listed |
| debian/wolfssl(Debian:12) | < 5.5.4-2+deb12u3 | 5.5.4-2+deb12u3 |
| debian/wolfssl(Debian:12) | = 5.5.4-2 | No fix listed |
| debian/wolfssl(Debian:12) | = 5.5.4-2+deb12u1 | No fix listed |
| debian/wolfssl(Debian:12) | = 5.5.4-2+deb12u2 | No fix listed |
| debian/wolfssl(Debian:13) | < 5.7.2-0.1+deb13u2 | 5.7.2-0.1+deb13u2 |
| debian/wolfssl(Debian:13) | = 5.7.2-0.1 | No fix listed |
| debian/wolfssl(Debian:13) | = 5.7.2-0.1+deb13u1 | No fix listed |
| ubuntu/wolfssl(Ubuntu:22.04) | All versions | No fix listed |
| alpine/wolfssl(Alpine:v3.24) | >= 5.5.4, < 5.9.2-r0 | 5.9.2-r0 |
| ubuntu/wolfssl(Ubuntu:24.04) | All versions | No fix listed |
| ubuntu/wolfssl(Ubuntu:26.04) | All versions | No fix listed |
| ubuntu/wolfssl(Ubuntu:26.10) | All versions | No fix listed |
| wolfSSL | >= 5.5.4, < 5.9.2 | 5.9.2 |
| MariaDB Server(Azure Linux:3.0) | All versions | No fix listed |
References
- MSRC Security Update Guide vendor-advisory
- github.com issue-tracking patch
- www.wolfssl.com vendor-advisory
- Debian Security Tracker CVE-2026-55962 vendor-advisory
- Ubuntu CVE tracker vendor-advisory
- www.cve.org
- security.alpinelinux.org vendor-advisory
- bugs.debian.org issue-tracking