Skip to navigation

Threat reportVulnerabilityTL-2026-1151

wolfSSL Improper Input Validation and Integer Underflow Vulnerabilities (CVE-2026-28739, CVE-2026-25106, CVE-2026-33091)

ACTIVE

Cisco Talos (researcher Ankur Tyagi) disclosed three vendor-patched vulnerabilities in the wolfSSL embedded TLS/SSL library: two improper-input-validation flaws (CVE-2026-28739 / TALOS-2026-2409, CVE-2026-25106 / TALOS-2026-2410) and one integer-underflow flaw (CVE-2026-33091 / TALOS-2026-2408). All three were fixed by the vendor prior to public disclosure on 2026-07-01/02 and rolled up in a Talos blog post on 2026-07-09.

Key facts

IdentifiersTL-2026-1151, CVE-2026-28739, CVE-2026-25106, CVE-2026-33091
Also known asTALOS-2026-2408, TALOS-2026-2409, TALOS-2026-2410
SeverityUNKNOWN
Affected productswolfSSL Inc. wolfSSL embedded TLS/SSL and cryptography library
Weaknesses (CWE)CWE-20, CWE-191
ToolswolfSSL embedded TLS/SSL library
MITRE ATT&CK techniquesT1036 Masquerading, T1040 Network Sniffing, T1068 Exploitation for Privilege Escalation, T1190 Exploit Public-Facing Application, T1203 Exploitation for Client Execution, T1210 Exploitation of Remote Services, T1211 Exploitation for Stealth, T1499 Endpoint Denial of Service, T1518 Software Discovery, T1557 Adversary-in-the-Middle, T1573 Encrypted Channel, T1587.004 Exploits and 4 more in the attack flow
MotivationUNKNOWN
Target sectorstechnology, manufacturing, critical-infrastructure, health, automotive, telecoms
Target regionsGlobal
Detection rules9 (1 shown free)
Sources7 cited sources

Detection coverage

As of 2026-07-09, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-1151 across Splunk SPL, Microsoft KQL and Sigma, covering 15 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.

Free detection: Anomalous TLS Handshake / Certificate Length Field Against wolfSSL-Linked Endpoint

Detects inbound TLS/X.509 handshake traffic to a certificate-validating, wolfSSL-linked endpoint where the declared handshake/certificate length field is inconsistent with observed payload size — the network-observable signature of probing CVE-2026-28739 / CVE-2026-25106 improper-input-validation parsing paths (CWE-20).

  • Languages: Splunk SPL, Microsoft KQL, Sigma
  • ATT&CK: T1190, T1595.002
  • Data sources: network_traffic, stream:tcp, DeviceNetworkEvents
  • Severity: high
  • Confidence: medium

Splunk SPL

index=network sourcetype="stream:tcp" dest_port IN (443,8443,4433,5443)
| eval length_mismatch=if(tls_handshake_declared_len > (bytes_in + 512) OR tls_handshake_declared_len < 8, 1, 0)
| where length_mismatch=1
| stats count min(_time) as first_seen max(_time) as last_seen values(dest_ip) as dest_ip values(dest_port) as dest_port by src_ip
| where count >= 1
| table src_ip dest_ip dest_port count first_seen last_seen

Microsoft KQL

DeviceNetworkEvents
| where Timestamp > ago(24h)
| where RemotePort in (443, 8443, 4433, 5443)
| where ActionType == "ConnectionSuccess"
| extend HandshakeLenMismatch = iff(isnotempty(AdditionalFields), tostring(AdditionalFields), "")
| where HandshakeLenMismatch has "tls_length_anomaly" or HandshakeLenMismatch has "cert_length_anomaly"
| project Timestamp, DeviceName, LocalIP, RemoteIP, RemotePort, InitiatingProcessFileName, HandshakeLenMismatch
| summarize ConnectionCount = count() by DeviceName, RemoteIP, RemotePort
| where ConnectionCount >= 1

Sigma

title: Anomalous TLS Handshake or Certificate Length Field via wolfSSL-Linked Endpoint
id: 6a1e2f10-1151-4c11-9a01-tl20261151spl001
status: experimental
description: Detects TLS/X.509 handshake traffic where the declared handshake or certificate length field does not match observed payload size, consistent with probing wolfSSL CVE-2026-28739/CVE-2026-25106 improper-input-validation parsing paths.
references:
    - https://blog.talosintelligence.com/wolfssl-vulnerabilities/
author: Threadlinqs Team
date: 2026-07-09
tags:
    - attack.initial-access
    - attack.t1190
    - attack.reconnaissance
    - attack.t1595.002
    - cve.2026.28739
    - cve.2026.25106
    - cwe.20
logsource:
    category: network_connection
    product: linux
detection:
    selection:
        DestinationPort:
            - 443
            - 8443
            - 4433
            - 5443
        Initiated: true
    anomaly:
        TlsLengthAnomaly: true
    condition: selection and anomaly
falsepositives:
    - Legitimate TLS handshakes with unusually large certificate chains or nonstandard extensions
    - Load balancers re-fragmenting TLS records
level: medium

Known false positives:

  • Legitimate TLS handshakes with unusually large certificate chains or nonstandard TLS extensions
  • Middleboxes/load balancers re-fragmenting or re-writing TLS records

Tuning notes: Requires a TLS-parsing network sensor (e.g. Zeek/Suricata TLS logs feeding stream:tcp) that computes declared-vs-observed length deltas; without that enrichment field this rule needs a companion Zeek/Suricata pipeline. Scope dest_ip to known wolfSSL-linked internet-facing assets from the SBOM inventory to reduce noise.

8 more detection rules (Splunk SPL, Microsoft KQL, Sigma) · unlock with TL Creds. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple)
  • Repeated Malformed-Handshake Connection Attempts Against Certificate-Validating Endpoint · unlock with TL Creds
  • Process Spawning ASN.1/Certificate-Parsing Debug Utilities Near wolfSSL-Linked Binaries · unlock with TL Creds
  • Masquerading Process Name Mimicking Legitimate TLS/Crypto Service Post-wolfSSL Exploitation · unlock with TL Creds
  • Adversary-in-the-Middle Interception Setup Targeting [indicator] Certificate Validation Bypass · unlock with TL Creds
  • Endpoint Crash or Service Restart Loop on wolfSSL-Linked TLS-Terminating Service · unlock with TL Creds
  • [indicator] Vulnerability-Scanning Reconnaissance Against Public-Facing Certificate-Validating Assets · unlock with TL Creds
  • Software-Discovery-Then-Connect Pattern Targeting [indicator] Package Metadata · unlock with TL Creds
  • Fixed-Interval Low-Jitter Beacon Pattern Over TLS-Terminating Service · unlock with TL Creds

Indicators of compromise

As of 2026-07-09, Threadlinqs Intelligence tracks 15 indicators of compromise for TL-2026-1151.

15 indicators of compromise · unlock with TL Creds. Compare plans

Technical analysis

wolfSSL is a small-footprint, portable TLS/SSL and cryptography library used across embedded systems, IoT devices, industrial and automotive controllers, medical devices, and cloud services where a lightweight secure-transport stack is required. Cisco Talos's third-party vulnerability disclosure program, through researcher Ankur Tyagi, identified and privately reported three distinct defects in the library to the vendor. Two of the three (TALOS-2026-2409 / CVE-2026-28739 and TALOS-2026-2410 / CVE-2026-25106) are classified by Talos as improper input validation issues; the source article groups both under this shared classification without further public breakdown of the specific parsing paths affected. The third (TALOS-2026-2408 / CVE-2026-33091) is classified as an integer underflow issue, a defect class in which an arithmetic subtraction on an attacker-influenced length or index value wraps below zero, typically producing an unexpectedly large unsigned value that is then used in a subsequent memory-copy or bounds calculation -- a pattern that commonly leads to heap corruption, out-of-bounds read/write, denial of service, or in the worst case remote code execution, depending on how the resulting value is consumed downstream. wolfSSL has released patches addressing all three defects; the Talos source article does not publish the affected version range, a CVSS score/vector, or any evidence of in-the-wild exploitation, so those fields are recorded as UNKNOWN/null per source-grounding requirements rather than estimated. Independent research confirms wolfSSL shipped v5.9.1 on 2026-04-08 and v5.9.2 on 2026-06-23, consistent with the Talos disclosure timeline (private vendor notification 2026-04-29, patch released 2026-06-23, public advisory 2026-07-01/02), indicating v5.9.2 is the remediated release line. Given the vulnerability classes involved -- input validation defects in a TLS library are frequently rooted in certificate/handshake parsing, and integer underflow defects in crypto/ASN.1 libraries are a recurring heap-corruption root cause (per CWE-191 advisory guidance) -- the practical risk profile for unpatched deployments is assessed as HIGH, spanning potential denial of service, memory corruption, and (for the input-validation class) possible security-control bypass in certificate/data validation logic, pending any vendor clarification of exact impact.

MITRE ATT&CK techniques by tactic:

Defense Evasion

T1036 Masquerading; T1211 Exploitation for Stealth

Credential Access

T1040 Network Sniffing; T1557 Adversary-in-the-Middle

Privilege Escalation

T1068 Exploitation for Privilege Escalation

Initial Access

T1190 Exploit Public-Facing Application

Execution

T1203 Exploitation for Client Execution

Lateral Movement

T1210 Exploitation of Remote Services

Impact

T1499 Endpoint Denial of Service

Discovery

T1518 Software Discovery

Command and Control

T1573 Encrypted Channel

Resource Development

T1587.004 Exploits; T1588.005 Exploits; T1588.006 Vulnerabilities

Reconnaissance

T1592.002 Software; T1595.002 Vulnerability Scanning

Remediation

Patches

  • Upgrade to wolfSSL v5.9.2 (released 2026-06-23) or later, which the disclosure timeline indicates contains the fixes for all three reported issues

Immediate actions

  • Inventory all products and firmware images embedding wolfSSL and identify the linked library version
  • Prioritize internet-facing and certificate-validating deployments (VPN endpoints, IoT device provisioning, TLS-terminating gateways) for patch review
  • Where patching is not immediately possible, restrict exposure of services that parse untrusted TLS handshakes, X.509 certificates, or PKCS#7/CMS structures through wolfSSL

Workarounds

  • No vendor-published workaround is documented in the source article; version upgrade is the only confirmed remediation

Longer-term hardening

  • Adopt a component/SBOM tracking process for embedded cryptographic libraries to shorten future patch-identification time
  • Enable fuzzing/static-analysis coverage of ASN.1, certificate, and length-arithmetic parsing paths in any custom code layered on wolfSSL
  • Subscribe to Cisco Talos and wolfSSL vendor security advisories for early warning of future disclosures

Affected and fixed versions

  • wolfSSL Inc. — wolfSSL embedded TLS/SSL and cryptography library
    Vulnerable versions: Not published by source; wolfSSL v5.9.1 (2026-04-08) and earlier releases are consistent with the pre-patch disclosure timeline
    Fixed in: wolfSSL v5.9.2 (released 2026-06-23), per the vendor patch date confirmed in the Talos disclosure timeline

Timeline

  • wolfSSL v5.9.1 released; per the confirmed disclosure timeline this and earlier releases predate the fix for the three reported issues.
  • Cisco Talos (researcher Ankur Tyagi) privately disclosed the three wolfSSL vulnerabilities (TALOS-2026-2408/2409/2410) to the wolfSSL vendor under Cisco's third-party disclosure policy.
  • wolfSSL released version 5.9.2, the release consistent with the vendor-patch date recorded in the Talos disclosure timeline for these issues.
  • Cisco Talos publicly disclosed TALOS-2026-2408 (CVE-2026-33091, integer underflow) and TALOS-2026-2409 (CVE-2026-28739, improper input validation).
  • Cisco Talos publicly disclosed TALOS-2026-2410 (CVE-2026-25106, improper input validation).
  • The same Cisco Talos roundup post that disclosed the three wolfSSL CVEs also published 14 GeoVision advisories covering 37 CVEs (researcher Philippe Laulheret) and one VTK-DICOM heap-based buffer overflow, CVE-2026-22879 / TALOS-2026-2366 (researcher Emmanuel Tacheau) -- unrelated products bundled in the same disclosure cycle, authored by Kri Dontje.
  • NVD API query for CVE-2026-28739, CVE-2026-25106, and CVE-2026-33091 returned zero published records (totalResults: 0) at RESEARCH time, confirming no independent CVSS/CWE scoring is yet available and grounding the source's UNKNOWN severity and null CVSS fields.
  • TL-Intel-Harness HUNT phase ingested the Talos blog post via the Cisco Talos Intelligence Blog RSS feed and created threat skeleton TL-2026-1151.
  • Cisco Talos Intelligence Blog published a consolidated vulnerability-disclosure roundup covering the three wolfSSL CVEs alongside separate GeoVision and VTK-DICOM advisories, noting Snort coverage is available via Snort.org rule sets.

Sources cited

Previous and next in vulnerability

Drafted by the Threadlinqs research pipeline from 7 sources; published ; last updated —.

Threadlinqs Intelligence — Real-Time Threat Detection Platform

// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats