Client accepts unsolicited RawPublicKey server certificate type (CVE-2026-89136) | HOL Guard CVE

High · CVSS 8.3CVE-2026-89136

Client accepts unsolicited RawPublicKey server certificate type

Answer in brief

CVE-2026-89136 records a High severity (CVSS 8.3) vulnerability in Client accepts unsolicited RawPublicKey server certificate type. The current sources do not mark it as known exploited. The current feed maps wolfSSL/wolfSSL (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 27, 2026Updated Sep 27, 2026Source checked Sep 27, 2026First seen by HOL Sep 27, 2026Material review Sep 27, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 8.3
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Not reported

Why this deserves its current priority

CVSS is 8.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps wolfSSL/wolfSSL (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
wolfSSL/wolfSSLgeneric	>=5.6.0 <=5.9.2	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for wolfSSL/wolfSSL.
Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

Published upstream
Sep 27, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 27, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 27, 2026

Sources and claim methodology

GitHub security advisorygithub.com

Upstream source description

When using RPK (Raw Public Key), the client side of a TLS 1.2, 1.3 and DTLS 1.2 connection could accept an unsolicited server_cert_type=RawPublicKey which allowed a malicious or misbehaving server to bypass authentication. RPK is off by default and only enabled in --enable-rpk OR --enable-all OR --enable-distro AKA HAVE_RPK builds.

Quoted source text, attributed separately from HOL analysis.