Is CVE-2026-6092 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-6092 being exploited in the wild.

How severe is CVE-2026-6092?

Informational severity, with a CVSS score of 2.1, published 25 June 2026.

Is there a fix for CVE-2026-6092?

A patch was published on 2026-04-09: Fix merged into wolfSSL master branch via PR 10167 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-6092 attacked?

It is attacked over the network or from the adjacent network, in a software library.

Am I affected by CVE-2026-6092?

Check whether you run Wolfssl at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-6092: wolfSSL algorithm downgrade from Encrypt-then-MAC to MAC-then-Encrypt

CVE-2026-6092 · Severity: info · CVSS 2.1 · Published 2026-06-25

wolfSSL is a security library used to protect communications for embedded devices and cloud services. A flaw in how it handles secure connections could allow the system to use a less secure encryption method than intended when a previous session fails to resume correctly. While this reduces the overall strength of the security, it does not directly expose data to an attacker without other significant conditions being met.

Technologies: Wolfssl. Vendors: Wolfssl.

Quick answers

Is CVE-2026-6092 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-6092 being exploited in the wild.
How severe is CVE-2026-6092?: Informational severity, with a CVSS score of 2.1, published 25 June 2026.
Which products and versions are affected?: Wolfssl 5.2.0 through 5.9.1.
Is there a fix for CVE-2026-6092?: A patch was published on 2026-04-09: Fix merged into wolfSSL master branch via PR 10167 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-6092 attacked?: It is attacked over the network or from the adjacent network, in a software library.
Am I affected by CVE-2026-6092?: Check whether you run Wolfssl at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A vulnerability exists in wolfSSL versions 5.2.0 through 5.9.1 where the TLS 1.2 implementation fails to enforce the Encrypt-then-MAC (EtM) extension during specific handshake paths. Specifically, if a server initially attempts to resume a session but the resumption lookup fails (e.g., due to a stale session ID), the logic in DoClientHello may silently disable EtM and fall back to the older MAC-then-Encrypt (MtE) mechanism. This is classified as a 'Selection of Less-Secure Algorithm During Negotiation' (CWE-757). An attacker with adjacent network access and specific preconditions could potentially exploit this downgrade, though the impact is limited to a loss of cryptographic strength. The issue is fixed in wolfSSL version 5.9.1.

Affected products

wolfSSL wolfSSL 5.2.0 through 5.9.1

Timeline

2026-04-09: patched: Fix merged into wolfSSL master branch via PR 10167
2026-06-25: disclosed: CVE-2026-6092 published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.