Action not permitted
Modal body text goes here.
Modal Title
Modal Body
CVE-2026-42766 (GCVE-0-2026-42766)
Vulnerability from cvelistv5 – Published: 2026-06-09 16:03 – Updated: 2026-06-10 07:48- CWE-476 - NULL Pointer Dereference
{
"containers": {
"adp": [
{
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 5.9,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
}
},
{
"other": {
"content": {
"id": "CVE-2026-42766",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-06-09T19:46:24.673332Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-06-09T19:46:27.585Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "OpenSSL",
"vendor": "OpenSSL",
"versions": [
{
"lessThan": "4.0.1",
"status": "affected",
"version": "4.0.0",
"versionType": "semver"
},
{
"lessThan": "3.6.3",
"status": "affected",
"version": "3.6.0",
"versionType": "semver"
},
{
"lessThan": "3.5.7",
"status": "affected",
"version": "3.5.0",
"versionType": "semver"
},
{
"lessThan": "3.4.6",
"status": "affected",
"version": "3.4.0",
"versionType": "semver"
},
{
"lessThan": "3.0.21",
"status": "affected",
"version": "3.0.0",
"versionType": "semver"
},
{
"lessThan": "1.1.1zh",
"status": "affected",
"version": "1.1.1",
"versionType": "custom"
},
{
"lessThan": "1.0.2zq",
"status": "affected",
"version": "1.0.2",
"versionType": "custom"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "Mayank Jangid"
},
{
"lang": "en",
"type": "reporter",
"value": "Kushal Khemka"
},
{
"lang": "en",
"type": "reporter",
"value": "Hari Priandana"
},
{
"lang": "en",
"type": "reporter",
"value": "Bhabani Sankar Das"
},
{
"lang": "en",
"type": "reporter",
"value": "Qifan Zhang (Palo Alto Networks)"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Igor Ustinov"
}
],
"datePublic": "2026-06-09T14:00:00.000Z",
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "Issue summary: A specially crafted password-encrypted CMS message\u003cbr\u003ecan trigger a NULL pointer dereference during CMS decryption.\u003cbr\u003e\u003cbr\u003eImpact summary: This NULL pointer dereference leads to an application crash\u003cbr\u003eand a Denial of Service.\u003cbr\u003e\u003cbr\u003eThe CMS PasswordRecipientInfo.keyDerivationAlgorithm field is defined as\u003cbr\u003eOPTIONAL in the ASN.1 specification and may therefore be absent in specially\u003cbr\u003ecrafted inputs. During the password-based CMS decryption the OpenSSL\u003cbr\u003eCMS implementation dereferences this field without first checking whether it\u003cbr\u003ewas present.\u003cbr\u003e\u003cbr\u003eAn attacker who supplies such a CMS message to an application performing\u003cbr\u003epassword-based CMS decryption can trigger an application crash, leading to\u003cbr\u003ea Denial of Service.\u003cbr\u003e\u003cbr\u003eApplications that process password-encrypted CMS messages may be affected.\u003cbr\u003e\u003cbr\u003eThe FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this\u003cbr\u003eissue, as the affected code is outside the OpenSSL FIPS module boundary."
}
],
"value": "Issue summary: A specially crafted password-encrypted CMS message\ncan trigger a NULL pointer dereference during CMS decryption.\n\nImpact summary: This NULL pointer dereference leads to an application crash\nand a Denial of Service.\n\nThe CMS PasswordRecipientInfo.keyDerivationAlgorithm field is defined as\nOPTIONAL in the ASN.1 specification and may therefore be absent in specially\ncrafted inputs. During the password-based CMS decryption the OpenSSL\nCMS implementation dereferences this field without first checking whether it\nwas present.\n\nAn attacker who supplies such a CMS message to an application performing\npassword-based CMS decryption can trigger an application crash, leading to\na Denial of Service.\n\nApplications that process password-encrypted CMS messages may be affected.\n\nThe FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this\nissue, as the affected code is outside the OpenSSL FIPS module boundary."
}
],
"metrics": [
{
"format": "other",
"other": {
"content": {
"text": "Low"
},
"type": "https://openssl-library.org/policies/general/security-policy/"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-476",
"description": "CWE-476 NULL Pointer Dereference",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-06-10T07:48:01.992Z",
"orgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"shortName": "openssl"
},
"references": [
{
"name": "OpenSSL Advisory",
"tags": [
"vendor-advisory"
],
"url": "https://openssl-library.org/news/secadv/20260609.txt"
},
{
"name": "4.0.1 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/12bc26ffb3a2be728c9b86e1cae277de5b33dfa4"
},
{
"name": "3.6.3 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/da26f368732b83e40e9d356fe61c3d3aaab6d2e8"
},
{
"name": "3.5.7 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/056d06c1918fafbb98c1c85a02e4c47cc4e199ce"
},
{
"name": "3.4.6 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/ab52d88cb5374876d59aee3c91f9e4ccce2b7ce4"
},
{
"name": "3.0.21 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/3ff64913615d648cfbb6a6f1cf5529ae7ea829d7"
}
],
"source": {
"discovery": "UNKNOWN"
},
"title": "Possible NULL Dereference in Password-Based CMS Decryption",
"x_generator": {
"engine": "Vulnogram 0.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"assignerShortName": "openssl",
"cveId": "CVE-2026-42766",
"datePublished": "2026-06-09T16:03:26.679Z",
"dateReserved": "2026-04-29T09:22:27.968Z",
"dateUpdated": "2026-06-10T07:48:01.992Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-42766",
"date": "2026-11-19",
"epss": "0.0106",
"percentile": "0.65241"
},
"microsoft_vex": {
"current_release_date": "2026-11-16T22:51:16.000Z",
"cve": "CVE-2026-42766",
"id": "msrc_CVE-2026-42766",
"initial_release_date": "2026-06-13T01:05:17.000Z",
"product_status:fixed": "3",
"product_status:known_affected": "3",
"product_status:known_not_affected": "7",
"product_status:under_investigation": "3",
"source": "Microsoft CSAF VEX",
"status": "final",
"title": "Possible NULL Dereference in Password-Based CMS Decryption",
"url": "https://msrc.microsoft.com/csaf/vex/2026/msrc_cve-2026-42766.json",
"version": "9"
},
"redhat_vex": {
"aggregate_severity": "Low",
"current_release_date": "2026-11-07T11:19:04+00:00",
"cve": "CVE-2026-42766",
"id": "CVE-2026-42766",
"initial_release_date": "2026-06-09T00:00:00+00:00",
"product_status:fixed": "207",
"product_status:known_affected": "47",
"product_status:known_not_affected": "124",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "openssl: Possible NULL Dereference in Password-Based CMS Decryption",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-42766.json",
"version": "3"
},
"vulnrichment": {
"containers": {
"adp": [
{
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 5.9,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
}
},
{
"other": {
"content": {
"id": "CVE-2026-42766",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-06-09T19:46:24.673332Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-06-09T19:46:17.520Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "OpenSSL",
"vendor": "OpenSSL",
"versions": [
{
"lessThan": "4.0.1",
"status": "affected",
"version": "4.0.0",
"versionType": "semver"
},
{
"lessThan": "3.6.3",
"status": "affected",
"version": "3.6.0",
"versionType": "semver"
},
{
"lessThan": "3.5.7",
"status": "affected",
"version": "3.5.0",
"versionType": "semver"
},
{
"lessThan": "3.4.6",
"status": "affected",
"version": "3.4.0",
"versionType": "semver"
},
{
"lessThan": "3.0.21",
"status": "affected",
"version": "3.0.0",
"versionType": "semver"
},
{
"lessThan": "1.1.1zh",
"status": "affected",
"version": "1.1.1",
"versionType": "custom"
},
{
"lessThan": "1.0.2zq",
"status": "affected",
"version": "1.0.2",
"versionType": "custom"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "Mayank Jangid"
},
{
"lang": "en",
"type": "reporter",
"value": "Kushal Khemka"
},
{
"lang": "en",
"type": "reporter",
"value": "Hari Priandana"
},
{
"lang": "en",
"type": "reporter",
"value": "Bhabani Sankar Das"
},
{
"lang": "en",
"type": "reporter",
"value": "Qifan Zhang (Palo Alto Networks)"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Igor Ustinov"
}
],
"datePublic": "2026-06-09T14:00:00.000Z",
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "Issue summary: A specially crafted password-encrypted CMS message\u003cbr\u003ecan trigger a NULL pointer dereference during CMS decryption.\u003cbr\u003e\u003cbr\u003eImpact summary: This NULL pointer dereference leads to an application crash\u003cbr\u003eand a Denial of Service.\u003cbr\u003e\u003cbr\u003eThe CMS PasswordRecipientInfo.keyDerivationAlgorithm field is defined as\u003cbr\u003eOPTIONAL in the ASN.1 specification and may therefore be absent in specially\u003cbr\u003ecrafted inputs. During the password-based CMS decryption the OpenSSL\u003cbr\u003eCMS implementation dereferences this field without first checking whether it\u003cbr\u003ewas present.\u003cbr\u003e\u003cbr\u003eAn attacker who supplies such a CMS message to an application performing\u003cbr\u003epassword-based CMS decryption can trigger an application crash, leading to\u003cbr\u003ea Denial of Service.\u003cbr\u003e\u003cbr\u003eApplications that process password-encrypted CMS messages may be affected.\u003cbr\u003e\u003cbr\u003eThe FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this\u003cbr\u003eissue, as the affected code is outside the OpenSSL FIPS module boundary."
}
],
"value": "Issue summary: A specially crafted password-encrypted CMS message\ncan trigger a NULL pointer dereference during CMS decryption.\n\nImpact summary: This NULL pointer dereference leads to an application crash\nand a Denial of Service.\n\nThe CMS PasswordRecipientInfo.keyDerivationAlgorithm field is defined as\nOPTIONAL in the ASN.1 specification and may therefore be absent in specially\ncrafted inputs. During the password-based CMS decryption the OpenSSL\nCMS implementation dereferences this field without first checking whether it\nwas present.\n\nAn attacker who supplies such a CMS message to an application performing\npassword-based CMS decryption can trigger an application crash, leading to\na Denial of Service.\n\nApplications that process password-encrypted CMS messages may be affected.\n\nThe FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this\nissue, as the affected code is outside the OpenSSL FIPS module boundary."
}
],
"metrics": [
{
"format": "other",
"other": {
"content": {
"text": "Low"
},
"type": "https://openssl-library.org/policies/general/security-policy/"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-476",
"description": "CWE-476 NULL Pointer Dereference",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-06-10T07:48:01.992Z",
"orgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"shortName": "openssl"
},
"references": [
{
"name": "OpenSSL Advisory",
"tags": [
"vendor-advisory"
],
"url": "https://openssl-library.org/news/secadv/20260609.txt"
},
{
"name": "4.0.1 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/12bc26ffb3a2be728c9b86e1cae277de5b33dfa4"
},
{
"name": "3.6.3 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/da26f368732b83e40e9d356fe61c3d3aaab6d2e8"
},
{
"name": "3.5.7 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/056d06c1918fafbb98c1c85a02e4c47cc4e199ce"
},
{
"name": "3.4.6 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/ab52d88cb5374876d59aee3c91f9e4ccce2b7ce4"
},
{
"name": "3.0.21 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/3ff64913615d648cfbb6a6f1cf5529ae7ea829d7"
}
],
"source": {
"discovery": "UNKNOWN"
},
"title": "Possible NULL Dereference in Password-Based CMS Decryption",
"x_generator": {
"engine": "Vulnogram 0.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"assignerShortName": "openssl",
"cveId": "CVE-2026-42766",
"datePublished": "2026-06-09T16:03:26.679Z",
"dateReserved": "2026-04-29T09:22:27.968Z",
"dateUpdated": "2026-06-10T07:48:01.992Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
}
}
OESA-2026-2783 (CVE-2026-34180)
Vulnerability from osv_openeuler – Published: 2026-06-24 11:11 – Updated: 2026-08-06 11:11 – Source websiteOpenSSL is a robust, commercial-grade, and full-featured toolkit for the Transport Layer Security (TLS) and Secure Sockets Layer (SSL) protocols.
Security Fix(es):
Issue summary: Parsing a crafted DER-encoded ASN.1 structure with a primitive element whose content exceeds 2 gigabytes in length may cause a heap buffer over-read on 64-bit Unix and Unix-like platforms.
Impact summary: The heap buffer over-read may crash the application (Denial of Service) or to load into the decoded ASN.1 object contents of memory beyond the end of the input buffer. More typically such ASN.1 elements would instead be truncated.
An integer truncation in OpenSSL's ASN.1 decoder causes the content length of an ASN.1 primitive element to be mishandled when it exceeds 2 gigabytes. In the worst case the truncated length is treated as a request to scan the binary content for a terminating zero byte, possibly causing OpenSSL to read either less than or beyond the end of the allocated buffer.
Applications that pass attacker-supplied data to d2i_X509(), d2i_PKCS7(), or any other d2i_* decoding function are affected. OpenSSL's own command-line tools are not vulnerable, as data read through the BIO layer is checked before it reaches the affected code. The issue only affects 64-bit Unix and Unix-like platforms; 32-bit platforms and 64-bit Windows are not affected.
The FIPS modules in 4.0, 3.6, 3.5, 3.4 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.(CVE-2026-34180)
Issue summary: A specially crafted password-encrypted CMS message can trigger a NULL pointer dereference during CMS decryption.
Impact summary: This NULL pointer dereference leads to an application crash and a Denial of Service.
The CMS PasswordRecipientInfo.keyDerivationAlgorithm field is defined as OPTIONAL in the ASN.1 specification and may therefore be absent in specially crafted inputs. During the password-based CMS decryption the OpenSSL CMS implementation dereferences this field without first checking whether it was present.
An attacker who supplies such a CMS message to an application performing password-based CMS decryption can trigger an application crash, leading to a Denial of Service.
Applications that process password-encrypted CMS messages may be affected.
The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.(CVE-2026-42766)
Issue summary: A specially crafted PKCS#7 or S/MIME signed message could trigger a use-after-free during PKCS#7 signature verification.
Impact summary: A use-after-free may result in process crashes, heap corruption, or potentially remote code execution.
When processing a PKCS#7 or S/MIME signed message, if the SignedData digestAlgorithms field is present as an empty ASN.1 SET, OpenSSL may incorrectly free a caller-owned BIO during PKCS7_verify(). A subsequent use of the BIO by the calling application results in a use-after-free condition.
In the common case this occurs when the application later calls BIO_free() on the BIO originally passed to PKCS7_verify(). Depending on allocator behavior and application-specific BIO usage patterns, this may result in a crash or other memory corruption. In some application contexts this may potentially be exploitable for remote code execution.
Applications that process PKCS#7 or S/MIME signed messages using OpenSSL PKCS#7 APIs may be affected. Applications using the CMS APIs for this processing are not affected.
The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.(CVE-2026-45447)
Issue summary: A signed integer overflow when sizing the destination buffer for Unicode output in ASN1_mbstring_ncopy() can lead to a heap buffer overflow.
Impact summary: A heap buffer overflow may lead to a crash or possibly attacker controlled code execution or other undefined behaviour.
In ASN1_mbstring_copy() and ASN1_mbstring_ncopy() the destination size for Unicode output is computed in a signed int: by left shift of the input character count for BMPSTRING (UTF-16) and UNIVERSALSTRING (UTF-32), and by summing per-character byte counts for UTF8STRING. The calculation overflows when the input reaches around 2^30 characters. In the worst case (UNIVERSALSTRING at 2^30 characters) the size wraps to zero, OPENSSL_malloc(1) is called, and the subsequent character copy writes several gigabytes past the one-byte allocation.
X.509 certificate processing routes through ASN1_STRING_set_by_NID(), whose DIRSTRING_TYPE mask excludes UNIVERSALSTRING and whose per-NID size limits cap the input length; no network protocol or certificate-handling path in OpenSSL exercises the overflow. Triggering the bug requires an application that calls ASN1_mbstring_copy() or ASN1_mbstring_ncopy() directly, or registers a custom string type via ASN1_STRING_TABLE_add(), with attacker-controlled input on the order of half a gigabyte or more. For these reasons this issue was assigned Low severity.
The FIPS modules in 4.0, 3.6, 3.5, 3.4 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.(CVE-2026-7383)
Issue summary: When CMS password-based decryption (RFC 3211 / PWRI key unwrap) processes attacker-supplied CMS data, an attacker-chosen stream-mode KEK cipher can trigger a heap out-of-bounds read in kek_unwrap_key().
Impact summary: A heap buffer over-read may trigger a crash which leads to Denial of Service for an application if the input buffer ends at a memory page boundary and the following page is unmapped. There is no information disclosure as the over-read bytes are not revealed to the attacker.
The key unwrapping function performs a check-byte test as specified in the RFC that reads 7 bytes from a heap allocation that is based on the wrapped key length from the message. There is a minimum length check based on the block length of the wrapping cipher. However the cipher is selected from an OID carried in the attacker's PWRI keyEncryptionAlgorithm with no requirement that the cipher be a block cipher. When an attacker selects a stream-mode cipher the guard will be ineffective and the allocated buffer containing the unwrapped key can be too small to fit the check-bytes specified in the RFC and a buffer over-read can happen.
Applications calling CMS_decrypt() or CMS_decrypt_set1_password() (equivalently openssl cms -decrypt -pwri_password ...) on untrusted CMS data are vulnerable to this issue. No password knowledge is required: the over-read happens during the unwrap attempt before any authentication succeeds.
The over-read is limited to a few bytes and is not written to output, so there is no information disclosure. Triggering a crash requires the allocation to border unmapped memory, which is unlikely with the normal allocator.
The FIPS modules are not affected by this issue.(CVE-2026-9076)
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"openssl-1.1.1f-43.oe2003sp4.aarch64.rpm",
"openssl-debuginfo-1.1.1f-43.oe2003sp4.aarch64.rpm",
"openssl-debugsource-1.1.1f-43.oe2003sp4.aarch64.rpm",
"openssl-devel-1.1.1f-43.oe2003sp4.aarch64.rpm",
"openssl-libs-1.1.1f-43.oe2003sp4.aarch64.rpm"
],
"noarch": [
"openssl-help-1.1.1f-43.oe2003sp4.noarch.rpm"
],
"src": [
"openssl-1.1.1f-43.oe2003sp4.src.rpm"
],
"x86_64": [
"openssl-1.1.1f-43.oe2003sp4.x86_64.rpm",
"openssl-debuginfo-1.1.1f-43.oe2003sp4.x86_64.rpm",
"openssl-debugsource-1.1.1f-43.oe2003sp4.x86_64.rpm",
"openssl-devel-1.1.1f-43.oe2003sp4.x86_64.rpm",
"openssl-libs-1.1.1f-43.oe2003sp4.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:20.03-LTS-SP4",
"name": "openssl",
"purl": "pkg:rpm/openEuler/openssl\u0026distro=openEuler-20.03-LTS-SP4"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.1.1f-43.oe2003sp4"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "High"
},
"details": "OpenSSL is a robust, commercial-grade, and full-featured toolkit for the Transport Layer Security (TLS) and Secure Sockets Layer (SSL) protocols.\r\n\r\nSecurity Fix(es):\n\nIssue summary: Parsing a crafted DER-encoded ASN.1 structure with a primitive\nelement whose content exceeds 2 gigabytes in length may cause a heap buffer\nover-read on 64-bit Unix and Unix-like platforms.\n\nImpact summary: The heap buffer over-read may crash the application (Denial of\nService) or to load into the decoded ASN.1 object contents of memory beyond the\nend of the input buffer. More typically such ASN.1 elements would instead be\ntruncated.\n\nAn integer truncation in OpenSSL\u0026apos;s ASN.1 decoder causes the content length of\nan ASN.1 primitive element to be mishandled when it exceeds 2 gigabytes. In the\nworst case the truncated length is treated as a request to scan the binary\ncontent for a terminating zero byte, possibly causing OpenSSL to read either\nless than or beyond the end of the allocated buffer.\n\nApplications that pass attacker-supplied data to d2i_X509(), d2i_PKCS7(), or\nany other d2i_* decoding function are affected. OpenSSL\u0026apos;s own command-line\ntools are not vulnerable, as data read through the BIO layer is checked before\nit reaches the affected code. The issue only affects 64-bit Unix and Unix-like\nplatforms; 32-bit platforms and 64-bit Windows are not affected.\n\nThe FIPS modules in 4.0, 3.6, 3.5, 3.4 and 3.0 are not affected by this issue,\nas the affected code is outside the OpenSSL FIPS module boundary.(CVE-2026-34180)\n\nIssue summary: A specially crafted password-encrypted CMS message\ncan trigger a NULL pointer dereference during CMS decryption.\n\nImpact summary: This NULL pointer dereference leads to an application crash\nand a Denial of Service.\n\nThe CMS PasswordRecipientInfo.keyDerivationAlgorithm field is defined as\nOPTIONAL in the ASN.1 specification and may therefore be absent in specially\ncrafted inputs. During the password-based CMS decryption the OpenSSL\nCMS implementation dereferences this field without first checking whether it\nwas present.\n\nAn attacker who supplies such a CMS message to an application performing\npassword-based CMS decryption can trigger an application crash, leading to\na Denial of Service.\n\nApplications that process password-encrypted CMS messages may be affected.\n\nThe FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this\nissue, as the affected code is outside the OpenSSL FIPS module boundary.(CVE-2026-42766)\n\nIssue summary: A specially crafted PKCS#7 or S/MIME signed message could\ntrigger a use-after-free during PKCS#7 signature verification.\n\nImpact summary: A use-after-free may result in process crashes, heap\ncorruption, or potentially remote code execution.\n\nWhen processing a PKCS#7 or S/MIME signed message, if the SignedData\ndigestAlgorithms field is present as an empty ASN.1 SET, OpenSSL may\nincorrectly free a caller-owned BIO during PKCS7_verify(). A subsequent\nuse of the BIO by the calling application results in a use-after-free\ncondition.\n\nIn the common case this occurs when the application later calls\nBIO_free() on the BIO originally passed to PKCS7_verify(). Depending\non allocator behavior and application-specific BIO usage patterns, this\nmay result in a crash or other memory corruption. In some application\ncontexts this may potentially be exploitable for remote code execution.\n\nApplications that process PKCS#7 or S/MIME signed messages using OpenSSL\nPKCS#7 APIs may be affected. Applications using the CMS APIs for this\nprocessing are not affected.\n\nThe FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this\nissue, as the affected code is outside the OpenSSL FIPS module boundary.(CVE-2026-45447)\n\nIssue summary: A signed integer overflow when sizing the destination\nbuffer for Unicode output in ASN1_mbstring_ncopy() can lead to a heap\nbuffer overflow.\n\nImpact summary: A heap buffer overflow may lead to a crash or possibly\nattacker controlled code execution or other undefined behaviour.\n\nIn ASN1_mbstring_copy() and ASN1_mbstring_ncopy() the destination\nsize for Unicode output is computed in a signed int: by left shift\nof the input character count for BMPSTRING (UTF-16) and\nUNIVERSALSTRING (UTF-32), and by summing per-character byte counts\nfor UTF8STRING. The calculation overflows when the input reaches\naround 2^30 characters. In the worst case (UNIVERSALSTRING at 2^30\ncharacters) the size wraps to zero, OPENSSL_malloc(1) is called, and\nthe subsequent character copy writes several gigabytes past the\none-byte allocation.\n\nX.509 certificate processing routes through ASN1_STRING_set_by_NID(),\nwhose DIRSTRING_TYPE mask excludes UNIVERSALSTRING and whose per-NID\nsize limits cap the input length; no network protocol or\ncertificate-handling path in OpenSSL exercises the overflow.\nTriggering the bug requires an application that calls\nASN1_mbstring_copy() or ASN1_mbstring_ncopy() directly, or registers\na custom string type via ASN1_STRING_TABLE_add(), with\nattacker-controlled input on the order of half a gigabyte or more.\nFor these reasons this issue was assigned Low severity.\n\nThe FIPS modules in 4.0, 3.6, 3.5, 3.4 and 3.0 are not affected by\nthis issue, as the affected code is outside the OpenSSL FIPS module\nboundary.(CVE-2026-7383)\n\nIssue summary: When CMS password-based decryption (RFC 3211 / PWRI key unwrap)\nprocesses attacker-supplied CMS data, an attacker-chosen stream-mode KEK\ncipher can trigger a heap out-of-bounds read in kek_unwrap_key().\n\nImpact summary: A heap buffer over-read may trigger a crash which leads to\nDenial of Service for an application if the input buffer ends at a memory\npage boundary and the following page is unmapped. There is no information\ndisclosure as the over-read bytes are not revealed to the attacker.\n\nThe key unwrapping function performs a check-byte test as specified in the\nRFC that reads 7 bytes from a heap allocation that is based on the wrapped\nkey length from the message. There is a minimum length check based on the\nblock length of the wrapping cipher. However the cipher is selected from\nan OID carried in the attacker\u0026apos;s PWRI keyEncryptionAlgorithm with no\nrequirement that the cipher be a block cipher. When an attacker selects\na stream-mode cipher the guard will be ineffective and the allocated buffer\ncontaining the unwrapped key can be too small to fit the check-bytes\nspecified in the RFC and a buffer over-read can happen.\n\nApplications calling CMS_decrypt() or CMS_decrypt_set1_password()\n(equivalently openssl cms -decrypt -pwri_password ...) on untrusted CMS\ndata are vulnerable to this issue. No password knowledge is required: the\nover-read happens during the unwrap attempt before any authentication\nsucceeds.\n\nThe over-read is limited to a few bytes and is not written to output, so\nthere is no information disclosure. Triggering a crash requires the\nallocation to border unmapped memory, which is unlikely with the normal\nallocator.\n\nThe FIPS modules are not affected by this issue.(CVE-2026-9076)",
"id": "OESA-2026-2783",
"modified": "2026-08-06T11:11:42Z",
"published": "2026-06-24T11:11:42Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-2783"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-34180"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-42766"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-45447"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-7383"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-9076"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "openssl security update",
"upstream": [
"CVE-2026-34180",
"CVE-2026-42766",
"CVE-2026-45447",
"CVE-2026-7383",
"CVE-2026-9076"
]
}
OESA-2026-2784 (CVE-2026-34180)
Vulnerability from osv_openeuler – Published: 2026-06-24 11:11 – Updated: 2026-08-06 11:11 – Source websiteOpenSSL is a robust, commercial-grade, and full-featured toolkit for the Transport Layer Security (TLS) and Secure Sockets Layer (SSL) protocols.
Security Fix(es):
Issue summary: Parsing a crafted DER-encoded ASN.1 structure with a primitive element whose content exceeds 2 gigabytes in length may cause a heap buffer over-read on 64-bit Unix and Unix-like platforms.
Impact summary: The heap buffer over-read may crash the application (Denial of Service) or to load into the decoded ASN.1 object contents of memory beyond the end of the input buffer. More typically such ASN.1 elements would instead be truncated.
An integer truncation in OpenSSL's ASN.1 decoder causes the content length of an ASN.1 primitive element to be mishandled when it exceeds 2 gigabytes. In the worst case the truncated length is treated as a request to scan the binary content for a terminating zero byte, possibly causing OpenSSL to read either less than or beyond the end of the allocated buffer.
Applications that pass attacker-supplied data to d2i_X509(), d2i_PKCS7(), or any other d2i_* decoding function are affected. OpenSSL's own command-line tools are not vulnerable, as data read through the BIO layer is checked before it reaches the affected code. The issue only affects 64-bit Unix and Unix-like platforms; 32-bit platforms and 64-bit Windows are not affected.
The FIPS modules in 4.0, 3.6, 3.5, 3.4 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.(CVE-2026-34180)
Issue summary: A specially crafted password-encrypted CMS message can trigger a NULL pointer dereference during CMS decryption.
Impact summary: This NULL pointer dereference leads to an application crash and a Denial of Service.
The CMS PasswordRecipientInfo.keyDerivationAlgorithm field is defined as OPTIONAL in the ASN.1 specification and may therefore be absent in specially crafted inputs. During the password-based CMS decryption the OpenSSL CMS implementation dereferences this field without first checking whether it was present.
An attacker who supplies such a CMS message to an application performing password-based CMS decryption can trigger an application crash, leading to a Denial of Service.
Applications that process password-encrypted CMS messages may be affected.
The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.(CVE-2026-42766)
Issue summary: A specially crafted PKCS#7 or S/MIME signed message could trigger a use-after-free during PKCS#7 signature verification.
Impact summary: A use-after-free may result in process crashes, heap corruption, or potentially remote code execution.
When processing a PKCS#7 or S/MIME signed message, if the SignedData digestAlgorithms field is present as an empty ASN.1 SET, OpenSSL may incorrectly free a caller-owned BIO during PKCS7_verify(). A subsequent use of the BIO by the calling application results in a use-after-free condition.
In the common case this occurs when the application later calls BIO_free() on the BIO originally passed to PKCS7_verify(). Depending on allocator behavior and application-specific BIO usage patterns, this may result in a crash or other memory corruption. In some application contexts this may potentially be exploitable for remote code execution.
Applications that process PKCS#7 or S/MIME signed messages using OpenSSL PKCS#7 APIs may be affected. Applications using the CMS APIs for this processing are not affected.
The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.(CVE-2026-45447)
Issue summary: A signed integer overflow when sizing the destination buffer for Unicode output in ASN1_mbstring_ncopy() can lead to a heap buffer overflow.
Impact summary: A heap buffer overflow may lead to a crash or possibly attacker controlled code execution or other undefined behaviour.
In ASN1_mbstring_copy() and ASN1_mbstring_ncopy() the destination size for Unicode output is computed in a signed int: by left shift of the input character count for BMPSTRING (UTF-16) and UNIVERSALSTRING (UTF-32), and by summing per-character byte counts for UTF8STRING. The calculation overflows when the input reaches around 2^30 characters. In the worst case (UNIVERSALSTRING at 2^30 characters) the size wraps to zero, OPENSSL_malloc(1) is called, and the subsequent character copy writes several gigabytes past the one-byte allocation.
X.509 certificate processing routes through ASN1_STRING_set_by_NID(), whose DIRSTRING_TYPE mask excludes UNIVERSALSTRING and whose per-NID size limits cap the input length; no network protocol or certificate-handling path in OpenSSL exercises the overflow. Triggering the bug requires an application that calls ASN1_mbstring_copy() or ASN1_mbstring_ncopy() directly, or registers a custom string type via ASN1_STRING_TABLE_add(), with attacker-controlled input on the order of half a gigabyte or more. For these reasons this issue was assigned Low severity.
The FIPS modules in 4.0, 3.6, 3.5, 3.4 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.(CVE-2026-7383)
Issue summary: When CMS password-based decryption (RFC 3211 / PWRI key unwrap) processes attacker-supplied CMS data, an attacker-chosen stream-mode KEK cipher can trigger a heap out-of-bounds read in kek_unwrap_key().
Impact summary: A heap buffer over-read may trigger a crash which leads to Denial of Service for an application if the input buffer ends at a memory page boundary and the following page is unmapped. There is no information disclosure as the over-read bytes are not revealed to the attacker.
The key unwrapping function performs a check-byte test as specified in the RFC that reads 7 bytes from a heap allocation that is based on the wrapped key length from the message. There is a minimum length check based on the block length of the wrapping cipher. However the cipher is selected from an OID carried in the attacker's PWRI keyEncryptionAlgorithm with no requirement that the cipher be a block cipher. When an attacker selects a stream-mode cipher the guard will be ineffective and the allocated buffer containing the unwrapped key can be too small to fit the check-bytes specified in the RFC and a buffer over-read can happen.
Applications calling CMS_decrypt() or CMS_decrypt_set1_password() (equivalently openssl cms -decrypt -pwri_password ...) on untrusted CMS data are vulnerable to this issue. No password knowledge is required: the over-read happens during the unwrap attempt before any authentication succeeds.
The over-read is limited to a few bytes and is not written to output, so there is no information disclosure. Triggering a crash requires the allocation to border unmapped memory, which is unlikely with the normal allocator.
The FIPS modules are not affected by this issue.(CVE-2026-9076)
| URL | Type | |||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"openssl-1.1.1wa-17.oe2203sp4.aarch64.rpm",
"openssl-debuginfo-1.1.1wa-17.oe2203sp4.aarch64.rpm",
"openssl-debugsource-1.1.1wa-17.oe2203sp4.aarch64.rpm",
"openssl-devel-1.1.1wa-17.oe2203sp4.aarch64.rpm",
"openssl-libs-1.1.1wa-17.oe2203sp4.aarch64.rpm",
"openssl-perl-1.1.1wa-17.oe2203sp4.aarch64.rpm"
],
"noarch": [
"openssl-help-1.1.1wa-17.oe2203sp4.noarch.rpm"
],
"src": [
"openssl-1.1.1wa-17.oe2203sp4.src.rpm"
],
"x86_64": [
"openssl-1.1.1wa-17.oe2203sp4.x86_64.rpm",
"openssl-debuginfo-1.1.1wa-17.oe2203sp4.x86_64.rpm",
"openssl-debugsource-1.1.1wa-17.oe2203sp4.x86_64.rpm",
"openssl-devel-1.1.1wa-17.oe2203sp4.x86_64.rpm",
"openssl-libs-1.1.1wa-17.oe2203sp4.x86_64.rpm",
"openssl-perl-1.1.1wa-17.oe2203sp4.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:22.03-LTS-SP4",
"name": "openssl",
"purl": "pkg:rpm/openEuler/openssl\u0026distro=openEuler-22.03-LTS-SP4"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.1.1wa-17.oe2203sp4"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "High"
},
"details": "OpenSSL is a robust, commercial-grade, and full-featured toolkit for the Transport Layer Security (TLS) and Secure Sockets Layer (SSL) protocols.\r\n\r\nSecurity Fix(es):\n\nIssue summary: Parsing a crafted DER-encoded ASN.1 structure with a primitive\nelement whose content exceeds 2 gigabytes in length may cause a heap buffer\nover-read on 64-bit Unix and Unix-like platforms.\n\nImpact summary: The heap buffer over-read may crash the application (Denial of\nService) or to load into the decoded ASN.1 object contents of memory beyond the\nend of the input buffer. More typically such ASN.1 elements would instead be\ntruncated.\n\nAn integer truncation in OpenSSL\u0026apos;s ASN.1 decoder causes the content length of\nan ASN.1 primitive element to be mishandled when it exceeds 2 gigabytes. In the\nworst case the truncated length is treated as a request to scan the binary\ncontent for a terminating zero byte, possibly causing OpenSSL to read either\nless than or beyond the end of the allocated buffer.\n\nApplications that pass attacker-supplied data to d2i_X509(), d2i_PKCS7(), or\nany other d2i_* decoding function are affected. OpenSSL\u0026apos;s own command-line\ntools are not vulnerable, as data read through the BIO layer is checked before\nit reaches the affected code. The issue only affects 64-bit Unix and Unix-like\nplatforms; 32-bit platforms and 64-bit Windows are not affected.\n\nThe FIPS modules in 4.0, 3.6, 3.5, 3.4 and 3.0 are not affected by this issue,\nas the affected code is outside the OpenSSL FIPS module boundary.(CVE-2026-34180)\n\nIssue summary: A specially crafted password-encrypted CMS message\ncan trigger a NULL pointer dereference during CMS decryption.\n\nImpact summary: This NULL pointer dereference leads to an application crash\nand a Denial of Service.\n\nThe CMS PasswordRecipientInfo.keyDerivationAlgorithm field is defined as\nOPTIONAL in the ASN.1 specification and may therefore be absent in specially\ncrafted inputs. During the password-based CMS decryption the OpenSSL\nCMS implementation dereferences this field without first checking whether it\nwas present.\n\nAn attacker who supplies such a CMS message to an application performing\npassword-based CMS decryption can trigger an application crash, leading to\na Denial of Service.\n\nApplications that process password-encrypted CMS messages may be affected.\n\nThe FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this\nissue, as the affected code is outside the OpenSSL FIPS module boundary.(CVE-2026-42766)\n\nIssue summary: A specially crafted PKCS#7 or S/MIME signed message could\ntrigger a use-after-free during PKCS#7 signature verification.\n\nImpact summary: A use-after-free may result in process crashes, heap\ncorruption, or potentially remote code execution.\n\nWhen processing a PKCS#7 or S/MIME signed message, if the SignedData\ndigestAlgorithms field is present as an empty ASN.1 SET, OpenSSL may\nincorrectly free a caller-owned BIO during PKCS7_verify(). A subsequent\nuse of the BIO by the calling application results in a use-after-free\ncondition.\n\nIn the common case this occurs when the application later calls\nBIO_free() on the BIO originally passed to PKCS7_verify(). Depending\non allocator behavior and application-specific BIO usage patterns, this\nmay result in a crash or other memory corruption. In some application\ncontexts this may potentially be exploitable for remote code execution.\n\nApplications that process PKCS#7 or S/MIME signed messages using OpenSSL\nPKCS#7 APIs may be affected. Applications using the CMS APIs for this\nprocessing are not affected.\n\nThe FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this\nissue, as the affected code is outside the OpenSSL FIPS module boundary.(CVE-2026-45447)\n\nIssue summary: A signed integer overflow when sizing the destination\nbuffer for Unicode output in ASN1_mbstring_ncopy() can lead to a heap\nbuffer overflow.\n\nImpact summary: A heap buffer overflow may lead to a crash or possibly\nattacker controlled code execution or other undefined behaviour.\n\nIn ASN1_mbstring_copy() and ASN1_mbstring_ncopy() the destination\nsize for Unicode output is computed in a signed int: by left shift\nof the input character count for BMPSTRING (UTF-16) and\nUNIVERSALSTRING (UTF-32), and by summing per-character byte counts\nfor UTF8STRING. The calculation overflows when the input reaches\naround 2^30 characters. In the worst case (UNIVERSALSTRING at 2^30\ncharacters) the size wraps to zero, OPENSSL_malloc(1) is called, and\nthe subsequent character copy writes several gigabytes past the\none-byte allocation.\n\nX.509 certificate processing routes through ASN1_STRING_set_by_NID(),\nwhose DIRSTRING_TYPE mask excludes UNIVERSALSTRING and whose per-NID\nsize limits cap the input length; no network protocol or\ncertificate-handling path in OpenSSL exercises the overflow.\nTriggering the bug requires an application that calls\nASN1_mbstring_copy() or ASN1_mbstring_ncopy() directly, or registers\na custom string type via ASN1_STRING_TABLE_add(), with\nattacker-controlled input on the order of half a gigabyte or more.\nFor these reasons this issue was assigned Low severity.\n\nThe FIPS modules in 4.0, 3.6, 3.5, 3.4 and 3.0 are not affected by\nthis issue, as the affected code is outside the OpenSSL FIPS module\nboundary.(CVE-2026-7383)\n\nIssue summary: When CMS password-based decryption (RFC 3211 / PWRI key unwrap)\nprocesses attacker-supplied CMS data, an attacker-chosen stream-mode KEK\ncipher can trigger a heap out-of-bounds read in kek_unwrap_key().\n\nImpact summary: A heap buffer over-read may trigger a crash which leads to\nDenial of Service for an application if the input buffer ends at a memory\npage boundary and the following page is unmapped. There is no information\ndisclosure as the over-read bytes are not revealed to the attacker.\n\nThe key unwrapping function performs a check-byte test as specified in the\nRFC that reads 7 bytes from a heap allocation that is based on the wrapped\nkey length from the message. There is a minimum length check based on the\nblock length of the wrapping cipher. However the cipher is selected from\nan OID carried in the attacker\u0026apos;s PWRI keyEncryptionAlgorithm with no\nrequirement that the cipher be a block cipher. When an attacker selects\na stream-mode cipher the guard will be ineffective and the allocated buffer\ncontaining the unwrapped key can be too small to fit the check-bytes\nspecified in the RFC and a buffer over-read can happen.\n\nApplications calling CMS_decrypt() or CMS_decrypt_set1_password()\n(equivalently openssl cms -decrypt -pwri_password ...) on untrusted CMS\ndata are vulnerable to this issue. No password knowledge is required: the\nover-read happens during the unwrap attempt before any authentication\nsucceeds.\n\nThe over-read is limited to a few bytes and is not written to output, so\nthere is no information disclosure. Triggering a crash requires the\nallocation to border unmapped memory, which is unlikely with the normal\nallocator.\n\nThe FIPS modules are not affected by this issue.(CVE-2026-9076)",
"id": "OESA-2026-2784",
"modified": "2026-08-06T11:11:42Z",
"published": "2026-06-24T11:11:42Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-2784"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-34180"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-42766"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-45447"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-7383"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-9076"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "openssl security update",
"upstream": [
"CVE-2026-34180",
"CVE-2026-42766",
"CVE-2026-45447",
"CVE-2026-7383",
"CVE-2026-9076"
]
}
OESA-2026-3002 (CVE-2026-42766)
Vulnerability from osv_openeuler – Published: 2026-07-19 11:11 – Updated: 2026-08-06 11:11 – Source websiteEDK II is a modern, feature-rich, cross-platform firmware development environment for the UEFI and PI specifications.
Security Fix(es):
Issue summary: A specially crafted password-encrypted CMS message can trigger a NULL pointer dereference during CMS decryption.
Impact summary: This NULL pointer dereference leads to an application crash and a Denial of Service.
The CMS PasswordRecipientInfo.keyDerivationAlgorithm field is defined as OPTIONAL in the ASN.1 specification and may therefore be absent in specially crafted inputs. During the password-based CMS decryption the OpenSSL CMS implementation dereferences this field without first checking whether it was present.
An attacker who supplies such a CMS message to an application performing password-based CMS decryption can trigger an application crash, leading to a Denial of Service.
Applications that process password-encrypted CMS messages may be affected.
The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.(CVE-2026-42766)
Issue summary: An attacker-controlled CMP (Certificate Management Protocol) server could trigger a NULL pointer dereference in a CMP client application.
Impact summary: A NULL pointer dereference causes a crash of the application and a Denial of Service.
An attacker controlling a CMP server (or acting as a man-in-the-middle) could craft a CMP response containing a CRMF (Certificate Request Message Format) CertRepMessage with an EncryptedValue structure where the symmAlg field has an algorithm OID but no parameters field. When the OpenSSL CMP client processes this response, the NULL dereference occurs, causing a crash of the CMP client.
Applications that process untrusted CMP/CRMF messages may be affected.
The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.(CVE-2026-42767)
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'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.
- 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.
- 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.(CVE-2026-42768)
| URL | Type | |
|---|---|---|
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"edk2-debuginfo-202308-45.oe2403sp3.aarch64.rpm",
"edk2-debugsource-202308-45.oe2403sp3.aarch64.rpm",
"edk2-devel-202308-45.oe2403sp3.aarch64.rpm"
],
"noarch": [
"edk2-aarch64-202308-45.oe2403sp3.noarch.rpm",
"edk2-help-202308-45.oe2403sp3.noarch.rpm",
"edk2-ovmf-202308-45.oe2403sp3.noarch.rpm",
"python3-edk2-devel-202308-45.oe2403sp3.noarch.rpm"
],
"src": [
"edk2-202308-45.oe2403sp3.src.rpm"
],
"x86_64": [
"edk2-debuginfo-202308-45.oe2403sp3.x86_64.rpm",
"edk2-debugsource-202308-45.oe2403sp3.x86_64.rpm",
"edk2-devel-202308-45.oe2403sp3.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:24.03-LTS-SP3",
"name": "edk2",
"purl": "pkg:rpm/openEuler/edk2\u0026distro=openEuler-24.03-LTS-SP3"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "202308-45.oe2403sp3"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "Medium"
},
"details": "EDK II is a modern, feature-rich, cross-platform firmware development environment for the UEFI and PI specifications.\r\n\r\nSecurity Fix(es):\n\nIssue summary: A specially crafted password-encrypted CMS message\ncan trigger a NULL pointer dereference during CMS decryption.\n\nImpact summary: This NULL pointer dereference leads to an application crash\nand a Denial of Service.\n\nThe CMS PasswordRecipientInfo.keyDerivationAlgorithm field is defined as\nOPTIONAL in the ASN.1 specification and may therefore be absent in specially\ncrafted inputs. During the password-based CMS decryption the OpenSSL\nCMS implementation dereferences this field without first checking whether it\nwas present.\n\nAn attacker who supplies such a CMS message to an application performing\npassword-based CMS decryption can trigger an application crash, leading to\na Denial of Service.\n\nApplications that process password-encrypted CMS messages may be affected.\n\nThe FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this\nissue, as the affected code is outside the OpenSSL FIPS module boundary.(CVE-2026-42766)\n\nIssue summary: An attacker-controlled CMP (Certificate Management Protocol)\nserver could trigger a NULL pointer dereference in a CMP client application.\n\nImpact summary: A NULL pointer dereference causes a crash of the\napplication and a Denial of Service.\n\nAn attacker controlling a CMP server (or acting as a man-in-the-middle) could\ncraft a CMP response containing a CRMF (Certificate Request Message Format)\nCertRepMessage with an EncryptedValue structure where the symmAlg field\nhas an algorithm OID but no parameters field. When the OpenSSL CMP client\nprocesses this response, the NULL dereference occurs, causing a crash of\nthe CMP client.\n\nApplications that process untrusted CMP/CRMF messages may be affected.\n\nThe FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this\nissue, as the affected code is outside the OpenSSL FIPS module boundary.(CVE-2026-42767)\n\nIssue summary: The CMS_decrypt and PKCS7_decrypt functions are vulnerable to\nBleichenbacher-style attack when an attacker is able to provide the CMS or\nS/MIME messages and observe the error code and/or decryption output.\n\nImpact summary: The Bleichenbacher-style attack allows an attacker to use the\nvictim\u0026apos;s vulnerable application as a way to decrypt or sign messages with the\nvictim\u0026apos;s private RSA key.\n\nThe attack is possible in 2 variants.\n\n1. The decryption API (CMS_decrypt(), PKCS7_decrypt()) is used without\nproviding the recipient certificate. In this case OpenSSL iterates over every\nKeyTransRecipientInfo (KTRI) without stopping at the first success.\n\nAn attacker who authors a message with two KTRI entries \u2014 the first one\nwrapping a real CEK under the victim\u0026apos;s public key, the second with an\narbitrary probe ciphertext \u2014 obtains opportunity to iterate the 2nd KTRI to\nget a valid PKCS#1 v1.5 padding if the error code of the application is\navailable.\n\nThat is a Bleichenbacher oracle (Bleichenbacher, CRYPTO \u0026apos;98): an\nadaptive-chosen-ciphertext side channel from which the attacker decrypts any\nRSA ciphertext to the victim\u0026apos;s key or forges any PKCS#1 v1.5 signature under\nit.\n\n2. When the decryption API (CMS_decrypt(), PKCS7_decrypt()) is provided with\nthe recipient certificate, and the recipient is not found, a random\nkey is substituted.\n\nAn attacker who authors a message and is able to compare both error code and\nthe result of the decryption, can mount a Bleichenbacher oracle.\n\nWe are not aware of any applications that provide a remote attacker\nan opportunity to mount an attack described in these scenarios. We consider\nthe existence of such application very unlikely, and for this reason this\nCVE has been evaluated as Low severity.\n\nTo avoid these attacks, when RSA PKCS#1 v1.5 Key Transport is in use, the\ninvoked EVP_PKEY_decrypt() will use the implicit rejection mechanism described\nin draft-irtf-cfrg-rsa-guidance. In previous OpenSSL releases the implicit\nrejection was explicitly disabled.\n\nThe implicit rejection mechanism always returns a plaintext value,\nthe symmetric key. This result is deterministic for the ciphertext and the\nprivate key. The length of the decryption result can happen to match the\nlength of the key of the symmetric cipher that was used for the content\nencryption. When a certificate is not provided, the last RecipientInfo\nproducing a key that looks valid will be used. It may cause getting garbage\ncontent on decryption. As a proper way to deal with this a recipient\ncertificate has to be provided to identify the particular RecipientInfo for\ndecryption.\n\nThe FIPS modules in 4.0, 3.6, 3.5, and 3.4 are not affected by this issue, as\nCMS and S/MIME processing happens outside the OpenSSL FIPS module boundary.(CVE-2026-42768)",
"id": "OESA-2026-3002",
"modified": "2026-08-06T11:11:54Z",
"published": "2026-07-19T11:11:54Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-3002"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-42766"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-42767"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-42768"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
],
"summary": "edk2 security update",
"upstream": [
"CVE-2026-42766",
"CVE-2026-42767",
"CVE-2026-42768"
]
}
OESA-2026-3003 (CVE-2026-42766)
Vulnerability from osv_openeuler – Published: 2026-07-19 11:11 – Updated: 2026-08-06 11:11 – Source websiteEDK II is a modern, feature-rich, cross-platform firmware development environment for the UEFI and PI specifications.
Security Fix(es):
Issue summary: A specially crafted password-encrypted CMS message can trigger a NULL pointer dereference during CMS decryption.
Impact summary: This NULL pointer dereference leads to an application crash and a Denial of Service.
The CMS PasswordRecipientInfo.keyDerivationAlgorithm field is defined as OPTIONAL in the ASN.1 specification and may therefore be absent in specially crafted inputs. During the password-based CMS decryption the OpenSSL CMS implementation dereferences this field without first checking whether it was present.
An attacker who supplies such a CMS message to an application performing password-based CMS decryption can trigger an application crash, leading to a Denial of Service.
Applications that process password-encrypted CMS messages may be affected.
The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.(CVE-2026-42766)
Issue summary: An attacker-controlled CMP (Certificate Management Protocol) server could trigger a NULL pointer dereference in a CMP client application.
Impact summary: A NULL pointer dereference causes a crash of the application and a Denial of Service.
An attacker controlling a CMP server (or acting as a man-in-the-middle) could craft a CMP response containing a CRMF (Certificate Request Message Format) CertRepMessage with an EncryptedValue structure where the symmAlg field has an algorithm OID but no parameters field. When the OpenSSL CMP client processes this response, the NULL dereference occurs, causing a crash of the CMP client.
Applications that process untrusted CMP/CRMF messages may be affected.
The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.(CVE-2026-42767)
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'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.
- 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.
- 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.(CVE-2026-42768)
| URL | Type | |
|---|---|---|
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"edk2-debuginfo-202308-45.oe2403sp4.aarch64.rpm",
"edk2-debugsource-202308-45.oe2403sp4.aarch64.rpm",
"edk2-devel-202308-45.oe2403sp4.aarch64.rpm"
],
"noarch": [
"edk2-aarch64-202308-45.oe2403sp4.noarch.rpm",
"edk2-help-202308-45.oe2403sp4.noarch.rpm",
"edk2-ovmf-202308-45.oe2403sp4.noarch.rpm",
"python3-edk2-devel-202308-45.oe2403sp4.noarch.rpm"
],
"src": [
"edk2-202308-45.oe2403sp4.src.rpm"
],
"x86_64": [
"edk2-debuginfo-202308-45.oe2403sp4.x86_64.rpm",
"edk2-debugsource-202308-45.oe2403sp4.x86_64.rpm",
"edk2-devel-202308-45.oe2403sp4.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:24.03-LTS-SP4",
"name": "edk2",
"purl": "pkg:rpm/openEuler/edk2\u0026distro=openEuler-24.03-LTS-SP4"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "202308-45.oe2403sp4"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "Medium"
},
"details": "EDK II is a modern, feature-rich, cross-platform firmware development environment for the UEFI and PI specifications.\r\n\r\nSecurity Fix(es):\n\nIssue summary: A specially crafted password-encrypted CMS message\ncan trigger a NULL pointer dereference during CMS decryption.\n\nImpact summary: This NULL pointer dereference leads to an application crash\nand a Denial of Service.\n\nThe CMS PasswordRecipientInfo.keyDerivationAlgorithm field is defined as\nOPTIONAL in the ASN.1 specification and may therefore be absent in specially\ncrafted inputs. During the password-based CMS decryption the OpenSSL\nCMS implementation dereferences this field without first checking whether it\nwas present.\n\nAn attacker who supplies such a CMS message to an application performing\npassword-based CMS decryption can trigger an application crash, leading to\na Denial of Service.\n\nApplications that process password-encrypted CMS messages may be affected.\n\nThe FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this\nissue, as the affected code is outside the OpenSSL FIPS module boundary.(CVE-2026-42766)\n\nIssue summary: An attacker-controlled CMP (Certificate Management Protocol)\nserver could trigger a NULL pointer dereference in a CMP client application.\n\nImpact summary: A NULL pointer dereference causes a crash of the\napplication and a Denial of Service.\n\nAn attacker controlling a CMP server (or acting as a man-in-the-middle) could\ncraft a CMP response containing a CRMF (Certificate Request Message Format)\nCertRepMessage with an EncryptedValue structure where the symmAlg field\nhas an algorithm OID but no parameters field. When the OpenSSL CMP client\nprocesses this response, the NULL dereference occurs, causing a crash of\nthe CMP client.\n\nApplications that process untrusted CMP/CRMF messages may be affected.\n\nThe FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this\nissue, as the affected code is outside the OpenSSL FIPS module boundary.(CVE-2026-42767)\n\nIssue summary: The CMS_decrypt and PKCS7_decrypt functions are vulnerable to\nBleichenbacher-style attack when an attacker is able to provide the CMS or\nS/MIME messages and observe the error code and/or decryption output.\n\nImpact summary: The Bleichenbacher-style attack allows an attacker to use the\nvictim\u0026apos;s vulnerable application as a way to decrypt or sign messages with the\nvictim\u0026apos;s private RSA key.\n\nThe attack is possible in 2 variants.\n\n1. The decryption API (CMS_decrypt(), PKCS7_decrypt()) is used without\nproviding the recipient certificate. In this case OpenSSL iterates over every\nKeyTransRecipientInfo (KTRI) without stopping at the first success.\n\nAn attacker who authors a message with two KTRI entries \u2014 the first one\nwrapping a real CEK under the victim\u0026apos;s public key, the second with an\narbitrary probe ciphertext \u2014 obtains opportunity to iterate the 2nd KTRI to\nget a valid PKCS#1 v1.5 padding if the error code of the application is\navailable.\n\nThat is a Bleichenbacher oracle (Bleichenbacher, CRYPTO \u0026apos;98): an\nadaptive-chosen-ciphertext side channel from which the attacker decrypts any\nRSA ciphertext to the victim\u0026apos;s key or forges any PKCS#1 v1.5 signature under\nit.\n\n2. When the decryption API (CMS_decrypt(), PKCS7_decrypt()) is provided with\nthe recipient certificate, and the recipient is not found, a random\nkey is substituted.\n\nAn attacker who authors a message and is able to compare both error code and\nthe result of the decryption, can mount a Bleichenbacher oracle.\n\nWe are not aware of any applications that provide a remote attacker\nan opportunity to mount an attack described in these scenarios. We consider\nthe existence of such application very unlikely, and for this reason this\nCVE has been evaluated as Low severity.\n\nTo avoid these attacks, when RSA PKCS#1 v1.5 Key Transport is in use, the\ninvoked EVP_PKEY_decrypt() will use the implicit rejection mechanism described\nin draft-irtf-cfrg-rsa-guidance. In previous OpenSSL releases the implicit\nrejection was explicitly disabled.\n\nThe implicit rejection mechanism always returns a plaintext value,\nthe symmetric key. This result is deterministic for the ciphertext and the\nprivate key. The length of the decryption result can happen to match the\nlength of the key of the symmetric cipher that was used for the content\nencryption. When a certificate is not provided, the last RecipientInfo\nproducing a key that looks valid will be used. It may cause getting garbage\ncontent on decryption. As a proper way to deal with this a recipient\ncertificate has to be provided to identify the particular RecipientInfo for\ndecryption.\n\nThe FIPS modules in 4.0, 3.6, 3.5, and 3.4 are not affected by this issue, as\nCMS and S/MIME processing happens outside the OpenSSL FIPS module boundary.(CVE-2026-42768)",
"id": "OESA-2026-3003",
"modified": "2026-08-06T11:11:54Z",
"published": "2026-07-19T11:11:54Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-3003"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-42766"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-42767"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-42768"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
],
"summary": "edk2 security update",
"upstream": [
"CVE-2026-42766",
"CVE-2026-42767",
"CVE-2026-42768"
]
}
OESA-2026-3004 (CVE-2026-42766)
Vulnerability from osv_openeuler – Published: 2026-07-19 11:11 – Updated: 2026-08-06 11:11 – Source websiteEDK II is a modern, feature-rich, cross-platform firmware development environment for the UEFI and PI specifications.
Security Fix(es):
Issue summary: A specially crafted password-encrypted CMS message can trigger a NULL pointer dereference during CMS decryption.
Impact summary: This NULL pointer dereference leads to an application crash and a Denial of Service.
The CMS PasswordRecipientInfo.keyDerivationAlgorithm field is defined as OPTIONAL in the ASN.1 specification and may therefore be absent in specially crafted inputs. During the password-based CMS decryption the OpenSSL CMS implementation dereferences this field without first checking whether it was present.
An attacker who supplies such a CMS message to an application performing password-based CMS decryption can trigger an application crash, leading to a Denial of Service.
Applications that process password-encrypted CMS messages may be affected.
The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.(CVE-2026-42766)
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'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.
- 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.
- 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.(CVE-2026-42768)
| URL | Type | |
|---|---|---|
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"edk2-debuginfo-202002-38.oe2003sp4.aarch64.rpm",
"edk2-debugsource-202002-38.oe2003sp4.aarch64.rpm",
"edk2-devel-202002-38.oe2003sp4.aarch64.rpm"
],
"noarch": [
"edk2-aarch64-202002-38.oe2003sp4.noarch.rpm",
"edk2-help-202002-38.oe2003sp4.noarch.rpm",
"edk2-ovmf-202002-38.oe2003sp4.noarch.rpm",
"python3-edk2-devel-202002-38.oe2003sp4.noarch.rpm"
],
"src": [
"edk2-202002-38.oe2003sp4.src.rpm"
],
"x86_64": [
"edk2-debuginfo-202002-38.oe2003sp4.x86_64.rpm",
"edk2-debugsource-202002-38.oe2003sp4.x86_64.rpm",
"edk2-devel-202002-38.oe2003sp4.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:20.03-LTS-SP4",
"name": "edk2",
"purl": "pkg:rpm/openEuler/edk2\u0026distro=openEuler-20.03-LTS-SP4"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "202002-38.oe2003sp4"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "Medium"
},
"details": "EDK II is a modern, feature-rich, cross-platform firmware development environment for the UEFI and PI specifications.\r\n\r\nSecurity Fix(es):\n\nIssue summary: A specially crafted password-encrypted CMS message\ncan trigger a NULL pointer dereference during CMS decryption.\n\nImpact summary: This NULL pointer dereference leads to an application crash\nand a Denial of Service.\n\nThe CMS PasswordRecipientInfo.keyDerivationAlgorithm field is defined as\nOPTIONAL in the ASN.1 specification and may therefore be absent in specially\ncrafted inputs. During the password-based CMS decryption the OpenSSL\nCMS implementation dereferences this field without first checking whether it\nwas present.\n\nAn attacker who supplies such a CMS message to an application performing\npassword-based CMS decryption can trigger an application crash, leading to\na Denial of Service.\n\nApplications that process password-encrypted CMS messages may be affected.\n\nThe FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this\nissue, as the affected code is outside the OpenSSL FIPS module boundary.(CVE-2026-42766)\n\nIssue summary: The CMS_decrypt and PKCS7_decrypt functions are vulnerable to\nBleichenbacher-style attack when an attacker is able to provide the CMS or\nS/MIME messages and observe the error code and/or decryption output.\n\nImpact summary: The Bleichenbacher-style attack allows an attacker to use the\nvictim\u0026apos;s vulnerable application as a way to decrypt or sign messages with the\nvictim\u0026apos;s private RSA key.\n\nThe attack is possible in 2 variants.\n\n1. The decryption API (CMS_decrypt(), PKCS7_decrypt()) is used without\nproviding the recipient certificate. In this case OpenSSL iterates over every\nKeyTransRecipientInfo (KTRI) without stopping at the first success.\n\nAn attacker who authors a message with two KTRI entries \u2014 the first one\nwrapping a real CEK under the victim\u0026apos;s public key, the second with an\narbitrary probe ciphertext \u2014 obtains opportunity to iterate the 2nd KTRI to\nget a valid PKCS#1 v1.5 padding if the error code of the application is\navailable.\n\nThat is a Bleichenbacher oracle (Bleichenbacher, CRYPTO \u0026apos;98): an\nadaptive-chosen-ciphertext side channel from which the attacker decrypts any\nRSA ciphertext to the victim\u0026apos;s key or forges any PKCS#1 v1.5 signature under\nit.\n\n2. When the decryption API (CMS_decrypt(), PKCS7_decrypt()) is provided with\nthe recipient certificate, and the recipient is not found, a random\nkey is substituted.\n\nAn attacker who authors a message and is able to compare both error code and\nthe result of the decryption, can mount a Bleichenbacher oracle.\n\nWe are not aware of any applications that provide a remote attacker\nan opportunity to mount an attack described in these scenarios. We consider\nthe existence of such application very unlikely, and for this reason this\nCVE has been evaluated as Low severity.\n\nTo avoid these attacks, when RSA PKCS#1 v1.5 Key Transport is in use, the\ninvoked EVP_PKEY_decrypt() will use the implicit rejection mechanism described\nin draft-irtf-cfrg-rsa-guidance. In previous OpenSSL releases the implicit\nrejection was explicitly disabled.\n\nThe implicit rejection mechanism always returns a plaintext value,\nthe symmetric key. This result is deterministic for the ciphertext and the\nprivate key. The length of the decryption result can happen to match the\nlength of the key of the symmetric cipher that was used for the content\nencryption. When a certificate is not provided, the last RecipientInfo\nproducing a key that looks valid will be used. It may cause getting garbage\ncontent on decryption. As a proper way to deal with this a recipient\ncertificate has to be provided to identify the particular RecipientInfo for\ndecryption.\n\nThe FIPS modules in 4.0, 3.6, 3.5, and 3.4 are not affected by this issue, as\nCMS and S/MIME processing happens outside the OpenSSL FIPS module boundary.(CVE-2026-42768)",
"id": "OESA-2026-3004",
"modified": "2026-08-06T11:11:54Z",
"published": "2026-07-19T11:11:54Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-3004"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-42766"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-42768"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
],
"summary": "edk2 security update",
"upstream": [
"CVE-2026-42766",
"CVE-2026-42768"
]
}
OESA-2026-3005 (CVE-2026-42766)
Vulnerability from osv_openeuler – Published: 2026-07-19 11:11 – Updated: 2026-08-06 11:11 – Source websiteEDK II is a modern, feature-rich, cross-platform firmware development environment for the UEFI and PI specifications.
Security Fix(es):
Issue summary: A specially crafted password-encrypted CMS message can trigger a NULL pointer dereference during CMS decryption.
Impact summary: This NULL pointer dereference leads to an application crash and a Denial of Service.
The CMS PasswordRecipientInfo.keyDerivationAlgorithm field is defined as OPTIONAL in the ASN.1 specification and may therefore be absent in specially crafted inputs. During the password-based CMS decryption the OpenSSL CMS implementation dereferences this field without first checking whether it was present.
An attacker who supplies such a CMS message to an application performing password-based CMS decryption can trigger an application crash, leading to a Denial of Service.
Applications that process password-encrypted CMS messages may be affected.
The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.(CVE-2026-42766)
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'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.
- 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.
- 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.(CVE-2026-42768)
| URL | Type | |
|---|---|---|
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"edk2-debuginfo-202011-36.oe2203sp4.aarch64.rpm",
"edk2-debugsource-202011-36.oe2203sp4.aarch64.rpm",
"edk2-devel-202011-36.oe2203sp4.aarch64.rpm"
],
"noarch": [
"edk2-aarch64-202011-36.oe2203sp4.noarch.rpm",
"edk2-help-202011-36.oe2203sp4.noarch.rpm",
"edk2-ovmf-202011-36.oe2203sp4.noarch.rpm",
"python3-edk2-devel-202011-36.oe2203sp4.noarch.rpm"
],
"src": [
"edk2-202011-36.oe2203sp4.src.rpm"
],
"x86_64": [
"edk2-debuginfo-202011-36.oe2203sp4.x86_64.rpm",
"edk2-debugsource-202011-36.oe2203sp4.x86_64.rpm",
"edk2-devel-202011-36.oe2203sp4.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:22.03-LTS-SP4",
"name": "edk2",
"purl": "pkg:rpm/openEuler/edk2\u0026distro=openEuler-22.03-LTS-SP4"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "202011-36.oe2203sp4"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "Medium"
},
"details": "EDK II is a modern, feature-rich, cross-platform firmware development environment for the UEFI and PI specifications.\r\n\r\nSecurity Fix(es):\n\nIssue summary: A specially crafted password-encrypted CMS message\ncan trigger a NULL pointer dereference during CMS decryption.\n\nImpact summary: This NULL pointer dereference leads to an application crash\nand a Denial of Service.\n\nThe CMS PasswordRecipientInfo.keyDerivationAlgorithm field is defined as\nOPTIONAL in the ASN.1 specification and may therefore be absent in specially\ncrafted inputs. During the password-based CMS decryption the OpenSSL\nCMS implementation dereferences this field without first checking whether it\nwas present.\n\nAn attacker who supplies such a CMS message to an application performing\npassword-based CMS decryption can trigger an application crash, leading to\na Denial of Service.\n\nApplications that process password-encrypted CMS messages may be affected.\n\nThe FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this\nissue, as the affected code is outside the OpenSSL FIPS module boundary.(CVE-2026-42766)\n\nIssue summary: The CMS_decrypt and PKCS7_decrypt functions are vulnerable to\nBleichenbacher-style attack when an attacker is able to provide the CMS or\nS/MIME messages and observe the error code and/or decryption output.\n\nImpact summary: The Bleichenbacher-style attack allows an attacker to use the\nvictim\u0026apos;s vulnerable application as a way to decrypt or sign messages with the\nvictim\u0026apos;s private RSA key.\n\nThe attack is possible in 2 variants.\n\n1. The decryption API (CMS_decrypt(), PKCS7_decrypt()) is used without\nproviding the recipient certificate. In this case OpenSSL iterates over every\nKeyTransRecipientInfo (KTRI) without stopping at the first success.\n\nAn attacker who authors a message with two KTRI entries \u2014 the first one\nwrapping a real CEK under the victim\u0026apos;s public key, the second with an\narbitrary probe ciphertext \u2014 obtains opportunity to iterate the 2nd KTRI to\nget a valid PKCS#1 v1.5 padding if the error code of the application is\navailable.\n\nThat is a Bleichenbacher oracle (Bleichenbacher, CRYPTO \u0026apos;98): an\nadaptive-chosen-ciphertext side channel from which the attacker decrypts any\nRSA ciphertext to the victim\u0026apos;s key or forges any PKCS#1 v1.5 signature under\nit.\n\n2. When the decryption API (CMS_decrypt(), PKCS7_decrypt()) is provided with\nthe recipient certificate, and the recipient is not found, a random\nkey is substituted.\n\nAn attacker who authors a message and is able to compare both error code and\nthe result of the decryption, can mount a Bleichenbacher oracle.\n\nWe are not aware of any applications that provide a remote attacker\nan opportunity to mount an attack described in these scenarios. We consider\nthe existence of such application very unlikely, and for this reason this\nCVE has been evaluated as Low severity.\n\nTo avoid these attacks, when RSA PKCS#1 v1.5 Key Transport is in use, the\ninvoked EVP_PKEY_decrypt() will use the implicit rejection mechanism described\nin draft-irtf-cfrg-rsa-guidance. In previous OpenSSL releases the implicit\nrejection was explicitly disabled.\n\nThe implicit rejection mechanism always returns a plaintext value,\nthe symmetric key. This result is deterministic for the ciphertext and the\nprivate key. The length of the decryption result can happen to match the\nlength of the key of the symmetric cipher that was used for the content\nencryption. When a certificate is not provided, the last RecipientInfo\nproducing a key that looks valid will be used. It may cause getting garbage\ncontent on decryption. As a proper way to deal with this a recipient\ncertificate has to be provided to identify the particular RecipientInfo for\ndecryption.\n\nThe FIPS modules in 4.0, 3.6, 3.5, and 3.4 are not affected by this issue, as\nCMS and S/MIME processing happens outside the OpenSSL FIPS module boundary.(CVE-2026-42768)",
"id": "OESA-2026-3005",
"modified": "2026-08-06T11:11:54Z",
"published": "2026-07-19T11:11:54Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-3005"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-42766"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-42768"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
],
"summary": "edk2 security update",
"upstream": [
"CVE-2026-42766",
"CVE-2026-42768"
]
}
OESA-2026-3006 (CVE-2026-42766)
Vulnerability from osv_openeuler – Published: 2026-07-19 11:11 – Updated: 2026-08-06 11:11 – Source websiteEDK II is a modern, feature-rich, cross-platform firmware development environment for the UEFI and PI specifications.
Security Fix(es):
Issue summary: A specially crafted password-encrypted CMS message can trigger a NULL pointer dereference during CMS decryption.
Impact summary: This NULL pointer dereference leads to an application crash and a Denial of Service.
The CMS PasswordRecipientInfo.keyDerivationAlgorithm field is defined as OPTIONAL in the ASN.1 specification and may therefore be absent in specially crafted inputs. During the password-based CMS decryption the OpenSSL CMS implementation dereferences this field without first checking whether it was present.
An attacker who supplies such a CMS message to an application performing password-based CMS decryption can trigger an application crash, leading to a Denial of Service.
Applications that process password-encrypted CMS messages may be affected.
The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.(CVE-2026-42766)
Issue summary: An attacker-controlled CMP (Certificate Management Protocol) server could trigger a NULL pointer dereference in a CMP client application.
Impact summary: A NULL pointer dereference causes a crash of the application and a Denial of Service.
An attacker controlling a CMP server (or acting as a man-in-the-middle) could craft a CMP response containing a CRMF (Certificate Request Message Format) CertRepMessage with an EncryptedValue structure where the symmAlg field has an algorithm OID but no parameters field. When the OpenSSL CMP client processes this response, the NULL dereference occurs, causing a crash of the CMP client.
Applications that process untrusted CMP/CRMF messages may be affected.
The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.(CVE-2026-42767)
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'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.
- 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.
- 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.(CVE-2026-42768)
Issue summary: When EVP_PKEY_derive_set_peer() is called with a DHX (X9.42) peer key, the peer key is not properly checked for the subgroup membership.
Impact summary: A malicious peer which presents an X9.42 key carrying the victim's p and g parameters, a forged q = r (a small prime factor of the cofactor (p−1)/q_local), and a public value Y of order r can recover the victim's private key after a small number of key exchange attempts.
When EVP_PKEY_derive_set_peer() is called with a DHX (X9.42) peer key, the subgroup membership check Y^q ≡ 1 (mod p) is performed using the peer's own q parameter, not the local key's q. The peer's domain parameters are then matched against the domain parameters of the private key, but the value of q is not compared.
A malicious peer who presents an X9.42 key carrying the victim's p, g, a forged q = r (a small prime factor of the cofactor), and a public value Y of order r passes all checks. The shared secret then takes only r distinct values, leaking priv mod r. Repeating for each small-prime factor of the cofactor and combining via CRT recovers the full private key (Lim–Lee / small-subgroup-confinement attack).
The realistic attack surface is narrow: principally CMP deployments with long-lived RA/CA DHX keys and bespoke enterprise or government applications using X9.42 DHX static keys with interactive protocols and therefore this issue was assigned Low severity.
The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are affected by this issue.(CVE-2026-42770)
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"edk2-debuginfo-202308-41.oe2403sp1.aarch64.rpm",
"edk2-debugsource-202308-41.oe2403sp1.aarch64.rpm",
"edk2-devel-202308-41.oe2403sp1.aarch64.rpm"
],
"noarch": [
"edk2-aarch64-202308-41.oe2403sp1.noarch.rpm",
"edk2-help-202308-41.oe2403sp1.noarch.rpm",
"edk2-ovmf-202308-41.oe2403sp1.noarch.rpm",
"python3-edk2-devel-202308-41.oe2403sp1.noarch.rpm"
],
"src": [
"edk2-202308-41.oe2403sp1.src.rpm"
],
"x86_64": [
"edk2-debuginfo-202308-41.oe2403sp1.x86_64.rpm",
"edk2-debugsource-202308-41.oe2403sp1.x86_64.rpm",
"edk2-devel-202308-41.oe2403sp1.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:24.03-LTS-SP1",
"name": "edk2",
"purl": "pkg:rpm/openEuler/edk2\u0026distro=openEuler-24.03-LTS-SP1"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "202308-41.oe2403sp1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "Medium"
},
"details": "EDK II is a modern, feature-rich, cross-platform firmware development environment for the UEFI and PI specifications.\r\n\r\nSecurity Fix(es):\n\nIssue summary: A specially crafted password-encrypted CMS message\ncan trigger a NULL pointer dereference during CMS decryption.\n\nImpact summary: This NULL pointer dereference leads to an application crash\nand a Denial of Service.\n\nThe CMS PasswordRecipientInfo.keyDerivationAlgorithm field is defined as\nOPTIONAL in the ASN.1 specification and may therefore be absent in specially\ncrafted inputs. During the password-based CMS decryption the OpenSSL\nCMS implementation dereferences this field without first checking whether it\nwas present.\n\nAn attacker who supplies such a CMS message to an application performing\npassword-based CMS decryption can trigger an application crash, leading to\na Denial of Service.\n\nApplications that process password-encrypted CMS messages may be affected.\n\nThe FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this\nissue, as the affected code is outside the OpenSSL FIPS module boundary.(CVE-2026-42766)\n\nIssue summary: An attacker-controlled CMP (Certificate Management Protocol)\nserver could trigger a NULL pointer dereference in a CMP client application.\n\nImpact summary: A NULL pointer dereference causes a crash of the\napplication and a Denial of Service.\n\nAn attacker controlling a CMP server (or acting as a man-in-the-middle) could\ncraft a CMP response containing a CRMF (Certificate Request Message Format)\nCertRepMessage with an EncryptedValue structure where the symmAlg field\nhas an algorithm OID but no parameters field. When the OpenSSL CMP client\nprocesses this response, the NULL dereference occurs, causing a crash of\nthe CMP client.\n\nApplications that process untrusted CMP/CRMF messages may be affected.\n\nThe FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this\nissue, as the affected code is outside the OpenSSL FIPS module boundary.(CVE-2026-42767)\n\nIssue summary: The CMS_decrypt and PKCS7_decrypt functions are vulnerable to\nBleichenbacher-style attack when an attacker is able to provide the CMS or\nS/MIME messages and observe the error code and/or decryption output.\n\nImpact summary: The Bleichenbacher-style attack allows an attacker to use the\nvictim\u0026apos;s vulnerable application as a way to decrypt or sign messages with the\nvictim\u0026apos;s private RSA key.\n\nThe attack is possible in 2 variants.\n\n1. The decryption API (CMS_decrypt(), PKCS7_decrypt()) is used without\nproviding the recipient certificate. In this case OpenSSL iterates over every\nKeyTransRecipientInfo (KTRI) without stopping at the first success.\n\nAn attacker who authors a message with two KTRI entries \u2014 the first one\nwrapping a real CEK under the victim\u0026apos;s public key, the second with an\narbitrary probe ciphertext \u2014 obtains opportunity to iterate the 2nd KTRI to\nget a valid PKCS#1 v1.5 padding if the error code of the application is\navailable.\n\nThat is a Bleichenbacher oracle (Bleichenbacher, CRYPTO \u0026apos;98): an\nadaptive-chosen-ciphertext side channel from which the attacker decrypts any\nRSA ciphertext to the victim\u0026apos;s key or forges any PKCS#1 v1.5 signature under\nit.\n\n2. When the decryption API (CMS_decrypt(), PKCS7_decrypt()) is provided with\nthe recipient certificate, and the recipient is not found, a random\nkey is substituted.\n\nAn attacker who authors a message and is able to compare both error code and\nthe result of the decryption, can mount a Bleichenbacher oracle.\n\nWe are not aware of any applications that provide a remote attacker\nan opportunity to mount an attack described in these scenarios. We consider\nthe existence of such application very unlikely, and for this reason this\nCVE has been evaluated as Low severity.\n\nTo avoid these attacks, when RSA PKCS#1 v1.5 Key Transport is in use, the\ninvoked EVP_PKEY_decrypt() will use the implicit rejection mechanism described\nin draft-irtf-cfrg-rsa-guidance. In previous OpenSSL releases the implicit\nrejection was explicitly disabled.\n\nThe implicit rejection mechanism always returns a plaintext value,\nthe symmetric key. This result is deterministic for the ciphertext and the\nprivate key. The length of the decryption result can happen to match the\nlength of the key of the symmetric cipher that was used for the content\nencryption. When a certificate is not provided, the last RecipientInfo\nproducing a key that looks valid will be used. It may cause getting garbage\ncontent on decryption. As a proper way to deal with this a recipient\ncertificate has to be provided to identify the particular RecipientInfo for\ndecryption.\n\nThe FIPS modules in 4.0, 3.6, 3.5, and 3.4 are not affected by this issue, as\nCMS and S/MIME processing happens outside the OpenSSL FIPS module boundary.(CVE-2026-42768)\n\nIssue summary: When EVP_PKEY_derive_set_peer() is called with a DHX (X9.42)\npeer key, the peer key is not properly checked for the subgroup membership.\n\nImpact summary: A malicious peer which presents an X9.42 key carrying the\nvictim\u0026apos;s p and g parameters, a forged q = r (a small prime factor of the\ncofactor (p\u22121)/q_local), and a public value Y of order r can recover the\nvictim\u0026apos;s private key after a small number of key exchange attempts.\n\nWhen EVP_PKEY_derive_set_peer() is called with a DHX (X9.42) peer key, the\nsubgroup membership check Y^q \u2261 1 (mod p) is performed using the peer\u0026apos;s\nown q parameter, not the local key\u0026apos;s q. The peer\u0026apos;s domain parameters are\nthen matched against the domain parameters of the private key, but the value\nof q is not compared.\n\nA malicious peer who presents an X9.42 key carrying the victim\u0026apos;s p, g,\na forged q = r (a small prime factor of the cofactor), and a public\nvalue Y of order r passes all checks. The shared secret then takes only\nr distinct values, leaking priv mod r. Repeating for each small-prime\nfactor of the cofactor and combining via CRT recovers the full private\nkey (Lim\u2013Lee / small-subgroup-confinement attack).\n\nThe realistic attack surface is narrow: principally CMP deployments with\nlong-lived RA/CA DHX keys and bespoke enterprise or government applications\nusing X9.42 DHX static keys with interactive protocols and therefore this\nissue was assigned Low severity.\n\nThe FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are affected by this\nissue.(CVE-2026-42770)",
"id": "OESA-2026-3006",
"modified": "2026-08-06T11:11:54Z",
"published": "2026-07-19T11:11:54Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-3006"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-42766"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-42767"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-42768"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-42770"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
],
"summary": "edk2 security update",
"upstream": [
"CVE-2026-42766",
"CVE-2026-42767",
"CVE-2026-42768",
"CVE-2026-42770"
]
}
RLSA-2026:25237 (CVE-2026-34180)
Vulnerability from osv_rocky – Published: 2026-06-13 00:05 – Updated: 2026-06-27 00:06 – Source websiteOpenSSL is a toolkit that implements the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols, as well as a full-strength general-purpose cryptography library.
Security Fix(es):
-
openssl: OpenSSL: Heap buffer overflow due to signed integer overflow in Unicode output sizing (CVE-2026-7383)
-
openssl: OpenSSL: Denial of Service due to heap out-of-bounds read in CMS password-based decryption (CVE-2026-9076)
-
openssl: OpenSSL: Heap buffer over-read in ASN.1 decoding can lead to denial of service or information disclosure. (CVE-2026-34180)
-
openssl: PKCS#12 Files with PBMAC1 Are Accepted with Short HMAC Keys (CVE-2026-34181)
-
openssl: CMS AuthEnvelopedData Processing May Accept Forged Messages (CVE-2026-34182)
-
openssl: Unbounded Memory Growth in the QUIC PATH_CHALLENGE Handler (CVE-2026-34183)
-
openssl: NULL pointer dereference in QUIC server initial packet handling (CVE-2026-42764)
-
openssl: Possible NULL Dereference in Password-Based CMS Decryption (CVE-2026-42766)
-
openssl: NULL Pointer Dereference in CRMF EncryptedValue Decryption (CVE-2026-42767)
-
openssl: Multi-RecipientInfo Bleichenbacher Oracle in CMS_decrypt() and PKCS7_decrypt() (CVE-2026-42768)
-
openssl: Trust-Anchor Substitution via cert/issuer Typo in CMP rootCaKeyUpdate (CVE-2026-42769)
-
openssl: FFC-DH Peer Validation Uses Attacker-Supplied q (CVE-2026-42770)
-
openssl: AES-OCB IV Ignored on EVP_Cipher() Path (CVE-2026-45445)
-
openssl: Incorrect Tag Processing for Empty Messages in AES-GCM-SIV and AES-SIV modes (CVE-2026-45446)
-
openssl: Heap Use-After-Free in OpenSSL PKCS7_verify() (CVE-2026-45447)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
| URL | Type | ||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||
{
"affected": [
{
"package": {
"ecosystem": "Rocky Linux:10",
"name": "openssl-libs",
"purl": "pkg:rpm/rocky-linux/openssl-libs?distro=rocky-linux-10\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el10_2"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:10",
"name": "openssl-debuginfo",
"purl": "pkg:rpm/rocky-linux/openssl-debuginfo?distro=rocky-linux-10\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el10_2"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:10",
"name": "openssl-debugsource",
"purl": "pkg:rpm/rocky-linux/openssl-debugsource?distro=rocky-linux-10\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el10_2"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:10",
"name": "openssl-libs-debuginfo",
"purl": "pkg:rpm/rocky-linux/openssl-libs-debuginfo?distro=rocky-linux-10\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el10_2"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:10",
"name": "openssl",
"purl": "pkg:rpm/rocky-linux/openssl?distro=rocky-linux-10\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el10_2"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:10",
"name": "openssl-perl",
"purl": "pkg:rpm/rocky-linux/openssl-perl?distro=rocky-linux-10\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "AppStream"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el10_2"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:10",
"name": "openssl-devel",
"purl": "pkg:rpm/rocky-linux/openssl-devel?distro=rocky-linux-10\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "AppStream"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el10_2"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:10",
"name": "openssl-debuginfo",
"purl": "pkg:rpm/rocky-linux/openssl-debuginfo?distro=rocky-linux-10\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el10_2"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:10",
"name": "openssl-libs-debuginfo",
"purl": "pkg:rpm/rocky-linux/openssl-libs-debuginfo?distro=rocky-linux-10\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el10_2"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:10",
"name": "openssl-devel",
"purl": "pkg:rpm/rocky-linux/openssl-devel?distro=rocky-linux-10\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "AppStream"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el10_2"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:10",
"name": "openssl-libs",
"purl": "pkg:rpm/rocky-linux/openssl-libs?distro=rocky-linux-10\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el10_2"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:10",
"name": "openssl-perl",
"purl": "pkg:rpm/rocky-linux/openssl-perl?distro=rocky-linux-10\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "AppStream"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el10_2"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:10",
"name": "openssl-debugsource",
"purl": "pkg:rpm/rocky-linux/openssl-debugsource?distro=rocky-linux-10\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el10_2"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:10",
"name": "openssl",
"purl": "pkg:rpm/rocky-linux/openssl?distro=rocky-linux-10\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el10_2"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:10",
"name": "openssl-debugsource",
"purl": "pkg:rpm/rocky-linux/openssl-debugsource?distro=rocky-linux-10\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el10_2"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:10",
"name": "openssl-debuginfo",
"purl": "pkg:rpm/rocky-linux/openssl-debuginfo?distro=rocky-linux-10\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el10_2"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:10",
"name": "openssl-perl",
"purl": "pkg:rpm/rocky-linux/openssl-perl?distro=rocky-linux-10\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "AppStream"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el10_2"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:10",
"name": "openssl-libs-debuginfo",
"purl": "pkg:rpm/rocky-linux/openssl-libs-debuginfo?distro=rocky-linux-10\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el10_2"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:10",
"name": "openssl",
"purl": "pkg:rpm/rocky-linux/openssl?distro=rocky-linux-10\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el10_2"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:10",
"name": "openssl-devel",
"purl": "pkg:rpm/rocky-linux/openssl-devel?distro=rocky-linux-10\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "AppStream"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el10_2"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:10",
"name": "openssl-libs",
"purl": "pkg:rpm/rocky-linux/openssl-libs?distro=rocky-linux-10\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el10_2"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:10",
"name": "openssl-debuginfo",
"purl": "pkg:rpm/rocky-linux/openssl-debuginfo?distro=rocky-linux-10\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el10_2"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:10",
"name": "openssl-perl",
"purl": "pkg:rpm/rocky-linux/openssl-perl?distro=rocky-linux-10\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "AppStream"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el10_2"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:10",
"name": "openssl",
"purl": "pkg:rpm/rocky-linux/openssl?distro=rocky-linux-10\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el10_2"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:10",
"name": "openssl-libs-debuginfo",
"purl": "pkg:rpm/rocky-linux/openssl-libs-debuginfo?distro=rocky-linux-10\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el10_2"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:10",
"name": "openssl-devel",
"purl": "pkg:rpm/rocky-linux/openssl-devel?distro=rocky-linux-10\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "AppStream"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el10_2"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:10",
"name": "openssl-debugsource",
"purl": "pkg:rpm/rocky-linux/openssl-debugsource?distro=rocky-linux-10\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el10_2"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:10",
"name": "openssl-libs",
"purl": "pkg:rpm/rocky-linux/openssl-libs?distro=rocky-linux-10\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el10_2"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"credits": [
{
"name": "Rocky Enterprise Software Foundation"
},
{
"name": "Red Hat"
}
],
"database_specific": {
"license": "CC-BY-4.0",
"license_url": "https://creativecommons.org/licenses/by/4.0/",
"source_advisory": "RHSA-2026:25237"
},
"details": "OpenSSL is a toolkit that implements the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols, as well as a full-strength general-purpose cryptography library.\n\nSecurity Fix(es):\n\n* openssl: OpenSSL: Heap buffer overflow due to signed integer overflow in Unicode output sizing (CVE-2026-7383)\n\n* openssl: OpenSSL: Denial of Service due to heap out-of-bounds read in CMS password-based decryption (CVE-2026-9076)\n\n* openssl: OpenSSL: Heap buffer over-read in ASN.1 decoding can lead to denial of service or information disclosure. (CVE-2026-34180)\n\n* openssl: PKCS#12 Files with PBMAC1 Are Accepted with Short HMAC Keys (CVE-2026-34181)\n\n* openssl: CMS AuthEnvelopedData Processing May Accept Forged Messages (CVE-2026-34182)\n\n* openssl: Unbounded Memory Growth in the QUIC PATH_CHALLENGE Handler (CVE-2026-34183)\n\n* openssl: NULL pointer dereference in QUIC server initial packet handling (CVE-2026-42764)\n\n* openssl: Possible NULL Dereference in Password-Based CMS Decryption (CVE-2026-42766)\n\n* openssl: NULL Pointer Dereference in CRMF EncryptedValue Decryption (CVE-2026-42767)\n\n* openssl: Multi-RecipientInfo Bleichenbacher Oracle in CMS_decrypt() and PKCS7_decrypt() (CVE-2026-42768)\n\n* openssl: Trust-Anchor Substitution via cert/issuer Typo in CMP rootCaKeyUpdate (CVE-2026-42769)\n\n* openssl: FFC-DH Peer Validation Uses Attacker-Supplied q (CVE-2026-42770)\n\n* openssl: AES-OCB IV Ignored on EVP_Cipher() Path (CVE-2026-45445)\n\n* openssl: Incorrect Tag Processing for Empty Messages in AES-GCM-SIV and AES-SIV modes (CVE-2026-45446)\n\n* openssl: Heap Use-After-Free in OpenSSL PKCS7_verify() (CVE-2026-45447)\n\nFor more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.",
"id": "RLSA-2026:25237",
"modified": "2026-06-27T00:06:22.555811Z",
"published": "2026-06-13T00:05:06.020189Z",
"references": [
{
"type": "ADVISORY",
"url": "https://errata.rockylinux.org/RLSA-2026:25237"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2481897"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2481890"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2481892"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2481880"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2481882"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2481891"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2481881"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2481879"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2481884"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2481894"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2481885"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2481898"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2481896"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2481893"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2481887"
},
{
"type": "ADVISORY",
"url": "https://access.redhat.com/errata/RHSA-2026:25237"
}
],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
"type": "CVSS_V3"
}
],
"summary": "Important: openssl security update",
"upstream": [
"CVE-2026-34180",
"CVE-2026-34181",
"CVE-2026-34182",
"CVE-2026-34183",
"CVE-2026-42764",
"CVE-2026-42766",
"CVE-2026-42767",
"CVE-2026-42768",
"CVE-2026-42769",
"CVE-2026-42770",
"CVE-2026-45445",
"CVE-2026-45446",
"CVE-2026-45447",
"CVE-2026-7383",
"CVE-2026-9076"
]
}
RLSA-2026:25239 (CVE-2026-34180)
Vulnerability from osv_rocky – Published: 2026-06-13 00:03 – Updated: 2026-06-27 00:06 – Source websiteOpenSSL is a toolkit that implements the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols, as well as a full-strength general-purpose cryptography library.
Security Fix(es):
-
openssl: OpenSSL: Heap buffer overflow due to signed integer overflow in Unicode output sizing (CVE-2026-7383)
-
openssl: OpenSSL: Denial of Service due to heap out-of-bounds read in CMS password-based decryption (CVE-2026-9076)
-
openssl: OpenSSL: Heap buffer over-read in ASN.1 decoding can lead to denial of service or information disclosure. (CVE-2026-34180)
-
openssl: PKCS#12 Files with PBMAC1 Are Accepted with Short HMAC Keys (CVE-2026-34181)
-
openssl: CMS AuthEnvelopedData Processing May Accept Forged Messages (CVE-2026-34182)
-
openssl: Unbounded Memory Growth in the QUIC PATH_CHALLENGE Handler (CVE-2026-34183)
-
openssl: NULL pointer dereference in QUIC server initial packet handling (CVE-2026-42764)
-
openssl: Possible NULL Dereference in Password-Based CMS Decryption (CVE-2026-42766)
-
openssl: NULL Pointer Dereference in CRMF EncryptedValue Decryption (CVE-2026-42767)
-
openssl: Multi-RecipientInfo Bleichenbacher Oracle in CMS_decrypt() and PKCS7_decrypt() (CVE-2026-42768)
-
openssl: Trust-Anchor Substitution via cert/issuer Typo in CMP rootCaKeyUpdate (CVE-2026-42769)
-
openssl: FFC-DH Peer Validation Uses Attacker-Supplied q (CVE-2026-42770)
-
openssl: AES-OCB IV Ignored on EVP_Cipher() Path (CVE-2026-45445)
-
openssl: Incorrect Tag Processing for Empty Messages in AES-GCM-SIV and AES-SIV modes (CVE-2026-45446)
-
openssl: Heap Use-After-Free in OpenSSL PKCS7_verify() (CVE-2026-45447)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
| URL | Type | ||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||
{
"affected": [
{
"package": {
"ecosystem": "Rocky Linux:9",
"name": "openssl",
"purl": "pkg:rpm/rocky-linux/openssl?distro=rocky-linux-9\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el9_8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:9",
"name": "openssl-debuginfo",
"purl": "pkg:rpm/rocky-linux/openssl-debuginfo?distro=rocky-linux-9\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el9_8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:9",
"name": "openssl-debugsource",
"purl": "pkg:rpm/rocky-linux/openssl-debugsource?distro=rocky-linux-9\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el9_8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:9",
"name": "openssl-devel",
"purl": "pkg:rpm/rocky-linux/openssl-devel?distro=rocky-linux-9\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "AppStream"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el9_8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:9",
"name": "openssl-libs",
"purl": "pkg:rpm/rocky-linux/openssl-libs?distro=rocky-linux-9\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el9_8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:9",
"name": "openssl-libs-debuginfo",
"purl": "pkg:rpm/rocky-linux/openssl-libs-debuginfo?distro=rocky-linux-9\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el9_8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:9",
"name": "openssl-perl",
"purl": "pkg:rpm/rocky-linux/openssl-perl?distro=rocky-linux-9\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "AppStream"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el9_8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:9",
"name": "openssl",
"purl": "pkg:rpm/rocky-linux/openssl?distro=rocky-linux-9\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el9_8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:9",
"name": "openssl-debuginfo",
"purl": "pkg:rpm/rocky-linux/openssl-debuginfo?distro=rocky-linux-9\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el9_8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:9",
"name": "openssl-debugsource",
"purl": "pkg:rpm/rocky-linux/openssl-debugsource?distro=rocky-linux-9\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el9_8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:9",
"name": "openssl-devel",
"purl": "pkg:rpm/rocky-linux/openssl-devel?distro=rocky-linux-9\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "AppStream"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el9_8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:9",
"name": "openssl-libs",
"purl": "pkg:rpm/rocky-linux/openssl-libs?distro=rocky-linux-9\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el9_8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:9",
"name": "openssl-libs-debuginfo",
"purl": "pkg:rpm/rocky-linux/openssl-libs-debuginfo?distro=rocky-linux-9\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el9_8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:9",
"name": "openssl-perl",
"purl": "pkg:rpm/rocky-linux/openssl-perl?distro=rocky-linux-9\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "AppStream"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el9_8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:9",
"name": "openssl",
"purl": "pkg:rpm/rocky-linux/openssl?distro=rocky-linux-9\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el9_8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:9",
"name": "openssl-debuginfo",
"purl": "pkg:rpm/rocky-linux/openssl-debuginfo?distro=rocky-linux-9\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el9_8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:9",
"name": "openssl-debugsource",
"purl": "pkg:rpm/rocky-linux/openssl-debugsource?distro=rocky-linux-9\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el9_8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:9",
"name": "openssl-devel",
"purl": "pkg:rpm/rocky-linux/openssl-devel?distro=rocky-linux-9\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "AppStream"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el9_8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:9",
"name": "openssl-libs",
"purl": "pkg:rpm/rocky-linux/openssl-libs?distro=rocky-linux-9\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el9_8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:9",
"name": "openssl-libs-debuginfo",
"purl": "pkg:rpm/rocky-linux/openssl-libs-debuginfo?distro=rocky-linux-9\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el9_8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:9",
"name": "openssl-perl",
"purl": "pkg:rpm/rocky-linux/openssl-perl?distro=rocky-linux-9\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "AppStream"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el9_8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:9",
"name": "openssl",
"purl": "pkg:rpm/rocky-linux/openssl?distro=rocky-linux-9\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el9_8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:9",
"name": "openssl-debuginfo",
"purl": "pkg:rpm/rocky-linux/openssl-debuginfo?distro=rocky-linux-9\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el9_8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:9",
"name": "openssl-debugsource",
"purl": "pkg:rpm/rocky-linux/openssl-debugsource?distro=rocky-linux-9\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el9_8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:9",
"name": "openssl-devel",
"purl": "pkg:rpm/rocky-linux/openssl-devel?distro=rocky-linux-9\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "AppStream"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el9_8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:9",
"name": "openssl-libs",
"purl": "pkg:rpm/rocky-linux/openssl-libs?distro=rocky-linux-9\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el9_8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:9",
"name": "openssl-libs-debuginfo",
"purl": "pkg:rpm/rocky-linux/openssl-libs-debuginfo?distro=rocky-linux-9\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el9_8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:9",
"name": "openssl-perl",
"purl": "pkg:rpm/rocky-linux/openssl-perl?distro=rocky-linux-9\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "AppStream"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el9_8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:9",
"name": "openssl-debuginfo",
"purl": "pkg:rpm/rocky-linux/openssl-debuginfo?distro=rocky-linux-9\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el9_8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:9",
"name": "openssl-debugsource",
"purl": "pkg:rpm/rocky-linux/openssl-debugsource?distro=rocky-linux-9\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el9_8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:9",
"name": "openssl-devel",
"purl": "pkg:rpm/rocky-linux/openssl-devel?distro=rocky-linux-9\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "AppStream"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el9_8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:9",
"name": "openssl-libs",
"purl": "pkg:rpm/rocky-linux/openssl-libs?distro=rocky-linux-9\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el9_8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Rocky Linux:9",
"name": "openssl-libs-debuginfo",
"purl": "pkg:rpm/rocky-linux/openssl-libs-debuginfo?distro=rocky-linux-9\u0026epoch=1"
},
"ranges": [
{
"database_specific": {
"yum_repository": "BaseOS"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1:3.5.5-4.el9_8"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"credits": [
{
"name": "Rocky Enterprise Software Foundation"
},
{
"name": "Red Hat"
}
],
"database_specific": {
"license": "CC-BY-4.0",
"license_url": "https://creativecommons.org/licenses/by/4.0/",
"source_advisory": "RHSA-2026:25239"
},
"details": "OpenSSL is a toolkit that implements the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols, as well as a full-strength general-purpose cryptography library.\n\nSecurity Fix(es):\n\n* openssl: OpenSSL: Heap buffer overflow due to signed integer overflow in Unicode output sizing (CVE-2026-7383)\n\n* openssl: OpenSSL: Denial of Service due to heap out-of-bounds read in CMS password-based decryption (CVE-2026-9076)\n\n* openssl: OpenSSL: Heap buffer over-read in ASN.1 decoding can lead to denial of service or information disclosure. (CVE-2026-34180)\n\n* openssl: PKCS#12 Files with PBMAC1 Are Accepted with Short HMAC Keys (CVE-2026-34181)\n\n* openssl: CMS AuthEnvelopedData Processing May Accept Forged Messages (CVE-2026-34182)\n\n* openssl: Unbounded Memory Growth in the QUIC PATH_CHALLENGE Handler (CVE-2026-34183)\n\n* openssl: NULL pointer dereference in QUIC server initial packet handling (CVE-2026-42764)\n\n* openssl: Possible NULL Dereference in Password-Based CMS Decryption (CVE-2026-42766)\n\n* openssl: NULL Pointer Dereference in CRMF EncryptedValue Decryption (CVE-2026-42767)\n\n* openssl: Multi-RecipientInfo Bleichenbacher Oracle in CMS_decrypt() and PKCS7_decrypt() (CVE-2026-42768)\n\n* openssl: Trust-Anchor Substitution via cert/issuer Typo in CMP rootCaKeyUpdate (CVE-2026-42769)\n\n* openssl: FFC-DH Peer Validation Uses Attacker-Supplied q (CVE-2026-42770)\n\n* openssl: AES-OCB IV Ignored on EVP_Cipher() Path (CVE-2026-45445)\n\n* openssl: Incorrect Tag Processing for Empty Messages in AES-GCM-SIV and AES-SIV modes (CVE-2026-45446)\n\n* openssl: Heap Use-After-Free in OpenSSL PKCS7_verify() (CVE-2026-45447)\n\nFor more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.",
"id": "RLSA-2026:25239",
"modified": "2026-06-27T00:06:16.715697Z",
"published": "2026-06-13T00:03:17.085789Z",
"references": [
{
"type": "ADVISORY",
"url": "https://errata.rockylinux.org/RLSA-2026:25239"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2481879"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2481880"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2481881"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2481882"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2481884"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2481885"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2481887"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2481890"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2481891"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2481892"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2481893"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2481894"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2481896"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2481897"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2481898"
},
{
"type": "ADVISORY",
"url": "https://access.redhat.com/errata/RHSA-2026:25239"
}
],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
"type": "CVSS_V3"
}
],
"summary": "Important: openssl security update",
"upstream": [
"CVE-2026-34180",
"CVE-2026-34181",
"CVE-2026-34182",
"CVE-2026-34183",
"CVE-2026-42764",
"CVE-2026-42766",
"CVE-2026-42767",
"CVE-2026-42768",
"CVE-2026-42769",
"CVE-2026-42770",
"CVE-2026-45445",
"CVE-2026-45446",
"CVE-2026-45447",
"CVE-2026-7383",
"CVE-2026-9076"
]
}
UBUNTU-CVE-2026-42766 (CVE-2026-42766)
Vulnerability from osv_ubuntu – Published: 2026-06-09 00:00 – Updated: 2026-10-17 09:40 – Source websiteIssue summary: A specially crafted password-encrypted CMS message can trigger a NULL pointer dereference during CMS decryption. Impact summary: This NULL pointer dereference leads to an application crash and a Denial of Service. The CMS PasswordRecipientInfo.keyDerivationAlgorithm field is defined as OPTIONAL in the ASN.1 specification and may therefore be absent in specially crafted inputs. During the password-based CMS decryption the OpenSSL CMS implementation dereferences this field without first checking whether it was present. An attacker who supplies such a CMS message to an application performing password-based CMS decryption can trigger an application crash, leading to a Denial of Service. Applications that process password-encrypted CMS messages may be affected. The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.
{
"affected": [
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro with Legacy support add-on: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "libssl1.0.0",
"binary_version": "1.0.1f-1ubuntu2.27+esm14"
},
{
"binary_name": "openssl",
"binary_version": "1.0.1f-1ubuntu2.27+esm14"
}
],
"priority_reason": "OpenSSL developers have rated this as being low severity"
},
"package": {
"ecosystem": "Ubuntu:Pro:14.04:LTS",
"name": "openssl",
"purl": "pkg:deb/ubuntu/openssl@1.0.1f-1ubuntu2.27+esm14?arch=source\u0026distro=esm-infra-legacy/trusty"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.0.1f-1ubuntu2.27+esm14"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.0.1e-3ubuntu1",
"1.0.1e-4ubuntu1",
"1.0.1e-4ubuntu2",
"1.0.1e-4ubuntu3",
"1.0.1e-4ubuntu4",
"1.0.1f-1ubuntu1",
"1.0.1f-1ubuntu2",
"1.0.1f-1ubuntu2.1",
"1.0.1f-1ubuntu2.2",
"1.0.1f-1ubuntu2.3",
"1.0.1f-1ubuntu2.4",
"1.0.1f-1ubuntu2.5",
"1.0.1f-1ubuntu2.7",
"1.0.1f-1ubuntu2.8",
"1.0.1f-1ubuntu2.11",
"1.0.1f-1ubuntu2.12",
"1.0.1f-1ubuntu2.15",
"1.0.1f-1ubuntu2.16",
"1.0.1f-1ubuntu2.17",
"1.0.1f-1ubuntu2.18",
"1.0.1f-1ubuntu2.19",
"1.0.1f-1ubuntu2.20",
"1.0.1f-1ubuntu2.21",
"1.0.1f-1ubuntu2.22",
"1.0.1f-1ubuntu2.23",
"1.0.1f-1ubuntu2.24",
"1.0.1f-1ubuntu2.25",
"1.0.1f-1ubuntu2.26",
"1.0.1f-1ubuntu2.27",
"1.0.1f-1ubuntu2.27+esm1",
"1.0.1f-1ubuntu2.27+esm2",
"1.0.1f-1ubuntu2.27+esm3",
"1.0.1f-1ubuntu2.27+esm4",
"1.0.1f-1ubuntu2.27+esm5",
"1.0.1f-1ubuntu2.27+esm6",
"1.0.1f-1ubuntu2.27+esm7",
"1.0.1f-1ubuntu2.27+esm9",
"1.0.1f-1ubuntu2.27+esm10",
"1.0.1f-1ubuntu2.27+esm11",
"1.0.1f-1ubuntu2.27+esm12",
"1.0.1f-1ubuntu2.27+esm13"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro with Legacy support add-on: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "libssl1.0.0",
"binary_version": "1.0.2g-1ubuntu4.20+esm16"
},
{
"binary_name": "openssl",
"binary_version": "1.0.2g-1ubuntu4.20+esm16"
}
],
"priority_reason": "OpenSSL developers have rated this as being low severity"
},
"package": {
"ecosystem": "Ubuntu:Pro:16.04:LTS",
"name": "openssl",
"purl": "pkg:deb/ubuntu/openssl@1.0.2g-1ubuntu4.20+esm16?arch=source\u0026distro=esm-infra-legacy/xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.0.2g-1ubuntu4.20+esm16"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.0.2d-0ubuntu1",
"1.0.2d-0ubuntu2",
"1.0.2e-1ubuntu1",
"1.0.2f-2ubuntu1",
"1.0.2g-1ubuntu2",
"1.0.2g-1ubuntu3",
"1.0.2g-1ubuntu4",
"1.0.2g-1ubuntu4.1",
"1.0.2g-1ubuntu4.2",
"1.0.2g-1ubuntu4.4",
"1.0.2g-1ubuntu4.5",
"1.0.2g-1ubuntu4.6",
"1.0.2g-1ubuntu4.8",
"1.0.2g-1ubuntu4.9",
"1.0.2g-1ubuntu4.10",
"1.0.2g-1ubuntu4.11",
"1.0.2g-1ubuntu4.12",
"1.0.2g-1ubuntu4.13",
"1.0.2g-1ubuntu4.14",
"1.0.2g-1ubuntu4.15",
"1.0.2g-1ubuntu4.16",
"1.0.2g-1ubuntu4.17",
"1.0.2g-1ubuntu4.18",
"1.0.2g-1ubuntu4.19",
"1.0.2g-1ubuntu4.20",
"1.0.2g-1ubuntu4.20+esm1",
"1.0.2g-1ubuntu4.20+esm2",
"1.0.2g-1ubuntu4.20+esm3",
"1.0.2g-1ubuntu4.20+esm4",
"1.0.2g-1ubuntu4.20+esm5",
"1.0.2g-1ubuntu4.20+esm6",
"1.0.2g-1ubuntu4.20+esm7",
"1.0.2g-1ubuntu4.20+esm9",
"1.0.2g-1ubuntu4.20+esm10",
"1.0.2g-1ubuntu4.20+esm11",
"1.0.2g-1ubuntu4.20+esm12",
"1.0.2g-1ubuntu4.20+esm13",
"1.0.2g-1ubuntu4.20+esm14",
"1.0.2g-1ubuntu4.20+esm15"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "ovmf",
"binary_version": "0~20160408.ffea0a2c-2ubuntu0.2+esm4"
},
{
"binary_name": "qemu-efi",
"binary_version": "0~20160408.ffea0a2c-2ubuntu0.2+esm4"
}
],
"priority_reason": "OpenSSL developers have rated this as being low severity"
},
"package": {
"ecosystem": "Ubuntu:Pro:16.04:LTS",
"name": "edk2",
"purl": "pkg:deb/ubuntu/edk2@0~20160408.ffea0a2c-2ubuntu0.2+esm4?arch=source\u0026distro=esm-apps-legacy/xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0~20150106.5c2d456b-2",
"0~20160104.c2a892d7-1",
"0~20160408.ffea0a2c-2",
"0~20160408.ffea0a2c-2ubuntu0.1",
"0~20160408.ffea0a2c-2ubuntu0.2",
"0~20160408.ffea0a2c-2ubuntu0.2+esm1",
"0~20160408.ffea0a2c-2ubuntu0.2+esm3",
"0~20160408.ffea0a2c-2ubuntu0.2+esm4"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "nodejs",
"binary_version": "4.2.6~dfsg-1ubuntu4.2+esm3"
},
{
"binary_name": "nodejs-legacy",
"binary_version": "4.2.6~dfsg-1ubuntu4.2+esm3"
}
],
"priority_reason": "OpenSSL developers have rated this as being low severity"
},
"package": {
"ecosystem": "Ubuntu:Pro:16.04:LTS",
"name": "nodejs",
"purl": "pkg:deb/ubuntu/nodejs@4.2.6~dfsg-1ubuntu4.2+esm3?arch=source\u0026distro=esm-apps/xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.10.25~dfsg2-2ubuntu1",
"4.2.2~dfsg-1",
"4.2.3~dfsg-1",
"4.2.4~dfsg-1ubuntu1",
"4.2.4~dfsg-2",
"4.2.6~dfsg-1ubuntu1",
"4.2.6~dfsg-1ubuntu4",
"4.2.6~dfsg-1ubuntu4.1",
"4.2.6~dfsg-1ubuntu4.2",
"4.2.6~dfsg-1ubuntu4.2+esm1",
"4.2.6~dfsg-1ubuntu4.2+esm2",
"4.2.6~dfsg-1ubuntu4.2+esm3"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libssl1.0.0",
"binary_version": "1.0.2g-1ubuntu4.fips.4.20.15"
},
{
"binary_name": "libssl1.0.0-hmac",
"binary_version": "1.0.2g-1ubuntu4.fips.4.20.15"
},
{
"binary_name": "openssl",
"binary_version": "1.0.2g-1ubuntu4.fips.4.20.15"
}
],
"priority_reason": "OpenSSL developers have rated this as being low severity"
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-updates:16.04:LTS",
"name": "openssl",
"purl": "pkg:deb/ubuntu/openssl@1.0.2g-1ubuntu4.fips.4.20.15?arch=source\u0026distro=fips-updates/xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.0.2g-1ubuntu4.fips.4.9.1",
"1.0.2g-1ubuntu4.fips.4.13.1",
"1.0.2g-1ubuntu4.fips.4.15.1",
"1.0.2g-1ubuntu4.fips.4.16.1",
"1.0.2g-1ubuntu4.fips.4.17.1",
"1.0.2g-1ubuntu4.fips.4.18.1",
"1.0.2g-1ubuntu4.fips.4.19.3",
"1.0.2g-1ubuntu4.fips.4.20.1",
"1.0.2g-1ubuntu4.fips.4.20.2",
"1.0.2g-1ubuntu4.fips.4.20.3",
"1.0.2g-1ubuntu4.fips.4.20.6",
"1.0.2g-1ubuntu4.fips.4.20.7",
"1.0.2g-1ubuntu4.fips.4.20.9",
"1.0.2g-1ubuntu4.fips.4.20.10",
"1.0.2g-1ubuntu4.fips.4.20.11",
"1.0.2g-1ubuntu4.fips.4.20.12",
"1.0.2g-1ubuntu4.fips.4.20.13",
"1.0.2g-1ubuntu4.fips.4.20.14",
"1.0.2g-1ubuntu4.fips.4.20.15"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libssl1.0.0",
"binary_version": "1.0.2g-1ubuntu4.fips.4.6.3"
},
{
"binary_name": "libssl1.0.0-hmac",
"binary_version": "1.0.2g-1ubuntu4.fips.4.6.3"
},
{
"binary_name": "openssl",
"binary_version": "1.0.2g-1ubuntu4.fips.4.6.3"
}
],
"priority_reason": "OpenSSL developers have rated this as being low severity"
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS:16.04:LTS",
"name": "openssl",
"purl": "pkg:deb/ubuntu/openssl@1.0.2g-1ubuntu4.fips.4.6.3?arch=source\u0026distro=fips/xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.0.2g-1ubuntu4.fips.4.6~ppa1",
"1.0.2g-1ubuntu4.fips.4.6~ppa2",
"1.0.2g-1ubuntu4.fips.4.6~ppa3",
"1.0.2g-1ubuntu4.fips.4.6",
"1.0.2g-1ubuntu4.fips.4.6.1",
"1.0.2g-1ubuntu4.fips.4.6.2",
"1.0.2g-1ubuntu4.fips.4.6.3"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "libssl1.1",
"binary_version": "1.1.1-1ubuntu2.1~18.04.23+esm9"
},
{
"binary_name": "openssl",
"binary_version": "1.1.1-1ubuntu2.1~18.04.23+esm9"
}
],
"priority_reason": "OpenSSL developers have rated this as being low severity"
},
"package": {
"ecosystem": "Ubuntu:Pro:18.04:LTS",
"name": "openssl",
"purl": "pkg:deb/ubuntu/openssl@1.1.1-1ubuntu2.1~18.04.23+esm9?arch=source\u0026distro=esm-infra/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.1.1-1ubuntu2.1~18.04.23+esm9"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.0.2g-1ubuntu13",
"1.0.2g-1ubuntu14",
"1.0.2n-1ubuntu1",
"1.1.0g-2ubuntu1",
"1.1.0g-2ubuntu2",
"1.1.0g-2ubuntu3",
"1.1.0g-2ubuntu4",
"1.1.0g-2ubuntu4.1",
"1.1.0g-2ubuntu4.3",
"1.1.1-1ubuntu2.1~18.04.1",
"1.1.1-1ubuntu2.1~18.04.2",
"1.1.1-1ubuntu2.1~18.04.3",
"1.1.1-1ubuntu2.1~18.04.4",
"1.1.1-1ubuntu2.1~18.04.5",
"1.1.1-1ubuntu2.1~18.04.6",
"1.1.1-1ubuntu2.1~18.04.7",
"1.1.1-1ubuntu2.1~18.04.8",
"1.1.1-1ubuntu2.1~18.04.9",
"1.1.1-1ubuntu2.1~18.04.10",
"1.1.1-1ubuntu2.1~18.04.13",
"1.1.1-1ubuntu2.1~18.04.14",
"1.1.1-1ubuntu2.1~18.04.15",
"1.1.1-1ubuntu2.1~18.04.17",
"1.1.1-1ubuntu2.1~18.04.19",
"1.1.1-1ubuntu2.1~18.04.20",
"1.1.1-1ubuntu2.1~18.04.21",
"1.1.1-1ubuntu2.1~18.04.22",
"1.1.1-1ubuntu2.1~18.04.23",
"1.1.1-1ubuntu2.1~18.04.23+esm1",
"1.1.1-1ubuntu2.1~18.04.23+esm3",
"1.1.1-1ubuntu2.1~18.04.23+esm4",
"1.1.1-1ubuntu2.1~18.04.23+esm5",
"1.1.1-1ubuntu2.1~18.04.23+esm6",
"1.1.1-1ubuntu2.1~18.04.23+esm7",
"1.1.1-1ubuntu2.1~18.04.23+esm8"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "libssl1.0.0",
"binary_version": "1.0.2n-1ubuntu5.13+esm5"
},
{
"binary_name": "openssl1.0",
"binary_version": "1.0.2n-1ubuntu5.13+esm5"
}
],
"priority_reason": "OpenSSL developers have rated this as being low severity"
},
"package": {
"ecosystem": "Ubuntu:Pro:18.04:LTS",
"name": "openssl1.0",
"purl": "pkg:deb/ubuntu/openssl1.0@1.0.2n-1ubuntu5.13+esm5?arch=source\u0026distro=esm-infra/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.0.2n-1ubuntu5.13+esm5"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.0.2n-1ubuntu2",
"1.0.2n-1ubuntu3",
"1.0.2n-1ubuntu4",
"1.0.2n-1ubuntu5",
"1.0.2n-1ubuntu5.1",
"1.0.2n-1ubuntu5.2",
"1.0.2n-1ubuntu5.3",
"1.0.2n-1ubuntu5.4",
"1.0.2n-1ubuntu5.5",
"1.0.2n-1ubuntu5.6",
"1.0.2n-1ubuntu5.7",
"1.0.2n-1ubuntu5.8",
"1.0.2n-1ubuntu5.9",
"1.0.2n-1ubuntu5.10",
"1.0.2n-1ubuntu5.11",
"1.0.2n-1ubuntu5.12",
"1.0.2n-1ubuntu5.13",
"1.0.2n-1ubuntu5.13+esm1",
"1.0.2n-1ubuntu5.13+esm2",
"1.0.2n-1ubuntu5.13+esm3",
"1.0.2n-1ubuntu5.13+esm4"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "ovmf",
"binary_version": "0~20180205.c0d9813c-2ubuntu0.3+esm3"
},
{
"binary_name": "qemu-efi",
"binary_version": "0~20180205.c0d9813c-2ubuntu0.3+esm3"
},
{
"binary_name": "qemu-efi-aarch64",
"binary_version": "0~20180205.c0d9813c-2ubuntu0.3+esm3"
},
{
"binary_name": "qemu-efi-arm",
"binary_version": "0~20180205.c0d9813c-2ubuntu0.3+esm3"
}
],
"priority_reason": "OpenSSL developers have rated this as being low severity"
},
"package": {
"ecosystem": "Ubuntu:Pro:18.04:LTS",
"name": "edk2",
"purl": "pkg:deb/ubuntu/edk2@0~20180205.c0d9813c-2ubuntu0.3+esm3?arch=source\u0026distro=esm-apps/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0~20170911.5dfba97c-1",
"0~20171010.234dbcef-1",
"0~20171027.76fd5a66-1",
"0~20171205.a9212288-1",
"0~20180105.0bc94c74-1",
"0~20180205.c0d9813c-1",
"0~20180205.c0d9813c-2",
"0~20180205.c0d9813c-2ubuntu0.1",
"0~20180205.c0d9813c-2ubuntu0.2",
"0~20180205.c0d9813c-2ubuntu0.3",
"0~20180205.c0d9813c-2ubuntu0.3+esm1",
"0~20180205.c0d9813c-2ubuntu0.3+esm2",
"0~20180205.c0d9813c-2ubuntu0.3+esm3"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "nodejs",
"binary_version": "8.10.0~dfsg-2ubuntu0.4+esm6"
}
],
"priority_reason": "OpenSSL developers have rated this as being low severity"
},
"package": {
"ecosystem": "Ubuntu:Pro:18.04:LTS",
"name": "nodejs",
"purl": "pkg:deb/ubuntu/nodejs@8.10.0~dfsg-2ubuntu0.4+esm6?arch=source\u0026distro=esm-apps/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.11.4~dfsg-1ubuntu1",
"6.11.4~dfsg-1ubuntu2",
"6.12.0~dfsg-1ubuntu1",
"6.12.0~dfsg-2ubuntu1",
"6.12.0~dfsg-2ubuntu2",
"8.10.0~dfsg-2",
"8.10.0~dfsg-2ubuntu0.2",
"8.10.0~dfsg-2ubuntu0.3",
"8.10.0~dfsg-2ubuntu0.4",
"8.10.0~dfsg-2ubuntu0.4+esm1",
"8.10.0~dfsg-2ubuntu0.4+esm2",
"8.10.0~dfsg-2ubuntu0.4+esm3",
"8.10.0~dfsg-2ubuntu0.4+esm4",
"8.10.0~dfsg-2ubuntu0.4+esm5",
"8.10.0~dfsg-2ubuntu0.4+esm6"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "libssl1.1",
"binary_version": "1.1.1-1ubuntu2.fips.2.1~18.04.23.9"
},
{
"binary_name": "libssl1.1-hmac",
"binary_version": "1.1.1-1ubuntu2.fips.2.1~18.04.23.9"
},
{
"binary_name": "openssl",
"binary_version": "1.1.1-1ubuntu2.fips.2.1~18.04.23.9"
}
],
"priority_reason": "OpenSSL developers have rated this as being low severity"
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-updates:18.04:LTS",
"name": "openssl",
"purl": "pkg:deb/ubuntu/openssl@1.1.1-1ubuntu2.fips.2.1~18.04.23.9?arch=source\u0026distro=fips-updates/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.1.1-1ubuntu2.fips.2.1~18.04.23.9"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.1.1-1ubuntu2.fips.2.1~18.04.5.1",
"1.1.1-1ubuntu2.fips.2.1~18.04.6.1",
"1.1.1-1ubuntu2.fips.2.1~18.04.7.1",
"1.1.1-1ubuntu2.fips.2.1~18.04.9.1",
"1.1.1-1ubuntu2.fips.2.1~18.04.9.2",
"1.1.1-1ubuntu2.fips.2.1~18.04.9.3",
"1.1.1-1ubuntu2.fips.2.1~18.04.13.2",
"1.1.1-1ubuntu2.fips.2.1~18.04.15",
"1.1.1-1ubuntu2.fips.2.1~18.04.15.1",
"1.1.1-1ubuntu2.fips.2.1~18.04.15.2",
"1.1.1-1ubuntu2.fips.2.1~18.04.17",
"1.1.1-1ubuntu2.fips.2.1~18.04.20",
"1.1.1-1ubuntu2.fips.2.1~18.04.21",
"1.1.1-1ubuntu2.fips.2.1~18.04.22",
"1.1.1-1ubuntu2.fips.2.1~18.04.23",
"1.1.1-1ubuntu2.fips.2.1~18.04.23.3",
"1.1.1-1ubuntu2.fips.2.1~18.04.23.4",
"1.1.1-1ubuntu2.fips.2.1~18.04.23.5",
"1.1.1-1ubuntu2.fips.2.1~18.04.23.6",
"1.1.1-1ubuntu2.fips.2.1~18.04.23.7",
"1.1.1-1ubuntu2.fips.2.1~18.04.23.8"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libssl1.1",
"binary_version": "1.1.1-1ubuntu2.fips.2.1~18.04.15.2"
},
{
"binary_name": "libssl1.1-hmac",
"binary_version": "1.1.1-1ubuntu2.fips.2.1~18.04.15.2"
},
{
"binary_name": "openssl",
"binary_version": "1.1.1-1ubuntu2.fips.2.1~18.04.15.2"
}
],
"priority_reason": "OpenSSL developers have rated this as being low severity"
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS:18.04:LTS",
"name": "openssl",
"purl": "pkg:deb/ubuntu/openssl@1.1.1-1ubuntu2.fips.2.1~18.04.15.2?arch=source\u0026distro=fips/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.1.1-1ubuntu2.fips.2.1~18.04.3.1",
"1.1.1-1ubuntu2.fips.2.1~18.04.15.2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "ovmf",
"binary_version": "0~20191122.bd85bf54-2ubuntu3.6+esm1"
},
{
"binary_name": "qemu-efi",
"binary_version": "0~20191122.bd85bf54-2ubuntu3.6+esm1"
},
{
"binary_name": "qemu-efi-aarch64",
"binary_version": "0~20191122.bd85bf54-2ubuntu3.6+esm1"
},
{
"binary_name": "qemu-efi-arm",
"binary_version": "0~20191122.bd85bf54-2ubuntu3.6+esm1"
}
],
"priority_reason": "OpenSSL developers have rated this as being low severity"
},
"package": {
"ecosystem": "Ubuntu:Pro:20.04:LTS",
"name": "edk2",
"purl": "pkg:deb/ubuntu/edk2@0~20191122.bd85bf54-2ubuntu3.6+esm1?arch=source\u0026distro=esm-infra/focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0~20190606.20d2e5a1-2ubuntu1",
"0~20190828.37eef910-3",
"0~20190828.37eef910-4",
"0~20191122.bd85bf54-1",
"0~20191122.bd85bf54-1ubuntu1",
"0~20191122.bd85bf54-2",
"0~20191122.bd85bf54-2ubuntu1",
"0~20191122.bd85bf54-2ubuntu2",
"0~20191122.bd85bf54-2ubuntu3",
"0~20191122.bd85bf54-2ubuntu3.1",
"0~20191122.bd85bf54-2ubuntu3.2",
"0~20191122.bd85bf54-2ubuntu3.3",
"0~20191122.bd85bf54-2ubuntu3.4",
"0~20191122.bd85bf54-2ubuntu3.5",
"0~20191122.bd85bf54-2ubuntu3.6",
"0~20191122.bd85bf54-2ubuntu3.6+esm1"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "libssl1.1",
"binary_version": "1.1.1f-1ubuntu2.24+esm4"
},
{
"binary_name": "openssl",
"binary_version": "1.1.1f-1ubuntu2.24+esm4"
}
],
"priority_reason": "OpenSSL developers have rated this as being low severity"
},
"package": {
"ecosystem": "Ubuntu:Pro:20.04:LTS",
"name": "openssl",
"purl": "pkg:deb/ubuntu/openssl@1.1.1f-1ubuntu2.24+esm4?arch=source\u0026distro=esm-infra/focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.1.1f-1ubuntu2.24+esm4"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.1.1c-1ubuntu4",
"1.1.1d-2ubuntu3",
"1.1.1d-2ubuntu6",
"1.1.1f-1ubuntu1",
"1.1.1f-1ubuntu2",
"1.1.1f-1ubuntu2.1",
"1.1.1f-1ubuntu2.2",
"1.1.1f-1ubuntu2.3",
"1.1.1f-1ubuntu2.4",
"1.1.1f-1ubuntu2.5",
"1.1.1f-1ubuntu2.8",
"1.1.1f-1ubuntu2.9",
"1.1.1f-1ubuntu2.10",
"1.1.1f-1ubuntu2.11",
"1.1.1f-1ubuntu2.12",
"1.1.1f-1ubuntu2.13",
"1.1.1f-1ubuntu2.15",
"1.1.1f-1ubuntu2.16",
"1.1.1f-1ubuntu2.17",
"1.1.1f-1ubuntu2.18",
"1.1.1f-1ubuntu2.19",
"1.1.1f-1ubuntu2.20",
"1.1.1f-1ubuntu2.21",
"1.1.1f-1ubuntu2.22",
"1.1.1f-1ubuntu2.23",
"1.1.1f-1ubuntu2.24",
"1.1.1f-1ubuntu2.24+esm1",
"1.1.1f-1ubuntu2.24+esm2",
"1.1.1f-1ubuntu2.24+esm3"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "libssl1.1",
"binary_version": "1.1.1f-1ubuntu2.fips.24.4"
},
{
"binary_name": "libssl1.1-hmac",
"binary_version": "1.1.1f-1ubuntu2.fips.24.4"
},
{
"binary_name": "openssl",
"binary_version": "1.1.1f-1ubuntu2.fips.24.4"
}
],
"priority_reason": "OpenSSL developers have rated this as being low severity"
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-updates:20.04:LTS",
"name": "openssl",
"purl": "pkg:deb/ubuntu/openssl@1.1.1f-1ubuntu2.fips.24.4?arch=source\u0026distro=fips-updates/focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.1.1f-1ubuntu2.fips.24.4"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.1.1f-1ubuntu2.fips.7",
"1.1.1f-1ubuntu2.fips.7.2",
"1.1.1f-1ubuntu2.fips.12",
"1.1.1f-1ubuntu2.fips.13",
"1.1.1f-1ubuntu2.fips.13.1",
"1.1.1f-1ubuntu2.fips.16",
"1.1.1f-1ubuntu2.fips.17",
"1.1.1f-1ubuntu2.fips.18",
"1.1.1f-1ubuntu2.fips.19",
"1.1.1f-1ubuntu2.fips.20",
"1.1.1f-1ubuntu2.fips.21",
"1.1.1f-1ubuntu2.fips.22",
"1.1.1f-1ubuntu2.fips.24",
"1.1.1f-1ubuntu2.fips.24.1",
"1.1.1f-1ubuntu2.fips.24.2",
"1.1.1f-1ubuntu2.fips.24.3"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libssl1.1",
"binary_version": "1.1.1f-1ubuntu2.fips.7.1"
},
{
"binary_name": "libssl1.1-hmac",
"binary_version": "1.1.1f-1ubuntu2.fips.7.1"
},
{
"binary_name": "openssl",
"binary_version": "1.1.1f-1ubuntu2.fips.7.1"
}
],
"priority_reason": "OpenSSL developers have rated this as being low severity"
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS:20.04:LTS",
"name": "openssl",
"purl": "pkg:deb/ubuntu/openssl@1.1.1f-1ubuntu2.fips.7.1?arch=source\u0026distro=fips/focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.1.1f-1ubuntu2.fips.2.8",
"1.1.1f-1ubuntu2.fips.7.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "ovmf",
"binary_version": "2022.02-3ubuntu0.22.04.7"
},
{
"binary_name": "ovmf-ia32",
"binary_version": "2022.02-3ubuntu0.22.04.7"
},
{
"binary_name": "qemu-efi",
"binary_version": "2022.02-3ubuntu0.22.04.7"
},
{
"binary_name": "qemu-efi-aarch64",
"binary_version": "2022.02-3ubuntu0.22.04.7"
},
{
"binary_name": "qemu-efi-arm",
"binary_version": "2022.02-3ubuntu0.22.04.7"
}
],
"priority_reason": "OpenSSL developers have rated this as being low severity"
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "edk2",
"purl": "pkg:deb/ubuntu/edk2@2022.02-3ubuntu0.22.04.7?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2021.08~rc0-2",
"2021.08-3",
"2021.11~rc1-1",
"2021.11-1",
"2021.11-2",
"2022.02~rc1-1",
"2022.02~rc1-1ubuntu1",
"2022.02-1",
"2022.02-2",
"2022.02-3",
"2022.02-3ubuntu0.22.04.1",
"2022.02-3ubuntu0.22.04.2",
"2022.02-3ubuntu0.22.04.3",
"2022.02-3ubuntu0.22.04.4",
"2022.02-3ubuntu0.22.04.5",
"2022.02-3ubuntu0.22.04.6",
"2022.02-3ubuntu0.22.04.7"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "libssl3",
"binary_version": "3.0.2-0ubuntu1.25"
},
{
"binary_name": "openssl",
"binary_version": "3.0.2-0ubuntu1.25"
}
],
"priority_reason": "OpenSSL developers have rated this as being low severity"
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "openssl",
"purl": "pkg:deb/ubuntu/openssl@3.0.2-0ubuntu1.25?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.0.2-0ubuntu1.25"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.1.1l-1ubuntu1",
"3.0.0-1ubuntu1",
"3.0.1-0ubuntu1",
"3.0.2-0ubuntu1",
"3.0.2-0ubuntu1.1",
"3.0.2-0ubuntu1.2",
"3.0.2-0ubuntu1.4",
"3.0.2-0ubuntu1.5",
"3.0.2-0ubuntu1.6",
"3.0.2-0ubuntu1.7",
"3.0.2-0ubuntu1.8",
"3.0.2-0ubuntu1.9",
"3.0.2-0ubuntu1.10",
"3.0.2-0ubuntu1.12",
"3.0.2-0ubuntu1.13",
"3.0.2-0ubuntu1.14",
"3.0.2-0ubuntu1.15",
"3.0.2-0ubuntu1.16",
"3.0.2-0ubuntu1.17",
"3.0.2-0ubuntu1.18",
"3.0.2-0ubuntu1.19",
"3.0.2-0ubuntu1.20",
"3.0.2-0ubuntu1.21",
"3.0.2-0ubuntu1.23"
]
},
{
"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": "libssl3",
"binary_version": "3.0.2-0ubuntu1.12+Fips1"
},
{
"binary_name": "openssl",
"binary_version": "3.0.2-0ubuntu1.12+Fips1"
}
],
"priority_reason": "OpenSSL developers have rated this as being low severity"
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-preview:22.04:LTS",
"name": "openssl",
"purl": "pkg:deb/ubuntu/openssl@3.0.2-0ubuntu1.12+Fips1?arch=source\u0026distro=fips-preview/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.0.2-0ubuntu1.10+Fips1",
"3.0.2-0ubuntu1.12+Fips1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "openssl-fips-module-3",
"binary_version": "3.0.5-0ubuntu0.1+Fips2.1"
}
],
"priority_reason": "OpenSSL developers have rated this as being low severity"
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-preview:22.04:LTS",
"name": "openssl-fips",
"purl": "pkg:deb/ubuntu/openssl-fips@3.0.5-0ubuntu0.1+Fips2.1?arch=source\u0026distro=fips-preview/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.0.5-0ubuntu0.1+Fips2.1"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "libssl3",
"binary_version": "3.0.2-0ubuntu1.25+Fips1"
},
{
"binary_name": "openssl",
"binary_version": "3.0.2-0ubuntu1.25+Fips1"
}
],
"priority_reason": "OpenSSL developers have rated this as being low severity"
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-updates:22.04:LTS",
"name": "openssl",
"purl": "pkg:deb/ubuntu/openssl@3.0.2-0ubuntu1.25+Fips1?arch=source\u0026distro=fips-updates/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.0.2-0ubuntu1.25+Fips1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.0.2-0ubuntu1.10+Fips1",
"3.0.2-0ubuntu1.12+Fips1",
"3.0.2-0ubuntu1.14+Fips1",
"3.0.2-0ubuntu1.15+Fips1",
"3.0.2-0ubuntu1.16+Fips1",
"3.0.2-0ubuntu1.17+Fips1",
"3.0.2-0ubuntu1.18+Fips1",
"3.0.2-0ubuntu1.19+Fips1",
"3.0.2-0ubuntu1.20+Fips1",
"3.0.2-0ubuntu1.21+Fips1",
"3.0.2-0ubuntu1.23+Fips1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "openssl-fips-module-3",
"binary_version": "3.0.5-0ubuntu0.2+Fips1"
}
],
"priority_reason": "OpenSSL developers have rated this as being low severity"
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-updates:22.04:LTS",
"name": "openssl-fips",
"purl": "pkg:deb/ubuntu/openssl-fips@3.0.5-0ubuntu0.2+Fips1?arch=source\u0026distro=fips-updates/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.0.5-0ubuntu0.1+Fips2.1",
"3.0.5-0ubuntu0.2+Fips1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "efi-shell-aa64",
"binary_version": "2024.02-2ubuntu0.10"
},
{
"binary_name": "efi-shell-arm",
"binary_version": "2024.02-2ubuntu0.10"
},
{
"binary_name": "efi-shell-ia32",
"binary_version": "2024.02-2ubuntu0.10"
},
{
"binary_name": "efi-shell-riscv64",
"binary_version": "2024.02-2ubuntu0.10"
},
{
"binary_name": "efi-shell-x64",
"binary_version": "2024.02-2ubuntu0.10"
},
{
"binary_name": "ovmf",
"binary_version": "2024.02-2ubuntu0.10"
},
{
"binary_name": "ovmf-ia32",
"binary_version": "2024.02-2ubuntu0.10"
},
{
"binary_name": "ovmf-legacy",
"binary_version": "2024.02-2ubuntu0.10"
},
{
"binary_name": "qemu-efi-aarch64",
"binary_version": "2024.02-2ubuntu0.10"
},
{
"binary_name": "qemu-efi-arm",
"binary_version": "2024.02-2ubuntu0.10"
},
{
"binary_name": "qemu-efi-riscv64",
"binary_version": "2024.02-2ubuntu0.10"
}
],
"priority_reason": "OpenSSL developers have rated this as being low severity"
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "edk2",
"purl": "pkg:deb/ubuntu/edk2@2024.02-2ubuntu0.10?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2023.05-2",
"2023.11-2",
"2023.11-3",
"2023.11-4",
"2023.11-5",
"2023.11-6",
"2023.11-8",
"2024.02-1",
"2024.02-2",
"2024.02-2ubuntu0.1",
"2024.02-2ubuntu0.3",
"2024.02-2ubuntu0.4",
"2024.02-2ubuntu0.5",
"2024.02-2ubuntu0.6",
"2024.02-2ubuntu0.7",
"2024.02-2ubuntu0.8",
"2024.02-2ubuntu0.9",
"2024.02-2ubuntu0.10"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "libssl3t64",
"binary_version": "3.0.13-0ubuntu3.11"
},
{
"binary_name": "openssl",
"binary_version": "3.0.13-0ubuntu3.11"
}
],
"priority_reason": "OpenSSL developers have rated this as being low severity"
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "openssl",
"purl": "pkg:deb/ubuntu/openssl@3.0.13-0ubuntu3.11?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.0.13-0ubuntu3.11"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.0.10-1ubuntu2",
"3.0.10-1ubuntu2.1",
"3.0.10-1ubuntu3",
"3.0.10-1ubuntu4",
"3.0.13-0ubuntu2",
"3.0.13-0ubuntu3",
"3.0.13-0ubuntu3.1",
"3.0.13-0ubuntu3.2",
"3.0.13-0ubuntu3.3",
"3.0.13-0ubuntu3.4",
"3.0.13-0ubuntu3.5",
"3.0.13-0ubuntu3.6",
"3.0.13-0ubuntu3.7",
"3.0.13-0ubuntu3.9"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "openssl-fips-module-3",
"binary_version": "3.0.13-0ubuntu3.12+Fips1"
}
],
"priority_reason": "OpenSSL developers have rated this as being low severity"
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-updates:24.04:LTS",
"name": "openssl-fips",
"purl": "pkg:deb/ubuntu/openssl-fips@3.0.13-0ubuntu3.12+Fips1?arch=source\u0026distro=fips-updates/noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.0.13-0ubuntu3.12+Fips1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.0.13-0ubuntu3+Fips1",
"3.0.13-0ubuntu3.6+Fips1"
]
},
{
"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: A specially crafted password-encrypted CMS message can trigger a NULL pointer dereference during CMS decryption. Impact summary: This NULL pointer dereference leads to an application crash and a Denial of Service. The CMS PasswordRecipientInfo.keyDerivationAlgorithm field is defined as OPTIONAL in the ASN.1 specification and may therefore be absent in specially crafted inputs. During the password-based CMS decryption the OpenSSL CMS implementation dereferences this field without first checking whether it was present. An attacker who supplies such a CMS message to an application performing password-based CMS decryption can trigger an application crash, leading to a Denial of Service. Applications that process password-encrypted CMS messages may be affected. The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.",
"id": "UBUNTU-CVE-2026-42766",
"modified": "2026-10-17T09:40:59Z",
"published": "2026-06-09T00:00:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-42766"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42766"
},
{
"type": "REPORT",
"url": "https://openssl-library.org/news/secadv/20260609.txt"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-8414-2"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-8414-1"
}
],
"related": [
"USN-8414-2",
"USN-8414-1"
],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
},
{
"score": "low",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-42766"
]
}
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.