UBUNTU-CVE-2026-42768 (CVE-2026-42768)
Vulnerability from osv_ubuntu – Published: 2026-06-09 00:00 – Updated: 2026-10-17 09:40 – Source websiteIssue summary: The CMS_decrypt and PKCS7_decrypt functions are vulnerable to Bleichenbacher-style attack when an attacker is able to provide the CMS or S/MIME messages and observe the error code and/or decryption output. Impact summary: The Bleichenbacher-style attack allows an attacker to use the victim's vulnerable application as a way to decrypt or sign messages with the victim's private RSA key. The attack is possible in 2 variants. 1. The decryption API (CMS_decrypt(), PKCS7_decrypt()) is used without providing the recipient certificate. In this case OpenSSL iterates over every KeyTransRecipientInfo (KTRI) without stopping at the first success. An attacker who authors a message with two KTRI entries — the first one wrapping a real CEK under the victim's public key, the second with an arbitrary probe ciphertext — obtains opportunity to iterate the 2nd KTRI to get a valid PKCS#1 v1.5 padding if the error code of the application is available. That is a Bleichenbacher oracle (Bleichenbacher, CRYPTO '98): an adaptive-chosen-ciphertext side channel from which the attacker decrypts any RSA ciphertext to the victim's key or forges any PKCS#1 v1.5 signature under it. 2. When the decryption API (CMS_decrypt(), PKCS7_decrypt()) is provided with the recipient certificate, and the recipient is not found, a random key is substituted. An attacker who authors a message and is able to compare both error code and the result of the decryption, can mount a Bleichenbacher oracle. We are not aware of any applications that provide a remote attacker an opportunity to mount an attack described in these scenarios. We consider the existence of such application very unlikely, and for this reason this CVE has been evaluated as Low severity. To avoid these attacks, when RSA PKCS#1 v1.5 Key Transport is in use, the invoked EVP_PKEY_decrypt() will use the implicit rejection mechanism described in draft-irtf-cfrg-rsa-guidance. In previous OpenSSL releases the implicit rejection was explicitly disabled. The implicit rejection mechanism always returns a plaintext value, the symmetric key. This result is deterministic for the ciphertext and the private key. The length of the decryption result can happen to match the length of the key of the symmetric cipher that was used for the content encryption. When a certificate is not provided, the last RecipientInfo producing a key that looks valid will be used. It may cause getting garbage content on decryption. As a proper way to deal with this a recipient certificate has to be provided to identify the particular RecipientInfo for decryption. The FIPS modules in 4.0, 3.6, 3.5, and 3.4 are not affected by this issue, as CMS and S/MIME processing happens outside the OpenSSL FIPS module boundary.
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libnode72",
"binary_version": "12.22.9~dfsg-1ubuntu3.6+esm2"
},
{
"binary_name": "nodejs",
"binary_version": "12.22.9~dfsg-1ubuntu3.6+esm2"
}
],
"priority_reason": "OpenSSL developers have rated this as being low severity"
},
"package": {
"ecosystem": "Ubuntu:Pro:22.04:LTS",
"name": "nodejs",
"purl": "pkg:deb/ubuntu/nodejs@12.22.9~dfsg-1ubuntu3.6+esm2?arch=source\u0026distro=esm-apps/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"12.22.5~dfsg-5ubuntu1",
"12.22.7~dfsg-2ubuntu1",
"12.22.7~dfsg-2ubuntu3",
"12.22.9~dfsg-1ubuntu2",
"12.22.9~dfsg-1ubuntu3",
"12.22.9~dfsg-1ubuntu3.1",
"12.22.9~dfsg-1ubuntu3.2",
"12.22.9~dfsg-1ubuntu3.3",
"12.22.9~dfsg-1ubuntu3.4",
"12.22.9~dfsg-1ubuntu3.5",
"12.22.9~dfsg-1ubuntu3.6",
"12.22.9~dfsg-1ubuntu3.6+esm2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "efi-shell-aa64",
"binary_version": "2025.02-8ubuntu3.2"
},
{
"binary_name": "efi-shell-arm",
"binary_version": "2025.02-8ubuntu3.2"
},
{
"binary_name": "efi-shell-ia32",
"binary_version": "2025.02-8ubuntu3.2"
},
{
"binary_name": "efi-shell-loongarch64",
"binary_version": "2025.02-8ubuntu3.2"
},
{
"binary_name": "efi-shell-riscv64",
"binary_version": "2025.02-8ubuntu3.2"
},
{
"binary_name": "efi-shell-x64",
"binary_version": "2025.02-8ubuntu3.2"
},
{
"binary_name": "ovmf",
"binary_version": "2025.02-8ubuntu3.2"
},
{
"binary_name": "ovmf-ia32",
"binary_version": "2025.02-8ubuntu3.2"
},
{
"binary_name": "ovmf-inteltdx",
"binary_version": "2025.02-8ubuntu3.2"
},
{
"binary_name": "ovmf-legacy",
"binary_version": "2025.02-8ubuntu3.2"
},
{
"binary_name": "qemu-efi-aarch64",
"binary_version": "2025.02-8ubuntu3.2"
},
{
"binary_name": "qemu-efi-arm",
"binary_version": "2025.02-8ubuntu3.2"
},
{
"binary_name": "qemu-efi-loongarch64",
"binary_version": "2025.02-8ubuntu3.2"
},
{
"binary_name": "qemu-efi-riscv64",
"binary_version": "2025.02-8ubuntu3.2"
}
],
"priority_reason": "OpenSSL developers have rated this as being low severity"
},
"package": {
"ecosystem": "Ubuntu:25.10",
"name": "edk2",
"purl": "pkg:deb/ubuntu/edk2@2025.02-8ubuntu3.2?arch=source\u0026distro=questing"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2025.02-3ubuntu2",
"2025.02-8",
"2025.02-8ubuntu1",
"2025.02-8ubuntu2",
"2025.02-8ubuntu3",
"2025.02-8ubuntu3.1",
"2025.02-8ubuntu3.2"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "libssl3t64",
"binary_version": "3.5.3-1ubuntu3.4"
},
{
"binary_name": "openssl",
"binary_version": "3.5.3-1ubuntu3.4"
},
{
"binary_name": "openssl-provider-legacy",
"binary_version": "3.5.3-1ubuntu3.4"
}
],
"priority_reason": "OpenSSL developers have rated this as being low severity"
},
"package": {
"ecosystem": "Ubuntu:25.10",
"name": "openssl",
"purl": "pkg:deb/ubuntu/openssl@3.5.3-1ubuntu3.4?arch=source\u0026distro=questing"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.5.3-1ubuntu3.4"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.4.1-1ubuntu3",
"3.5.0-2ubuntu1",
"3.5.2-1ubuntu1",
"3.5.3-1ubuntu2",
"3.5.3-1ubuntu3",
"3.5.3-1ubuntu3.3"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "efi-shell-aa64",
"binary_version": "2026.05-2ubuntu3"
},
{
"binary_name": "efi-shell-loongarch64",
"binary_version": "2026.05-2ubuntu3"
},
{
"binary_name": "efi-shell-riscv64",
"binary_version": "2026.05-2ubuntu3"
},
{
"binary_name": "efi-shell-x64",
"binary_version": "2026.05-2ubuntu3"
},
{
"binary_name": "ovmf",
"binary_version": "2026.05-2ubuntu3"
},
{
"binary_name": "ovmf-amdsev",
"binary_version": "2026.05-2ubuntu3"
},
{
"binary_name": "ovmf-generic",
"binary_version": "2026.05-2ubuntu3"
},
{
"binary_name": "ovmf-inteltdx",
"binary_version": "2026.05-2ubuntu3"
},
{
"binary_name": "ovmf-legacy",
"binary_version": "2026.05-2ubuntu3"
},
{
"binary_name": "qemu-efi-aarch64",
"binary_version": "2026.05-2ubuntu3"
},
{
"binary_name": "qemu-efi-loongarch64",
"binary_version": "2026.05-2ubuntu3"
},
{
"binary_name": "qemu-efi-riscv64",
"binary_version": "2026.05-2ubuntu3"
}
],
"priority_reason": "OpenSSL developers have rated this as being low severity"
},
"package": {
"ecosystem": "Ubuntu:26.10",
"name": "edk2",
"purl": "pkg:deb/ubuntu/edk2@2026.05-2ubuntu3?arch=source\u0026distro=stonking"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2025.11-3ubuntu7",
"2025.11-3ubuntu8",
"2026.05-2ubuntu1",
"2026.05-2ubuntu2",
"2026.05-2ubuntu3"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "efi-shell-aa64-hwe",
"binary_version": "2026.05-2ubuntu3"
},
{
"binary_name": "efi-shell-loongarch64-hwe",
"binary_version": "2026.05-2ubuntu3"
},
{
"binary_name": "efi-shell-riscv64-hwe",
"binary_version": "2026.05-2ubuntu3"
},
{
"binary_name": "efi-shell-x64-hwe",
"binary_version": "2026.05-2ubuntu3"
},
{
"binary_name": "ovmf-amdsev-hwe",
"binary_version": "2026.05-2ubuntu3"
},
{
"binary_name": "ovmf-generic-hwe",
"binary_version": "2026.05-2ubuntu3"
},
{
"binary_name": "ovmf-hwe",
"binary_version": "2026.05-2ubuntu3"
},
{
"binary_name": "ovmf-inteltdx-hwe",
"binary_version": "2026.05-2ubuntu3"
},
{
"binary_name": "ovmf-legacy-hwe",
"binary_version": "2026.05-2ubuntu3"
},
{
"binary_name": "qemu-efi-aarch64-hwe",
"binary_version": "2026.05-2ubuntu3"
},
{
"binary_name": "qemu-efi-loongarch64-hwe",
"binary_version": "2026.05-2ubuntu3"
},
{
"binary_name": "qemu-efi-riscv64-hwe",
"binary_version": "2026.05-2ubuntu3"
}
],
"priority_reason": "OpenSSL developers have rated this as being low severity"
},
"package": {
"ecosystem": "Ubuntu:26.10",
"name": "edk2-hwe",
"purl": "pkg:deb/ubuntu/edk2-hwe@2026.05-2ubuntu3?arch=source\u0026distro=stonking"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2025.11-3ubuntu8",
"2025.11-3ubuntu9",
"2026.05-2ubuntu1",
"2026.05-2ubuntu2",
"2026.05-2ubuntu3"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "efi-shell-aa64",
"binary_version": "2025.11-3ubuntu7.3"
},
{
"binary_name": "efi-shell-loongarch64",
"binary_version": "2025.11-3ubuntu7.3"
},
{
"binary_name": "efi-shell-riscv64",
"binary_version": "2025.11-3ubuntu7.3"
},
{
"binary_name": "efi-shell-x64",
"binary_version": "2025.11-3ubuntu7.3"
},
{
"binary_name": "ovmf",
"binary_version": "2025.11-3ubuntu7.3"
},
{
"binary_name": "ovmf-amdsev",
"binary_version": "2025.11-3ubuntu7.3"
},
{
"binary_name": "ovmf-generic",
"binary_version": "2025.11-3ubuntu7.3"
},
{
"binary_name": "ovmf-inteltdx",
"binary_version": "2025.11-3ubuntu7.3"
},
{
"binary_name": "ovmf-legacy",
"binary_version": "2025.11-3ubuntu7.3"
},
{
"binary_name": "qemu-efi-aarch64",
"binary_version": "2025.11-3ubuntu7.3"
},
{
"binary_name": "qemu-efi-loongarch64",
"binary_version": "2025.11-3ubuntu7.3"
},
{
"binary_name": "qemu-efi-riscv64",
"binary_version": "2025.11-3ubuntu7.3"
}
],
"priority_reason": "OpenSSL developers have rated this as being low severity"
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "edk2",
"purl": "pkg:deb/ubuntu/edk2@2025.11-3ubuntu7.3?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2025.02-8ubuntu3",
"2025.11-3ubuntu6",
"2025.11-3ubuntu7",
"2025.11-3ubuntu7.2",
"2025.11-3ubuntu7.3"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "efi-shell-aa64-hwe",
"binary_version": "2025.11-3ubuntu8.2"
},
{
"binary_name": "efi-shell-loongarch64-hwe",
"binary_version": "2025.11-3ubuntu8.2"
},
{
"binary_name": "efi-shell-riscv64-hwe",
"binary_version": "2025.11-3ubuntu8.2"
},
{
"binary_name": "efi-shell-x64-hwe",
"binary_version": "2025.11-3ubuntu8.2"
},
{
"binary_name": "ovmf-amdsev-hwe",
"binary_version": "2025.11-3ubuntu8.2"
},
{
"binary_name": "ovmf-generic-hwe",
"binary_version": "2025.11-3ubuntu8.2"
},
{
"binary_name": "ovmf-hwe",
"binary_version": "2025.11-3ubuntu8.2"
},
{
"binary_name": "ovmf-inteltdx-hwe",
"binary_version": "2025.11-3ubuntu8.2"
},
{
"binary_name": "ovmf-legacy-hwe",
"binary_version": "2025.11-3ubuntu8.2"
},
{
"binary_name": "qemu-efi-aarch64-hwe",
"binary_version": "2025.11-3ubuntu8.2"
},
{
"binary_name": "qemu-efi-loongarch64-hwe",
"binary_version": "2025.11-3ubuntu8.2"
},
{
"binary_name": "qemu-efi-riscv64-hwe",
"binary_version": "2025.11-3ubuntu8.2"
}
],
"priority_reason": "OpenSSL developers have rated this as being low severity"
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "edk2-hwe",
"purl": "pkg:deb/ubuntu/edk2-hwe@2025.11-3ubuntu8.2?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2025.11-3ubuntu6",
"2025.11-3ubuntu8",
"2025.11-3ubuntu8.2"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "libssl3t64",
"binary_version": "3.5.5-1ubuntu3.2"
},
{
"binary_name": "openssl",
"binary_version": "3.5.5-1ubuntu3.2"
},
{
"binary_name": "openssl-provider-legacy",
"binary_version": "3.5.5-1ubuntu3.2"
}
],
"priority_reason": "OpenSSL developers have rated this as being low severity"
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "openssl",
"purl": "pkg:deb/ubuntu/openssl@3.5.5-1ubuntu3.2?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.5.5-1ubuntu3.2"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.5.3-1ubuntu2",
"3.5.5-1ubuntu1",
"3.5.5-1ubuntu3"
]
}
],
"aliases": [],
"details": "Issue summary: The CMS_decrypt and PKCS7_decrypt functions are vulnerable to Bleichenbacher-style attack when an attacker is able to provide the CMS or S/MIME messages and observe the error code and/or decryption output. Impact summary: The Bleichenbacher-style attack allows an attacker to use the victim\u0027s vulnerable application as a way to decrypt or sign messages with the victim\u0027s private RSA key. The attack is possible in 2 variants. 1. The decryption API (CMS_decrypt(), PKCS7_decrypt()) is used without providing the recipient certificate. In this case OpenSSL iterates over every KeyTransRecipientInfo (KTRI) without stopping at the first success. An attacker who authors a message with two KTRI entries \u2014 the first one wrapping a real CEK under the victim\u0027s public key, the second with an arbitrary probe ciphertext \u2014 obtains opportunity to iterate the 2nd KTRI to get a valid PKCS#1 v1.5 padding if the error code of the application is available. That is a Bleichenbacher oracle (Bleichenbacher, CRYPTO \u002798): an adaptive-chosen-ciphertext side channel from which the attacker decrypts any RSA ciphertext to the victim\u0027s key or forges any PKCS#1 v1.5 signature under it. 2. When the decryption API (CMS_decrypt(), PKCS7_decrypt()) is provided with the recipient certificate, and the recipient is not found, a random key is substituted. An attacker who authors a message and is able to compare both error code and the result of the decryption, can mount a Bleichenbacher oracle. We are not aware of any applications that provide a remote attacker an opportunity to mount an attack described in these scenarios. We consider the existence of such application very unlikely, and for this reason this CVE has been evaluated as Low severity. To avoid these attacks, when RSA PKCS#1 v1.5 Key Transport is in use, the invoked EVP_PKEY_decrypt() will use the implicit rejection mechanism described in draft-irtf-cfrg-rsa-guidance. In previous OpenSSL releases the implicit rejection was explicitly disabled. The implicit rejection mechanism always returns a plaintext value, the symmetric key. This result is deterministic for the ciphertext and the private key. The length of the decryption result can happen to match the length of the key of the symmetric cipher that was used for the content encryption. When a certificate is not provided, the last RecipientInfo producing a key that looks valid will be used. It may cause getting garbage content on decryption. As a proper way to deal with this a recipient certificate has to be provided to identify the particular RecipientInfo for decryption. The FIPS modules in 4.0, 3.6, 3.5, and 3.4 are not affected by this issue, as CMS and S/MIME processing happens outside the OpenSSL FIPS module boundary.",
"id": "UBUNTU-CVE-2026-42768",
"modified": "2026-10-17T09:40:59Z",
"published": "2026-06-09T00:00:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-42768"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42768"
},
{
"type": "REPORT",
"url": "https://openssl-library.org/news/secadv/20260609.txt"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-8414-1"
}
],
"related": [
"USN-8414-1"
],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
},
{
"score": "low",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-42768"
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.