CVE-2026-34182 Vulnerability Analysis & Exploit Details

CVE-2026-34182
Vulnerability Scoring

9.1
/10
Critical Risk

As a catastrophic security flaw, CVE-2026-34182 has severe implications, demanding immediate intervention.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-34182 Details

Status: Analyzed

Last updated: 🕕 15 Jun 2026, 18:13 UTC
Originally published on: 🕔 09 Jun 2026, 17:17 UTC

Time between publication and last update: 6 days

CVSS Release: version 3

CVSS3 Source

134c704f-9b21-4f2e-91b3-4a467353bcc0

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

CVE-2026-34182 Vulnerability Summary

CVE-2026-34182: Issue Summary: Cryptographic Message Services (CMS) processing fails to perform sufficient input validation on the cipher and tag length fields of AuthEnvelopedData containers, leading to various potential compromises. Impact Summary: Attackers making use of these vulnerabilities may achieve key-equivalent functionality for a given CMS recipient and/or bypass integrity validation for a given message. In one use case, an attacker may send a CMS message containing AuthEnvelopedData with the cipher specified as a non-AEAD cipher. OpenSSL erroneously allows this selection, and attempts to decrypt and validate the message. An on-path attacker who captures one legitimate AES-GCM AuthEnvelopedData addressed to the victim can re-emit it with the recipientInfos set left byte-for-byte intact, so the victim's private key still unwraps the genuine CEK (the content-encryption key), but with the inner OID rewritten to AES-256-OFB (Output Feedback Mode, an unauthenticated keystream mode) and with an attacker-chosen IV and ciphertext. The victim initializes AES-256-OFB under the real CEK, never consults the MAC field, and CMS_decrypt() returns success. If the application under attack responds to the attacker with any indicator showing success or failure of the decryption effort, it is possible for the attacker to use this as an oracle to obtain key equivalent functionality for the CEK used for the chosen recipient of the message. In another use case, an attacker can reduce the tag length of the chosen AEAD cipher for a given AuthEnvelopedData container to be a single byte long, allowing an attacker to brute force CMS decryption, producing an integrity bypass for applications that trust CMS_decrypt() to reject modified content. The FIPS modules are not affected by this issue.

Assessing the Risk of CVE-2026-34182

Access Complexity Graph

The exploitability of CVE-2026-34182 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-34182

With low attack complexity and no required privileges, CVE-2026-34182 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-34182, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-34182, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2026-34182 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2026-34182 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: None
    CVE-2026-34182 does not impact system availability.

CVE-2026-34182 References

External References

CWE Common Weakness Enumeration

CWE-354

CAPEC Common Attack Pattern Enumeration and Classification

  • Checksum Spoofing CAPEC-145 An adversary spoofs a checksum message for the purpose of making a payload appear to have a valid corresponding checksum. Checksums are used to verify message integrity. They consist of some value based on the value of the message they are protecting. Hash codes are a common checksum mechanism. Both the sender and recipient are able to compute the checksum based on the contents of the message. If the message contents change between the sender and recipient, the sender and recipient will compute different checksum values. Since the sender's checksum value is transmitted with the message, the recipient would know that a modification occurred. In checksum spoofing an adversary modifies the message body and then modifies the corresponding checksum so that the recipient's checksum calculation will match the checksum (created by the adversary) in the message. This would prevent the recipient from realizing that a change occurred.
  • Padding Oracle Crypto Attack CAPEC-463 An adversary is able to efficiently decrypt data without knowing the decryption key if a target system leaks data on whether or not a padding error happened while decrypting the ciphertext. A target system that leaks this type of information becomes the padding oracle and an adversary is able to make use of that oracle to efficiently decrypt data without knowing the decryption key by issuing on average 128*b calls to the padding oracle (where b is the number of bytes in the ciphertext block). In addition to performing decryption, an adversary is also able to produce valid ciphertexts (i.e., perform encryption) by using the padding oracle, all without knowing the encryption key.
  • Manipulating Writeable Configuration Files CAPEC-75 Generally these are manually edited files that are not in the preview of the system administrators, any ability on the attackers' behalf to modify these files, for example in a CVS repository, gives unauthorized access directly to the application, the same as authorized users.

Vulnerable Configurations

  • cpe:2.3:a:openssl:openssl:3.0.0:-:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.0.0:-:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.0.0:beta1:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.0.0:beta1:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.0.0:beta2:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.0.0:beta2:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.0.0:alpha1:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.0.0:alpha1:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.0.0:alpha10:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.0.0:alpha10:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.0.0:alpha11:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.0.0:alpha11:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.0.0:alpha12:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.0.0:alpha12:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.0.0:alpha13:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.0.0:alpha13:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.0.0:alpha14:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.0.0:alpha14:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.0.0:alpha15:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.0.0:alpha15:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.0.0:alpha16:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.0.0:alpha16:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.0.0:alpha17:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.0.0:alpha17:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.0.0:alpha2:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.0.0:alpha2:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.0.0:alpha3:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.0.0:alpha3:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.0.0:alpha4:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.0.0:alpha4:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.0.0:alpha5:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.0.0:alpha5:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.0.0:alpha6:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.0.0:alpha6:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.0.0:alpha7:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.0.0:alpha7:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.0.0:alpha8:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.0.0:alpha8:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.0.0:alpha9:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.0.0:alpha9:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.0.3:*:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.0.3:*:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.0.4:*:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.0.4:*:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.0.5:*:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.0.5:*:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.0.6:*:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.0.6:*:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.0.7:*:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.0.7:*:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.0.8:*:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.0.8:*:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.0.9:*:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.0.9:*:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.0.10:*:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.0.10:*:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.0.11:*:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.0.11:*:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.0.12:*:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.0.12:*:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.0.13:*:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.0.13:*:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.0.14:*:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.0.14:*:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.0.15:*:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.0.15:*:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.0.19:*:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.0.19:*:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.4.0:-:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.4.0:-:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.4.0:beta1:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.4.0:beta1:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.4.0:alpha1:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.4.0:alpha1:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.4.1:*:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.4.2:*:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.4.2:*:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.4.3:*:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.4.3:*:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.4.4:*:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.4.4:*:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.5.0:-:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.5.0:-:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.5.0:beta1:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.5.0:beta1:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.5.0:alpha1:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.5.0:alpha1:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.5.1:*:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.5.1:*:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.5.2:*:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.5.2:*:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.5.3:*:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.5.3:*:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.5.4:*:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.5.4:*:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.5.5:*:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.5.5:*:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.6.0:-:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.6.0:-:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.6.0:beta1:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.6.0:beta1:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.6.0:alpha1:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.6.0:alpha1:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:3.6.1:*:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:3.6.1:*:*:*:*:*:*:*
  • cpe:2.3:a:openssl:openssl:4.0.0:-:*:*:*:*:*:*
    cpe:2.3:a:openssl:openssl:4.0.0:-:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-34182: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-54236 – vLLM is an inference and serving engine for large language models (LLMs). Prior to 0.23.1rc0, the fix for CVE-2026-22778, which introduced a saniti...
  • CVE-2026-54235 – vLLM is an inference and serving engine for large language models (LLMs). Prior to 0.23.1rc0, ll temperature validation gates use comparison operat...
  • CVE-2026-54233 – vLLM is an inference and serving engine for large language models (LLMs). Prior to 0.23.1rc0, vLLM's /v1/audio/transcriptions endpoint limits compr...
  • CVE-2026-54232 – vLLM is an inference and serving engine for large language models (LLMs). Prior to 0.22.1, the vLLM Dockerfile is vulnerable to a dependency confus...
  • CVE-2026-53923 – vLLM is an inference and serving engine for large language models (LLMs). From 0.5.5 until 0.23.1rc0, integer truncation of tensor dimensions in vL...