The vulnerability occurs during TLS shutdown in wolfSSL implementations. A partial wolfSSL_read() followed by a bidirectional wolfSSL_shutdown() and another wolfSSL_read() can trigger a heap‑use‑after‑free condition. The resulting memory corruption could cause an application crash or, if an attacker can influence the freed memory region, potentially allow arbitrary code execution.

All wolfSSL builds that incorporate TLS (including default builds) are affected; version details are unspecified, so any current release may be vulnerable until a patch is applied.

The CVSS score of 2.3 indicates low severity. No EPSS data is available and the flaw is not listed in the CISA KEV catalog. The likely attack scenario requires the application to perform a specific read‑shutdown‑read sequence, which is typically local and depends on application flow. Consequently, the exploitation risk is considered low, but memory corruption remains a concern for affected deployments.