With TLS 1.3 pre-shared key (PSK) a malicious or faulty server could ignore the request for PFS (perfect forward secrecy) and the client would continue on with the connection using PSK without PFS. This happened when a server responded to a ClientHello containing psk_dhe_ke without a key_share extension. The re-use of an authenticated PSK connection that on the clients side unexpectedly did not have PFS, reduces the security of the connection.
Fix
Patch, vendor advisory and mitigation references on NVD 1
- https://github.com/wolfSSL/wolfssl/pull/9112 Issue Tracking, Patch
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 6.3 · wolfsslNVD modified 2026-10-19 13:10
Affected (CPE criteria) 1
cpe:2.3:a:wolfssl:wolfssl:*:*:*:*:*:*:*:*
References 2
- https://github.com/wolfSSL/wolfssl Product
- https://github.com/wolfSSL/wolfssl/pull/9112 Issue Tracking, Patch