Skip to main content
CVE-2026-34182VulnerabilityPublished

SUSE · Recommended update for openssl-3

Affects SUSESource GCVE Database

0
Compare

Not known to be exploited.

Data as of 10 Nov 2026, 18:55 UTC

Severity
Medium

Rated by Threat Radar · CVSS not yet scored by NVD

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

What to do

AI-suggested

Apply the recommended update for OpenSSL 3 provided by the vendor to ensure the strict tag initialization and length enforcement cannot be bypassed. Avoid setting the environment variable OPENSSL_ALLOW_CMS_UNAUTHENTICATED_AEAD to a non-zero value unless explicitly required and understood, as it disables critical security enforcement.

Description

An update for OpenSSL 3 addresses an issue where the strict tag initialization and length enforcement introduced in the fix for CVE-2026-34182 can be bypassed if the environment variable OPENSSL_ALLOW_CMS_UNAUTHENTICATED_AEAD is set to a non-zero value. This bypass allows circumvention of the intended security enforcement.

Reports on CVE-2026-34182

References

Community reviews

Loading reviews…