Metrics
Affected Vendors & Products
No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
| Link | Providers |
|---|---|
| https://github.com/wolfSSL/wolfssl/pull/10102 |
|
Fri, 10 Apr 2026 18:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Fri, 10 Apr 2026 09:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Wolfssl
Wolfssl wolfssl |
|
| Vendors & Products |
Wolfssl
Wolfssl wolfssl |
Thu, 09 Apr 2026 22:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | out-of-bounds write in TLSX_EchChangeSNI via attacker-controlled publicName | |
| Weaknesses | CWE-787 | |
| References |
| |
| Metrics |
cvssV4_0
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: wolfSSL
Published:
Updated: 2026-04-10T17:58:51.312Z
Reserved: 2026-04-03T15:55:20.740Z
Link: CVE-2026-5503
Updated: 2026-04-10T17:58:48.245Z
Status : Received
Published: 2026-04-09T23:17:01.257
Modified: 2026-04-09T23:17:01.257
Link: CVE-2026-5503
No data.
OpenCVE Enrichment
Updated: 2026-04-10T09:27:34Z