In TLSX_EchChangeSNI, the ctx->extensions branch set extensions unconditionally even when TLSX_Find returned NULL. This caused TLSX_UseSNI to attach the attacker-controlled publicName to the shared WOLFSSL_CTX when no inner SNI was configured. TLSX_EchRestoreSNI then failed to clean it up because its removal was gated on serverNameX != NULL. The inner ClientHello was sized before the pollution but written after it, causing TLSX_SNI_Write to memcpy 255 bytes past the allocation boundary.
References
| Link | Resource |
|---|---|
| https://github.com/wolfSSL/wolfssl/pull/10102 | Issue Tracking |
Configurations
History
27 Apr 2026, 17:53
| Type | Values Removed | Values Added |
|---|---|---|
| References | () https://github.com/wolfSSL/wolfssl/pull/10102 - Issue Tracking | |
| First Time |
Wolfssl
Wolfssl wolfssl |
|
| CVSS |
v2 : v3 : |
v2 : unknown
v3 : 9.1 |
| CPE | cpe:2.3:a:wolfssl:wolfssl:*:*:*:*:*:*:*:* |
09 Apr 2026, 23:17
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-04-09 23:17
Updated : 2026-04-27 17:53
NVD link : CVE-2026-5503
Mitre link : CVE-2026-5503
CVE.ORG link : CVE-2026-5503
JSON object : View
Products Affected
wolfssl
- wolfssl
CWE
CWE-787
Out-of-bounds Write
