DEBIAN-CVE-2026-55962
- Source
- https://security-tracker.debian.org/tracker/CVE-2026-55962
- Import Source
- https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2026-55962.json
- JSON Data
- https://api.osv.dev/v1/vulns/DEBIAN-CVE-2026-55962
- Upstream
- Published
- 2026-06-25T22:17:02Z
- Modified
- 2026-09-14T17:03:20Z
- Severity
-
- 6.5 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N CVSS Calculator
- Summary
- [none]
- Details
-
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.
- References
Affected packages
Debian:12 / wolfssl
Package
- Name
- wolfssl
- Purl
- pkg:deb/debian/wolfssl?arch=source&distro=bookworm
Debian:13 / wolfssl
Package
- Name
- wolfssl
- Purl
- pkg:deb/debian/wolfssl?arch=source&distro=trixie