Search
Find a vulnerability
Search criteria
ⓘ
Use this form to refine search results.
Full-text search supports keyword queries with ranking and filtering.
You can combine vendor, product, and sources to narrow results.
Enable “Apply ordering” to sort by date instead of relevance.
998 vulnerabilities by openssl
CVE-2026-95690 (GCVE-0-2026-95690)
Vulnerability from nvd – Published: 2026-11-18 11:44 – Updated: 2026-11-18 15:23
VLAI
EPSS
VEX
Summary
Receiving crafted out-of-sequence DTLS handshake fragments may cause OpenSSL to allocate a full message-length reassembly buffer for each buffered message, so a small amount of wire data consumes a large amount of memory.
Severity
5.3 (Medium)
SSVC
Exploitation: none
Automatable: yes
Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-18 13:50 UTC
CWE
- CWE-400 - Uncontrolled Resource Consumption
Assigner
References
2 references
Impacted products
{
"containers": {
"adp": [
{
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "LOW",
"baseScore": 5.3,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L",
"version": "3.1"
}
},
{
"other": {
"content": {
"id": "CVE-2026-95690",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-18T13:50:26.611679Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-400",
"description": "CWE-400 Uncontrolled Resource Consumption",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T15:23:34.371Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "OpenSSL",
"vendor": "OpenSSL",
"versions": [
{
"lessThan": "4.1.1",
"status": "affected",
"version": "4.1.0",
"versionType": "semver"
},
{
"lessThan": "4.0.4",
"status": "affected",
"version": "4.0.0",
"versionType": "semver"
},
{
"lessThan": "3.5.10",
"status": "affected",
"version": "3.5.0",
"versionType": "semver"
},
{
"lessThan": "3.0.24",
"status": "affected",
"version": "3.0.0",
"versionType": "semver"
},
{
"lessThan": "1.1.1zk",
"status": "affected",
"version": "1.1.1",
"versionType": "custom"
},
{
"lessThan": "1.0.2zt",
"status": "affected",
"version": "1.0.2",
"versionType": "custom"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "Receiving crafted out-of-sequence DTLS handshake fragments may cause OpenSSL to allocate a full message-length reassembly buffer for each buffered message, so a small amount of wire data consumes a large amount of memory."
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T11:44:16.564Z",
"orgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"shortName": "openssl"
},
"references": [
{
"name": "Fix PR for 4.1",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/pull/33620"
},
{
"name": "Fix PR for 4.0 and 3.5",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/pull/33729"
}
],
"x_generator": {
"engine": "cvelib 1.8.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"assignerShortName": "openssl",
"cveId": "CVE-2026-95690",
"datePublished": "2026-11-18T11:44:16.564Z",
"dateReserved": "2026-09-22T14:18:48.634Z",
"dateUpdated": "2026-11-18T15:23:34.371Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-84786 (GCVE-0-2026-84786)
Vulnerability from nvd – Published: 2026-11-18 11:43 – Updated: 2026-11-18 11:43
VLAI
EPSS
VEX
Summary
A DANE-enabled TLS client may crash by dereferencing a NULL pointer when processing an unusual combination of certificate and TLSA records.
Severity
No CVSS data available.
Assigner
References
1 reference
| URL | Tags |
|---|---|
| https://github.com/openssl/openssl/pull/33634 | patch |
Impacted products
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "OpenSSL",
"vendor": "OpenSSL",
"versions": [
{
"lessThan": "4.1.1",
"status": "affected",
"version": "4.1.0",
"versionType": "semver"
},
{
"lessThan": "4.0.4",
"status": "affected",
"version": "4.0.0",
"versionType": "semver"
},
{
"lessThan": "3.5.10",
"status": "affected",
"version": "3.5.0",
"versionType": "semver"
},
{
"lessThan": "3.0.24",
"status": "affected",
"version": "3.0.0",
"versionType": "semver"
},
{
"lessThan": "1.1.1zk",
"status": "affected",
"version": "1.1.1",
"versionType": "custom"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "A DANE-enabled TLS client may crash by dereferencing a NULL pointer when processing an unusual combination of certificate and TLSA records."
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T11:43:57.201Z",
"orgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"shortName": "openssl"
},
"references": [
{
"name": "Fix PR #33634",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/pull/33634"
}
],
"x_generator": {
"engine": "cvelib 1.8.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"assignerShortName": "openssl",
"cveId": "CVE-2026-84786",
"datePublished": "2026-11-18T11:43:57.201Z",
"dateReserved": "2026-09-02T10:14:02.262Z",
"dateUpdated": "2026-11-18T11:43:57.201Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-121482 (GCVE-0-2026-121482)
Vulnerability from nvd – Published: 2026-11-18 11:43 – Updated: 2026-11-18 11:43
VLAI
EPSS
VEX
Summary
Verifying a maliciously crafted CMS or PKCS#7 SignedData message with CRL checking enabled may consume excessive CPU time, growing with the square of the message size.
Severity
No CVSS data available.
Assigner
References
1 reference
| URL | Tags |
|---|---|
| https://github.com/openssl/openssl/pull/33546 | patch |
Impacted products
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "OpenSSL",
"vendor": "OpenSSL",
"versions": [
{
"lessThan": "4.1.1",
"status": "affected",
"version": "4.1.0",
"versionType": "semver"
},
{
"lessThan": "4.0.4",
"status": "affected",
"version": "4.0.0",
"versionType": "semver"
},
{
"lessThan": "3.5.10",
"status": "affected",
"version": "3.5.0",
"versionType": "semver"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "Verifying a maliciously crafted CMS or PKCS#7 SignedData message with CRL checking enabled may consume excessive CPU time, growing with the square of the message size."
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T11:43:42.786Z",
"orgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"shortName": "openssl"
},
"references": [
{
"name": "Fix PR #33546",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/pull/33546"
}
],
"x_generator": {
"engine": "cvelib 1.8.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"assignerShortName": "openssl",
"cveId": "CVE-2026-121482",
"datePublished": "2026-11-18T11:43:42.786Z",
"dateReserved": "2026-11-03T13:45:42.894Z",
"dateUpdated": "2026-11-18T11:43:42.786Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-121481 (GCVE-0-2026-121481)
Vulnerability from nvd – Published: 2026-11-18 11:43 – Updated: 2026-11-18 11:43
VLAI
EPSS
VEX
Summary
Calling EVP_EncodeBlock() with an input length close to INT_MAX may overflow the calculation of the encoded output size and write past the end of the caller-supplied output buffer.
Severity
No CVSS data available.
Assigner
References
1 reference
| URL | Tags |
|---|---|
| https://github.com/openssl/openssl/pull/33652 | patch |
Impacted products
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "OpenSSL",
"vendor": "OpenSSL",
"versions": [
{
"lessThan": "4.1.1",
"status": "affected",
"version": "4.1.0",
"versionType": "semver"
},
{
"lessThan": "4.0.4",
"status": "affected",
"version": "4.0.0",
"versionType": "semver"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "Calling EVP_EncodeBlock() with an input length close to INT_MAX may overflow the calculation of the encoded output size and write past the end of the caller-supplied output buffer."
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T11:43:33.634Z",
"orgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"shortName": "openssl"
},
"references": [
{
"name": "Fix PR #33652",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/pull/33652"
}
],
"x_generator": {
"engine": "cvelib 1.8.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"assignerShortName": "openssl",
"cveId": "CVE-2026-121481",
"datePublished": "2026-11-18T11:43:33.634Z",
"dateReserved": "2026-11-03T13:45:42.894Z",
"dateUpdated": "2026-11-18T11:43:33.634Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-107494 (GCVE-0-2026-107494)
Vulnerability from nvd – Published: 2026-11-18 11:43 – Updated: 2026-11-18 11:43
VLAI
EPSS
VEX
Summary
The QUIC stack queues a RETIRE_CONNECTION_ID frame also for retransmitted NEW_CONNECTION_ID frames. This allows a remote malicious QUIC stack to queue an unlimited number of RETIRE_CONNECTION_ID frames.
Severity
No CVSS data available.
Assigner
References
1 reference
| URL | Tags |
|---|---|
| https://github.com/openssl/openssl/pull/33544 | patch |
Impacted products
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "OpenSSL",
"vendor": "OpenSSL",
"versions": [
{
"lessThan": "4.1.1",
"status": "affected",
"version": "4.1.0",
"versionType": "semver"
},
{
"lessThan": "4.0.4",
"status": "affected",
"version": "4.0.0",
"versionType": "semver"
},
{
"lessThan": "3.5.10",
"status": "affected",
"version": "3.5.0",
"versionType": "semver"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "The QUIC stack queues a RETIRE_CONNECTION_ID frame also for retransmitted NEW_CONNECTION_ID frames. This allows a remote malicious QUIC stack to queue an unlimited number of RETIRE_CONNECTION_ID frames."
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T11:43:10.955Z",
"orgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"shortName": "openssl"
},
"references": [
{
"name": "Fix PR #33544",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/pull/33544"
}
],
"x_generator": {
"engine": "cvelib 1.8.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"assignerShortName": "openssl",
"cveId": "CVE-2026-107494",
"datePublished": "2026-11-18T11:43:10.955Z",
"dateReserved": "2026-10-08T08:31:36.278Z",
"dateUpdated": "2026-11-18T11:43:10.955Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-35190 (GCVE-0-2026-35190)
Vulnerability from nvd – Published: 2026-11-17 08:15 – Updated: 2026-11-17 16:52
VLAI
EPSS
VEX
Title
Out-of-Bounds Read in TLS 1.3 Key-Share Processing with Suite B Certificate Flag
Summary
Issue summary: A server configured with the Suite B certificate flag through
SSL_CTX_set_cert_flags() and with TLS 1.3 enabled may read past the end of a
fixed group list when it processes a ClientHello whose supported_groups and
key_share contain no Suite B group.
Impact summary: A remote client can send a ClientHello that makes the server
read past the end of a static array. The values read are never returned to the
client, so no memory is disclosed; on builds with sanitizers or hardened
allocators the read may crash the process, causing Denial of Service.
CWE: CWE-125: Out-of-bounds Read
Description: When the Suite B certificate flag is set, OpenSSL restricts the
accepted groups to P-256 and P-384 by substituting a fixed two-element list
for the configured group list. The tuple machinery used for key-share
selection was not updated for this substitution: tls1_get_group_tuples() still
returns the configured tuples, which by default describe eight groups. The
server-side walk in tls_parse_ctos_key_share() then advances through the
two-element list using those tuple counts without checking the cumulative
offset against the number of groups present.
Only applications that call SSL_CTX_set_cert_flags() with
SSL_CERT_FLAG_SUITEB_128_LOS and leave TLS 1.3 enabled are affected. The
openssl s_server -suiteB_128 option sets an X.509 verification parameter
instead, so the stock command line server is not vulnerable. Default
configurations do not reach this code.
A client that offers only groups outside the Suite B set, such as X25519,
forces every tuple to be walked and the read to run past the array. The bytes
read are compared against client group IDs and never sent back, so no memory
is disclosed. On builds with address sanitizers or hardened allocators the
read can abort the process; in ordinary release builds it reads a few bytes of
adjacent constant data.
FIPS impact: no
The affected code is outside the FIPS module boundary.
Severity
5.3 (Medium)
SSVC
Exploitation: none
Automatable: yes
Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-17 16:51 UTC
CWE
- CWE-125 - Out-of-bounds Read
Assigner
References
4 references
Impacted products
Date Public
2026-11-17 07:01
{
"containers": {
"adp": [
{
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.3,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
"version": "3.1"
}
},
{
"other": {
"content": {
"id": "CVE-2026-35190",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-17T16:51:09.335502Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-17T16:52:00.153Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "OpenSSL",
"vendor": "OpenSSL",
"versions": [
{
"lessThan": "4.1.1",
"status": "affected",
"version": "4.1.0",
"versionType": "semver"
},
{
"lessThan": "4.0.4",
"status": "affected",
"version": "4.0.0",
"versionType": "semver"
},
{
"lessThan": "3.5.10",
"status": "affected",
"version": "3.5.0",
"versionType": "semver"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "Laurent Gaffie (secorizon.com)"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Daniel Kubec"
}
],
"datePublic": "2026-11-17T07:01:24.000Z",
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "Issue summary: A server configured with the Suite B certificate flag through\u003cbr\u003eSSL_CTX_set_cert_flags() and with TLS 1.3 enabled may read past the end of a\u003cbr\u003efixed group list when it processes a ClientHello whose supported_groups and\u003cbr\u003ekey_share contain no Suite B group.\u003cbr\u003e\u003cbr\u003eImpact summary: A remote client can send a ClientHello that makes the server\u003cbr\u003eread past the end of a static array. The values read are never returned to the\u003cbr\u003eclient, so no memory is disclosed; on builds with sanitizers or hardened\u003cbr\u003eallocators the read may crash the process, causing Denial of Service.\u003cbr\u003e\u003cbr\u003eCWE: CWE-125: Out-of-bounds Read\u003cbr\u003e\u003cbr\u003eDescription: When the Suite B certificate flag is set, OpenSSL restricts the\u003cbr\u003eaccepted groups to P-256 and P-384 by substituting a fixed two-element list\u003cbr\u003efor the configured group list. The tuple machinery used for key-share\u003cbr\u003eselection was not updated for this substitution: tls1_get_group_tuples() still\u003cbr\u003ereturns the configured tuples, which by default describe eight groups. The\u003cbr\u003eserver-side walk in tls_parse_ctos_key_share() then advances through the\u003cbr\u003etwo-element list using those tuple counts without checking the cumulative\u003cbr\u003eoffset against the number of groups present.\u003cbr\u003e\u003cbr\u003eOnly applications that call SSL_CTX_set_cert_flags() with\u003cbr\u003eSSL_CERT_FLAG_SUITEB_128_LOS and leave TLS 1.3 enabled are affected. The\u003cbr\u003eopenssl s_server -suiteB_128 option sets an X.509 verification parameter\u003cbr\u003einstead, so the stock command line server is not vulnerable. Default\u003cbr\u003econfigurations do not reach this code.\u003cbr\u003e\u003cbr\u003eA client that offers only groups outside the Suite B set, such as X25519,\u003cbr\u003eforces every tuple to be walked and the read to run past the array. The bytes\u003cbr\u003eread are compared against client group IDs and never sent back, so no memory\u003cbr\u003eis disclosed. On builds with address sanitizers or hardened allocators the\u003cbr\u003eread can abort the process; in ordinary release builds it reads a few bytes of\u003cbr\u003eadjacent constant data.\u003cbr\u003e\u003cbr\u003eFIPS impact: no\u003cbr\u003eThe affected code is outside the FIPS module boundary."
}
],
"value": "Issue summary: A server configured with the Suite B certificate flag through\nSSL_CTX_set_cert_flags() and with TLS 1.3 enabled may read past the end of a\nfixed group list when it processes a ClientHello whose supported_groups and\nkey_share contain no Suite B group.\n\nImpact summary: A remote client can send a ClientHello that makes the server\nread past the end of a static array. The values read are never returned to the\nclient, so no memory is disclosed; on builds with sanitizers or hardened\nallocators the read may crash the process, causing Denial of Service.\n\nCWE: CWE-125: Out-of-bounds Read\n\nDescription: When the Suite B certificate flag is set, OpenSSL restricts the\naccepted groups to P-256 and P-384 by substituting a fixed two-element list\nfor the configured group list. The tuple machinery used for key-share\nselection was not updated for this substitution: tls1_get_group_tuples() still\nreturns the configured tuples, which by default describe eight groups. The\nserver-side walk in tls_parse_ctos_key_share() then advances through the\ntwo-element list using those tuple counts without checking the cumulative\noffset against the number of groups present.\n\nOnly applications that call SSL_CTX_set_cert_flags() with\nSSL_CERT_FLAG_SUITEB_128_LOS and leave TLS 1.3 enabled are affected. The\nopenssl s_server -suiteB_128 option sets an X.509 verification parameter\ninstead, so the stock command line server is not vulnerable. Default\nconfigurations do not reach this code.\n\nA client that offers only groups outside the Suite B set, such as X25519,\nforces every tuple to be walked and the read to run past the array. The bytes\nread are compared against client group IDs and never sent back, so no memory\nis disclosed. On builds with address sanitizers or hardened allocators the\nread can abort the process; in ordinary release builds it reads a few bytes of\nadjacent constant data.\n\nFIPS impact: no\nThe affected code is outside the FIPS module boundary."
}
],
"metrics": [
{
"format": "other",
"other": {
"content": {
"text": "Low"
},
"type": "https://openssl-library.org/policies/general/security-policy/"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-125",
"description": "Out-of-bounds Read",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-17T08:15:01.294Z",
"orgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"shortName": "openssl"
},
"references": [
{
"name": "OpenSSL Advisory",
"tags": [
"vendor-advisory"
],
"url": "https://openssl-library.org/news/secadv/20261117.txt"
},
{
"name": "4.1.1 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/ade64619df04056b3e5fd1c1befe9425a7c80eb6"
},
{
"name": "4.0.4 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/9a812981b927c5714b7c2e5d138618105cea2152"
},
{
"name": "3.5.10 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/9491b0d9cc7950af1f3dc89499bd5433b9cd4f43"
}
],
"source": {
"discovery": "UNKNOWN"
},
"title": "Out-of-Bounds Read in TLS 1.3 Key-Share Processing with Suite B Certificate Flag",
"x_generator": {
"engine": "Vulnogram 0.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"assignerShortName": "openssl",
"cveId": "CVE-2026-35190",
"datePublished": "2026-11-17T08:15:01.294Z",
"dateReserved": "2026-04-01T17:36:26.323Z",
"dateUpdated": "2026-11-17T16:52:00.153Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-124709 (GCVE-0-2026-124709)
Vulnerability from nvd – Published: 2026-11-17 08:14 – Updated: 2026-11-17 16:50
VLAI
EPSS
VEX
Title
Unbounded Memory Retention in QUIC Server for Rejected Streams
Summary
Issue summary: A QUIC server that rejects a stream opened by the peer may
retain that stream's state for the lifetime of the connection if the peer
resets the stream before the rejection is signalled, even though the peer's
stream credit is returned.
Impact summary: A remote client that completes a QUIC handshake can repeatedly
open and reset streams, causing server memory to grow without bound until the
process runs out of memory and every connection on it is lost. This is a
Denial of Service.
CWE: CWE-401: Missing Release of Memory after Effective Lifetime
Description: QUIC servers track each stream the peer opens. When the incoming
stream policy rejects a stream, OpenSSL schedules a STOP_SENDING frame, marks
the stream deleted and returns the peer's stream credit. A deleted stream is
collected only once its receive part is fully drained, which for a rejected
stream means the STOP_SENDING has been acknowledged. If the peer sends
RESET_STREAM first, the reset cancels the pending STOP_SENDING, so it is never
sent or acknowledged and the stream is never collected.
The default configuration reaches this path. Once a connection has a default
stream, meaning the application has read from or written to the connection as
the tutorial server does, the effective incoming stream policy rejects streams
the application does not accept. Applications that set the REJECT policy
explicitly are affected too.
Each retained stream costs about 300 bytes, and the peer's stream credit
window paces how quickly they accumulate. A client that keeps the connection
open and keeps opening and resetting streams grows server memory without
bound. The severity is Low because growth is slow, needs a long-lived
connection, and causes no memory corruption or disclosure.
FIPS impact: no
The affected code is outside the FIPS module boundary.
Severity
7.5 (High)
SSVC
Exploitation: none
Automatable: yes
Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-17 16:50 UTC
CWE
- CWE-401 - Missing Release of Memory after Effective Lifetime
Assigner
References
4 references
Impacted products
Date Public
2026-11-17 07:01
{
"containers": {
"adp": [
{
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
}
},
{
"other": {
"content": {
"id": "CVE-2026-124709",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-17T16:50:13.860911Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-17T16:50:38.539Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "OpenSSL",
"vendor": "OpenSSL",
"versions": [
{
"lessThan": "4.1.1",
"status": "affected",
"version": "4.1.0",
"versionType": "semver"
},
{
"lessThan": "4.0.4",
"status": "affected",
"version": "4.0.0",
"versionType": "semver"
},
{
"lessThan": "3.5.10",
"status": "affected",
"version": "3.5.0",
"versionType": "semver"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "Bhabani Sankar Das"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Bhabani Sankar Das"
}
],
"datePublic": "2026-11-17T07:01:24.000Z",
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "Issue summary: A QUIC server that rejects a stream opened by the peer may\u003cbr\u003eretain that stream\u0027s state for the lifetime of the connection if the peer\u003cbr\u003eresets the stream before the rejection is signalled, even though the peer\u0027s\u003cbr\u003estream credit is returned.\u003cbr\u003e\u003cbr\u003eImpact summary: A remote client that completes a QUIC handshake can repeatedly\u003cbr\u003eopen and reset streams, causing server memory to grow without bound until the\u003cbr\u003eprocess runs out of memory and every connection on it is lost. This is a\u003cbr\u003eDenial of Service.\u003cbr\u003e\u003cbr\u003eCWE: CWE-401: Missing Release of Memory after Effective Lifetime\u003cbr\u003e\u003cbr\u003eDescription: QUIC servers track each stream the peer opens. When the incoming\u003cbr\u003estream policy rejects a stream, OpenSSL schedules a STOP_SENDING frame, marks\u003cbr\u003ethe stream deleted and returns the peer\u0027s stream credit. A deleted stream is\u003cbr\u003ecollected only once its receive part is fully drained, which for a rejected\u003cbr\u003estream means the STOP_SENDING has been acknowledged. If the peer sends\u003cbr\u003eRESET_STREAM first, the reset cancels the pending STOP_SENDING, so it is never\u003cbr\u003esent or acknowledged and the stream is never collected.\u003cbr\u003e\u003cbr\u003eThe default configuration reaches this path. Once a connection has a default\u003cbr\u003estream, meaning the application has read from or written to the connection as\u003cbr\u003ethe tutorial server does, the effective incoming stream policy rejects streams\u003cbr\u003ethe application does not accept. Applications that set the REJECT policy\u003cbr\u003eexplicitly are affected too.\u003cbr\u003e\u003cbr\u003eEach retained stream costs about 300 bytes, and the peer\u0027s stream credit\u003cbr\u003ewindow paces how quickly they accumulate. A client that keeps the connection\u003cbr\u003eopen and keeps opening and resetting streams grows server memory without\u003cbr\u003ebound. The severity is Low because growth is slow, needs a long-lived\u003cbr\u003econnection, and causes no memory corruption or disclosure.\u003cbr\u003e\u003cbr\u003eFIPS impact: no\u003cbr\u003eThe affected code is outside the FIPS module boundary."
}
],
"value": "Issue summary: A QUIC server that rejects a stream opened by the peer may\nretain that stream\u0027s state for the lifetime of the connection if the peer\nresets the stream before the rejection is signalled, even though the peer\u0027s\nstream credit is returned.\n\nImpact summary: A remote client that completes a QUIC handshake can repeatedly\nopen and reset streams, causing server memory to grow without bound until the\nprocess runs out of memory and every connection on it is lost. This is a\nDenial of Service.\n\nCWE: CWE-401: Missing Release of Memory after Effective Lifetime\n\nDescription: QUIC servers track each stream the peer opens. When the incoming\nstream policy rejects a stream, OpenSSL schedules a STOP_SENDING frame, marks\nthe stream deleted and returns the peer\u0027s stream credit. A deleted stream is\ncollected only once its receive part is fully drained, which for a rejected\nstream means the STOP_SENDING has been acknowledged. If the peer sends\nRESET_STREAM first, the reset cancels the pending STOP_SENDING, so it is never\nsent or acknowledged and the stream is never collected.\n\nThe default configuration reaches this path. Once a connection has a default\nstream, meaning the application has read from or written to the connection as\nthe tutorial server does, the effective incoming stream policy rejects streams\nthe application does not accept. Applications that set the REJECT policy\nexplicitly are affected too.\n\nEach retained stream costs about 300 bytes, and the peer\u0027s stream credit\nwindow paces how quickly they accumulate. A client that keeps the connection\nopen and keeps opening and resetting streams grows server memory without\nbound. The severity is Low because growth is slow, needs a long-lived\nconnection, and causes no memory corruption or disclosure.\n\nFIPS impact: no\nThe affected code is outside the FIPS module boundary."
}
],
"metrics": [
{
"format": "other",
"other": {
"content": {
"text": "Low"
},
"type": "https://openssl-library.org/policies/general/security-policy/"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-401",
"description": "Missing Release of Memory after Effective Lifetime",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-17T08:14:35.674Z",
"orgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"shortName": "openssl"
},
"references": [
{
"name": "OpenSSL Advisory",
"tags": [
"vendor-advisory"
],
"url": "https://openssl-library.org/news/secadv/20261117.txt"
},
{
"name": "4.1.1 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/ead311df1037e7994a6d86c7e862d71ad59c52c7"
},
{
"name": "4.0.4 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/22291a6af12f158fbb13bfbd572a33dbdbf290d2"
},
{
"name": "3.5.10 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/f3acb0a3328046741479482c51cec815839e1b05"
}
],
"source": {
"discovery": "UNKNOWN"
},
"title": "Unbounded Memory Retention in QUIC Server for Rejected Streams",
"x_generator": {
"engine": "Vulnogram 0.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"assignerShortName": "openssl",
"cveId": "CVE-2026-124709",
"datePublished": "2026-11-17T08:14:35.674Z",
"dateReserved": "2026-11-09T10:45:57.951Z",
"dateUpdated": "2026-11-17T16:50:38.539Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-107493 (GCVE-0-2026-107493)
Vulnerability from nvd – Published: 2026-11-17 08:14 – Updated: 2026-11-17 16:49
VLAI
EPSS
VEX
Title
Use-After-Free in PEM_X509_INFO_read_bio_ex() when appending to a caller-supplied stack fails
Summary
Issue summary: When an application passes a stack to
PEM_X509_INFO_read_bio_ex() to add entries to, and reading fails,
OpenSSL frees every entry in the stack, both the old ones and any new
ones, but leaves them in the stack.
Impact summary: An application that passes an existing stack to
PEM_X509_INFO_read_bio_ex() and keeps using it after a failed read may
use memory that was already freed. This can cause a crash or, in
principle, memory corruption. Malformed PEM data can make the read fail,
but only applications that pass an existing stack are affected, and
OpenSSL itself does not do this.
CWE: CWE-416: Use After Free
Description: PEM_X509_INFO_read_bio_ex() reads certificates, CRLs and
private keys from PEM data and adds them to a stack of X509_INFO
structures. If the application passes a stack that is not NULL, the
function adds the new entries to it and must leave the entries that are
already there unchanged.
If reading fails, the function frees every entry in the stack. This
includes the entries that were there before the call, and the entries
added by the call. It does not remove these entries from the stack, so
the stack keeps pointers to freed memory. The failure can happen at any
point, even before any entry was added. A PEM item with invalid content
is enough. This also happens if the stack was empty: entries added
before the failure are freed but stay in the stack.
An application that then reads or frees the stack will use memory that
was already freed. This can crash the application or, in principle,
corrupt memory.
Only applications that pass a stack that is not NULL are affected.
OpenSSL itself never does this. Its own callers, including the code that
TLS uses to load CA certificates, always pass NULL. When the stack is
NULL, the function frees only the entries that it created itself, which
is safe. We expect that very few applications pass an existing stack. An
attacker can make the read fail with malformed PEM data, but cannot make
an application pass an existing stack.
The same problem affects PEM_X509_INFO_read_bio(), PEM_X509_INFO_read()
and PEM_X509_INFO_read_ex(), which use the same code. OpenSSL 1.1.1 and
1.0.2 have only the first two of these functions.
FIPS impact: no
The affected code is outside the FIPS module boundary.
Severity
7.7 (High)
SSVC
Exploitation: none
Automatable: no
Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-17 16:47 UTC
CWE
- CWE-416 - Use After Free
Assigner
References
4 references
Impacted products
Date Public
2026-11-17 07:01
{
"containers": {
"adp": [
{
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 7.7,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H",
"version": "3.1"
}
},
{
"other": {
"content": {
"id": "CVE-2026-107493",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-17T16:47:04.388261Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-17T16:49:16.589Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "OpenSSL",
"vendor": "OpenSSL",
"versions": [
{
"lessThan": "4.1.1",
"status": "affected",
"version": "4.1.0",
"versionType": "semver"
},
{
"lessThan": "4.0.4",
"status": "affected",
"version": "4.0.0",
"versionType": "semver"
},
{
"lessThan": "3.5.10",
"status": "affected",
"version": "3.5.0",
"versionType": "semver"
},
{
"lessThan": "3.0.24",
"status": "affected",
"version": "3.0.0",
"versionType": "semver"
},
{
"lessThan": "1.1.1zk",
"status": "affected",
"version": "1.1.1",
"versionType": "custom"
},
{
"lessThan": "1.0.2zt",
"status": "affected",
"version": "1.0.2",
"versionType": "custom"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "Filipe Casal (Trail of Bits)"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Viktor Dukhovni"
}
],
"datePublic": "2026-11-17T07:01:24.000Z",
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "Issue summary: When an application passes a stack to\u003cbr\u003ePEM_X509_INFO_read_bio_ex() to add entries to, and reading fails,\u003cbr\u003eOpenSSL frees every entry in the stack, both the old ones and any new\u003cbr\u003eones, but leaves them in the stack.\u003cbr\u003e\u003cbr\u003eImpact summary: An application that passes an existing stack to\u003cbr\u003ePEM_X509_INFO_read_bio_ex() and keeps using it after a failed read may\u003cbr\u003euse memory that was already freed. This can cause a crash or, in\u003cbr\u003eprinciple, memory corruption. Malformed PEM data can make the read fail,\u003cbr\u003ebut only applications that pass an existing stack are affected, and\u003cbr\u003eOpenSSL itself does not do this.\u003cbr\u003e\u003cbr\u003eCWE: CWE-416: Use After Free\u003cbr\u003e\u003cbr\u003eDescription: PEM_X509_INFO_read_bio_ex() reads certificates, CRLs and\u003cbr\u003eprivate keys from PEM data and adds them to a stack of X509_INFO\u003cbr\u003estructures. If the application passes a stack that is not NULL, the\u003cbr\u003efunction adds the new entries to it and must leave the entries that are\u003cbr\u003ealready there unchanged.\u003cbr\u003e\u003cbr\u003eIf reading fails, the function frees every entry in the stack. This\u003cbr\u003eincludes the entries that were there before the call, and the entries\u003cbr\u003eadded by the call. It does not remove these entries from the stack, so\u003cbr\u003ethe stack keeps pointers to freed memory. The failure can happen at any\u003cbr\u003epoint, even before any entry was added. A PEM item with invalid content\u003cbr\u003eis enough. This also happens if the stack was empty: entries added\u003cbr\u003ebefore the failure are freed but stay in the stack.\u003cbr\u003e\u003cbr\u003eAn application that then reads or frees the stack will use memory that\u003cbr\u003ewas already freed. This can crash the application or, in principle,\u003cbr\u003ecorrupt memory.\u003cbr\u003e\u003cbr\u003eOnly applications that pass a stack that is not NULL are affected.\u003cbr\u003eOpenSSL itself never does this. Its own callers, including the code that\u003cbr\u003eTLS uses to load CA certificates, always pass NULL. When the stack is\u003cbr\u003eNULL, the function frees only the entries that it created itself, which\u003cbr\u003eis safe. We expect that very few applications pass an existing stack. An\u003cbr\u003eattacker can make the read fail with malformed PEM data, but cannot make\u003cbr\u003ean application pass an existing stack.\u003cbr\u003e\u003cbr\u003eThe same problem affects PEM_X509_INFO_read_bio(), PEM_X509_INFO_read()\u003cbr\u003eand PEM_X509_INFO_read_ex(), which use the same code. OpenSSL 1.1.1 and\u003cbr\u003e1.0.2 have only the first two of these functions.\u003cbr\u003e\u003cbr\u003eFIPS impact: no\u003cbr\u003eThe affected code is outside the FIPS module boundary."
}
],
"value": "Issue summary: When an application passes a stack to\nPEM_X509_INFO_read_bio_ex() to add entries to, and reading fails,\nOpenSSL frees every entry in the stack, both the old ones and any new\nones, but leaves them in the stack.\n\nImpact summary: An application that passes an existing stack to\nPEM_X509_INFO_read_bio_ex() and keeps using it after a failed read may\nuse memory that was already freed. This can cause a crash or, in\nprinciple, memory corruption. Malformed PEM data can make the read fail,\nbut only applications that pass an existing stack are affected, and\nOpenSSL itself does not do this.\n\nCWE: CWE-416: Use After Free\n\nDescription: PEM_X509_INFO_read_bio_ex() reads certificates, CRLs and\nprivate keys from PEM data and adds them to a stack of X509_INFO\nstructures. If the application passes a stack that is not NULL, the\nfunction adds the new entries to it and must leave the entries that are\nalready there unchanged.\n\nIf reading fails, the function frees every entry in the stack. This\nincludes the entries that were there before the call, and the entries\nadded by the call. It does not remove these entries from the stack, so\nthe stack keeps pointers to freed memory. The failure can happen at any\npoint, even before any entry was added. A PEM item with invalid content\nis enough. This also happens if the stack was empty: entries added\nbefore the failure are freed but stay in the stack.\n\nAn application that then reads or frees the stack will use memory that\nwas already freed. This can crash the application or, in principle,\ncorrupt memory.\n\nOnly applications that pass a stack that is not NULL are affected.\nOpenSSL itself never does this. Its own callers, including the code that\nTLS uses to load CA certificates, always pass NULL. When the stack is\nNULL, the function frees only the entries that it created itself, which\nis safe. We expect that very few applications pass an existing stack. An\nattacker can make the read fail with malformed PEM data, but cannot make\nan application pass an existing stack.\n\nThe same problem affects PEM_X509_INFO_read_bio(), PEM_X509_INFO_read()\nand PEM_X509_INFO_read_ex(), which use the same code. OpenSSL 1.1.1 and\n1.0.2 have only the first two of these functions.\n\nFIPS impact: no\nThe affected code is outside the FIPS module boundary."
}
],
"metrics": [
{
"format": "other",
"other": {
"content": {
"text": "Low"
},
"type": "https://openssl-library.org/policies/general/security-policy/"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-416",
"description": "Use After Free",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-17T08:14:08.947Z",
"orgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"shortName": "openssl"
},
"references": [
{
"name": "OpenSSL Advisory",
"tags": [
"vendor-advisory"
],
"url": "https://openssl-library.org/news/secadv/20261117.txt"
},
{
"name": "4.1.1 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/c57a5ccf0c060755b5494a6870922b7c6cdd7dd8"
},
{
"name": "4.0.4 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/0486dfadfec558e1808f59d35a8d79e541c4e7d7"
},
{
"name": "3.5.10 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/c8f6d04f8e6d40b1bf83334e4a2ec9daf5943a3d"
}
],
"source": {
"discovery": "UNKNOWN"
},
"title": "Use-After-Free in PEM_X509_INFO_read_bio_ex() when appending to a caller-supplied stack fails",
"x_generator": {
"engine": "Vulnogram 0.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"assignerShortName": "openssl",
"cveId": "CVE-2026-107493",
"datePublished": "2026-11-17T08:14:08.947Z",
"dateReserved": "2026-10-08T08:31:36.278Z",
"dateUpdated": "2026-11-17T16:49:16.589Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-95692 (GCVE-0-2026-95692)
Vulnerability from nvd – Published: 2026-11-10 18:16 – Updated: 2026-11-16 19:08
VLAI
EPSS
VEX
Title
Out-of-Bounds Read and Incorrect IV Length Handling in AES-GCM-SIV
Summary
Issue summary: Setting an AES-GCM-SIV IV shorter than the expected nonce
length via EVP_CipherInit_ex() may trigger a heap out-of-bounds read.
Supplying a longer IV is silently truncated instead of rejected.
Impact summary: An application passing a caller-supplied IV of the wrong
length may crash or read beyond its buffer. Because trailing IV bytes are
ignored, an attacker who knows one message and tag may forge messages under a
different IV.
CWE: CWE-125: Out-of-bounds Read
Description: AES-GCM-SIV copies the caller-supplied IV or nonce into its
internal state using a copy whose length is taken from the expected nonce size
rather than from the length the caller actually provided. When the caller
passes a shorter IV, the copy reads past the end of the caller's buffer;
AddressSanitizer confirms a heap out-of-bounds read reached through
EVP_CipherInit_ex() into ossl_aes_gcm_siv_init(). When the caller passes a
longer IV, the implementation silently discards the trailing bytes instead of
rejecting the length.
The truncation breaks the binding between the IV and the computed
authentication tag. An attacker who has observed a message and its tag under
one IV can produce a message and tag that verify under a different IV whose
first bytes match, since the surplus bytes never influence the computation.
The message itself is unchanged, so this is a failure of IV commitment rather
than a classic existential forgery.
Only applications that call EVP_CipherInit_ex() (or the equivalent provider
cipher initialization) with an IV length other than the standard 12 bytes for
AES-GCM-SIV are affected. The severity is limited because the out-of-bounds
read is small and attacker-controlled only in length, and the forgery requires
an unusual IV length choice by the application.
FIPS impact: no
The FIPS modules are not affected by this issue, as AES-GCM-SIV is not an
approved algorithm.
Severity
7.5 (High)
SSVC
Exploitation: none
Automatable: yes
Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-16 19:08 UTC
CWE
- CWE-125 - Out-of-bounds Read
Assigner
References
4 references
Impacted products
Date Public
2026-11-10 11:00
{
"containers": {
"adp": [
{
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"version": "3.1"
}
},
{
"other": {
"content": {
"id": "CVE-2026-95692",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-16T19:08:03.379147Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-16T19:08:40.459Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "OpenSSL",
"vendor": "OpenSSL",
"versions": [
{
"lessThan": "4.1.1",
"status": "affected",
"version": "4.1.0",
"versionType": "semver"
},
{
"lessThan": "4.0.4",
"status": "affected",
"version": "4.0.0",
"versionType": "semver"
},
{
"lessThan": "3.5.10",
"status": "affected",
"version": "3.5.0",
"versionType": "semver"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "Billy Brumley (Rochester Institute of Technology)"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Billy Brumley (Rochester Institute of Technology)"
}
],
"datePublic": "2026-11-10T11:00:00.000Z",
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "Issue summary: Setting an AES-GCM-SIV IV shorter than the expected nonce\u003cbr\u003elength via EVP_CipherInit_ex() may trigger a heap out-of-bounds read.\u003cbr\u003eSupplying a longer IV is silently truncated instead of rejected.\u003cbr\u003e\u003cbr\u003eImpact summary: An application passing a caller-supplied IV of the wrong\u003cbr\u003elength may crash or read beyond its buffer. Because trailing IV bytes are\u003cbr\u003eignored, an attacker who knows one message and tag may forge messages under a\u003cbr\u003edifferent IV.\u003cbr\u003e\u003cbr\u003eCWE: CWE-125: Out-of-bounds Read\u003cbr\u003e\u003cbr\u003eDescription: AES-GCM-SIV copies the caller-supplied IV or nonce into its\u003cbr\u003einternal state using a copy whose length is taken from the expected nonce size\u003cbr\u003erather than from the length the caller actually provided. When the caller\u003cbr\u003epasses a shorter IV, the copy reads past the end of the caller\u0027s buffer;\u003cbr\u003eAddressSanitizer confirms a heap out-of-bounds read reached through\u003cbr\u003eEVP_CipherInit_ex() into ossl_aes_gcm_siv_init(). When the caller passes a\u003cbr\u003elonger IV, the implementation silently discards the trailing bytes instead of\u003cbr\u003erejecting the length.\u003cbr\u003e\u003cbr\u003eThe truncation breaks the binding between the IV and the computed\u003cbr\u003eauthentication tag. An attacker who has observed a message and its tag under\u003cbr\u003eone IV can produce a message and tag that verify under a different IV whose\u003cbr\u003efirst bytes match, since the surplus bytes never influence the computation.\u003cbr\u003eThe message itself is unchanged, so this is a failure of IV commitment rather\u003cbr\u003ethan a classic existential forgery.\u003cbr\u003e\u003cbr\u003eOnly applications that call EVP_CipherInit_ex() (or the equivalent provider\u003cbr\u003ecipher initialization) with an IV length other than the standard 12 bytes for\u003cbr\u003eAES-GCM-SIV are affected. The severity is limited because the out-of-bounds\u003cbr\u003eread is small and attacker-controlled only in length, and the forgery requires\u003cbr\u003ean unusual IV length choice by the application.\u003cbr\u003e\u003cbr\u003eFIPS impact: no\u003cbr\u003eThe FIPS modules are not affected by this issue, as AES-GCM-SIV is not an\u003cbr\u003eapproved algorithm."
}
],
"value": "Issue summary: Setting an AES-GCM-SIV IV shorter than the expected nonce\nlength via EVP_CipherInit_ex() may trigger a heap out-of-bounds read.\nSupplying a longer IV is silently truncated instead of rejected.\n\nImpact summary: An application passing a caller-supplied IV of the wrong\nlength may crash or read beyond its buffer. Because trailing IV bytes are\nignored, an attacker who knows one message and tag may forge messages under a\ndifferent IV.\n\nCWE: CWE-125: Out-of-bounds Read\n\nDescription: AES-GCM-SIV copies the caller-supplied IV or nonce into its\ninternal state using a copy whose length is taken from the expected nonce size\nrather than from the length the caller actually provided. When the caller\npasses a shorter IV, the copy reads past the end of the caller\u0027s buffer;\nAddressSanitizer confirms a heap out-of-bounds read reached through\nEVP_CipherInit_ex() into ossl_aes_gcm_siv_init(). When the caller passes a\nlonger IV, the implementation silently discards the trailing bytes instead of\nrejecting the length.\n\nThe truncation breaks the binding between the IV and the computed\nauthentication tag. An attacker who has observed a message and its tag under\none IV can produce a message and tag that verify under a different IV whose\nfirst bytes match, since the surplus bytes never influence the computation.\nThe message itself is unchanged, so this is a failure of IV commitment rather\nthan a classic existential forgery.\n\nOnly applications that call EVP_CipherInit_ex() (or the equivalent provider\ncipher initialization) with an IV length other than the standard 12 bytes for\nAES-GCM-SIV are affected. The severity is limited because the out-of-bounds\nread is small and attacker-controlled only in length, and the forgery requires\nan unusual IV length choice by the application.\n\nFIPS impact: no\nThe FIPS modules are not affected by this issue, as AES-GCM-SIV is not an\napproved algorithm."
}
],
"metrics": [
{
"format": "other",
"other": {
"content": {
"text": "Low"
},
"type": "https://openssl-library.org/policies/general/security-policy/"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-125",
"description": "CWE-125 Out-of-bounds Read",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-10T18:16:18.675Z",
"orgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"shortName": "openssl"
},
"references": [
{
"name": "OpenSSL Advisory",
"tags": [
"vendor-advisory"
],
"url": "https://openssl-library.org/news/secadv/20261110.txt"
},
{
"name": "4.1.1 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/70a47ac78b6f3be1b22fb1551bd0bfcff4f29613"
},
{
"name": "4.0.4 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/510872388f5d145cf870868b3d288a23822cb776"
},
{
"name": "3.5.10 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/257a3427aa0ef8d9dd2ef5b3e2d1c021a221b116"
}
],
"source": {
"discovery": "UNKNOWN"
},
"title": "Out-of-Bounds Read and Incorrect IV Length Handling in AES-GCM-SIV",
"x_generator": {
"engine": "Vulnogram 0.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"assignerShortName": "openssl",
"cveId": "CVE-2026-95692",
"datePublished": "2026-11-10T18:16:18.675Z",
"dateReserved": "2026-09-22T14:18:48.635Z",
"dateUpdated": "2026-11-16T19:08:40.459Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-95691 (GCVE-0-2026-95691)
Vulnerability from nvd – Published: 2026-11-10 18:16 – Updated: 2026-11-16 19:17
VLAI
EPSS
VEX
Title
Retransmitted QUIC CRYPTO Frames Can Cause DoS or One-byte Disclosure
Summary
Issue summary: A retransmitted QUIC CRYPTO frame can release packet storage
while the TLS record layer retains a direct pointer into that storage causing
use after free.
Impact summary: A malicious QUIC server can cause a heap-use-after-free read
in the OpenSSL QUIC client. The server can also identify one allocator-adjacent
byte through the client's protected Handshake response.
CWE: CWE-416: Use After Free
Description: During CRYPTO stream processing, a pointer into the first frame's
memory on the stream is lent to the TLS handshake processing. The memory
must remain stable until it is processed and released. However the processing
of retransmitted CRYPTO frames could release the memory if the retransmitted
frame fully overlapped the existing frame. This then causes use-after-free read
when the TLS handshake processing continues.
The use-after-free read can lead to a Denial-of-Service of the client
application or a minor leak of information about the heap memory contents
that might be overwritten with other data, subsequently allocated by
the application, to the peer.
FIPS impact: no
The FIPS module is not affected as the QUIC implementation is outside of
the OpenSSL FIPS module boundary.
Severity
8.1 (High)
SSVC
Exploitation: none
Automatable: no
Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-16 19:15 UTC
CWE
- CWE-416 - Use After Free
Assigner
References
4 references
Impacted products
Date Public
2026-11-10 11:00
{
"containers": {
"adp": [
{
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "ADJACENT_NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 8.1,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H",
"version": "3.1"
}
},
{
"other": {
"content": {
"id": "CVE-2026-95691",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-16T19:15:55.510879Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-16T19:17:17.580Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "OpenSSL",
"vendor": "OpenSSL",
"versions": [
{
"lessThan": "4.1.1",
"status": "affected",
"version": "4.1.0",
"versionType": "semver"
},
{
"lessThan": "4.0.4",
"status": "affected",
"version": "4.0.0",
"versionType": "semver"
},
{
"lessThan": "3.5.10",
"status": "affected",
"version": "3.5.0",
"versionType": "semver"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "Filipe Casal (Trail of Bits)"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Filipe Casal (Trail of Bits)"
}
],
"datePublic": "2026-11-10T11:00:00.000Z",
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "Issue summary: A retransmitted QUIC CRYPTO frame can release packet storage\u003cbr\u003ewhile the TLS record layer retains a direct pointer into that storage causing\u003cbr\u003euse after free.\u003cbr\u003e\u003cbr\u003eImpact summary: A malicious QUIC server can cause a heap-use-after-free read\u003cbr\u003ein the OpenSSL QUIC client. The server can also identify one allocator-adjacent\u003cbr\u003ebyte through the client\u0027s protected Handshake response.\u003cbr\u003e\u003cbr\u003eCWE: CWE-416: Use After Free\u003cbr\u003e\u003cbr\u003eDescription: During CRYPTO stream processing, a pointer into the first frame\u0027s\u003cbr\u003ememory on the stream is lent to the TLS handshake processing. The memory\u003cbr\u003emust remain stable until it is processed and released. However the processing\u003cbr\u003eof retransmitted CRYPTO frames could release the memory if the retransmitted\u003cbr\u003eframe fully overlapped the existing frame. This then causes use-after-free read\u003cbr\u003ewhen the TLS handshake processing continues.\u003cbr\u003e\u003cbr\u003eThe use-after-free read can lead to a Denial-of-Service of the client\u003cbr\u003eapplication or a minor leak of information about the heap memory contents\u003cbr\u003ethat might be overwritten with other data, subsequently allocated by\u003cbr\u003ethe application, to the peer.\u003cbr\u003e\u003cbr\u003eFIPS impact: no\u003cbr\u003eThe FIPS module is not affected as the QUIC implementation is outside of\u003cbr\u003ethe OpenSSL FIPS module boundary."
}
],
"value": "Issue summary: A retransmitted QUIC CRYPTO frame can release packet storage\nwhile the TLS record layer retains a direct pointer into that storage causing\nuse after free.\n\nImpact summary: A malicious QUIC server can cause a heap-use-after-free read\nin the OpenSSL QUIC client. The server can also identify one allocator-adjacent\nbyte through the client\u0027s protected Handshake response.\n\nCWE: CWE-416: Use After Free\n\nDescription: During CRYPTO stream processing, a pointer into the first frame\u0027s\nmemory on the stream is lent to the TLS handshake processing. The memory\nmust remain stable until it is processed and released. However the processing\nof retransmitted CRYPTO frames could release the memory if the retransmitted\nframe fully overlapped the existing frame. This then causes use-after-free read\nwhen the TLS handshake processing continues.\n\nThe use-after-free read can lead to a Denial-of-Service of the client\napplication or a minor leak of information about the heap memory contents\nthat might be overwritten with other data, subsequently allocated by\nthe application, to the peer.\n\nFIPS impact: no\nThe FIPS module is not affected as the QUIC implementation is outside of\nthe OpenSSL FIPS module boundary."
}
],
"metrics": [
{
"format": "other",
"other": {
"content": {
"text": "Low"
},
"type": "https://openssl-library.org/policies/general/security-policy/"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-416",
"description": "CWE-416 Use After Free",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-10T18:16:03.752Z",
"orgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"shortName": "openssl"
},
"references": [
{
"name": "OpenSSL Advisory",
"tags": [
"vendor-advisory"
],
"url": "https://openssl-library.org/news/secadv/20261110.txt"
},
{
"name": "4.1.1 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/dd90ceb99a3c2ddba336bb4a00be9ebabd84c2a1"
},
{
"name": "4.0.4 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/ec9d4de9d03989b29db5a3d7efdb4c285deaf386"
},
{
"name": "3.5.10 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/f6244675833e097c2429a40d1b206d95385bd42f"
}
],
"source": {
"discovery": "UNKNOWN"
},
"title": "Retransmitted QUIC CRYPTO Frames Can Cause DoS or One-byte Disclosure",
"x_generator": {
"engine": "Vulnogram 0.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"assignerShortName": "openssl",
"cveId": "CVE-2026-95691",
"datePublished": "2026-11-10T18:16:03.752Z",
"dateReserved": "2026-09-22T14:18:48.635Z",
"dateUpdated": "2026-11-16T19:17:17.580Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-88823 (GCVE-0-2026-88823)
Vulnerability from nvd – Published: 2026-11-10 18:15 – Updated: 2026-11-16 19:14
VLAI
EPSS
VEX
Title
AES-GCM-SIV AAD Forgery After Zero-length Incremental AAD Update
Summary
Issue summary: The AES-GCM-SIV implementation treats a zero-length Additional
Authenticated Data (AAD) update as a reset of all the AAD supplied so far,
instead of leaving the AAD unchanged. An application that supplies its AAD in
several fragments, one of which is empty, therefore produces or verifies
messages whose authentication tag does not cover the AAD supplied before
the empty fragment.
Impact summary: Data an application intended to authenticate alongside a
message is silently left unauthenticated. An attacker can forge the AAD of such
a message.
CWE: CWE-325: Missing Cryptographic Step
Description: An application passing AAD in multiple chunks of which some have
zero length will have the previous AAD chunks effectively unauthenticated. Also,
on context re-initialisation, the AAD was not reset, which meant that any AAD
accumulated from the previous context usage were also included in the AAD of the
new message.
The fix makes a zero-length AAD update a no-op and clears any accumulated AAD
whenever the context is re-initialised with a key or a nonce.
A re-initialisation that only changes parameters keeps the AAD.
FIPS impact: no
The FIPS modules are not affected, as AES-GCM-SIV is not a FIPS approved
algorithm and is implemented only in the default provider, outside the
OpenSSL FIPS module boundary.
Severity
7.5 (High)
SSVC
Exploitation: none
Automatable: yes
Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-16 19:14 UTC
CWE
- CWE-325 - Missing Cryptographic Step
Assigner
References
4 references
Impacted products
Date Public
2026-11-10 11:05
{
"containers": {
"adp": [
{
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
"version": "3.1"
}
},
{
"other": {
"content": {
"id": "CVE-2026-88823",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-16T19:14:15.207846Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-16T19:14:47.256Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "OpenSSL",
"vendor": "OpenSSL",
"versions": [
{
"lessThan": "4.1.1",
"status": "affected",
"version": "4.1.0",
"versionType": "semver"
},
{
"lessThan": "4.0.4",
"status": "affected",
"version": "4.0.0",
"versionType": "semver"
},
{
"lessThan": "3.5.10",
"status": "affected",
"version": "3.5.0",
"versionType": "semver"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "J\u00e9r\u00e9my Jean (ANSSI)"
},
{
"lang": "en",
"type": "reporter",
"value": "Bhargava Shastry"
},
{
"lang": "en",
"type": "reporter",
"value": "Jonathan Bateman (Rochester Institute of Technology)"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Daniel Kubec"
}
],
"datePublic": "2026-11-10T11:05:35.000Z",
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "Issue summary: The AES-GCM-SIV implementation treats a zero-length Additional\u003cbr\u003eAuthenticated Data (AAD) update as a reset of all the AAD supplied so far,\u003cbr\u003einstead of leaving the AAD unchanged. An application that supplies its AAD in\u003cbr\u003eseveral fragments, one of which is empty, therefore produces or verifies\u003cbr\u003emessages whose authentication tag does not cover the AAD supplied before\u003cbr\u003ethe empty fragment.\u003cbr\u003e\u003cbr\u003eImpact summary: Data an application intended to authenticate alongside a\u003cbr\u003emessage is silently left unauthenticated. An attacker can forge the AAD of such\u003cbr\u003ea message.\u003cbr\u003e\u003cbr\u003eCWE: CWE-325: Missing Cryptographic Step\u003cbr\u003e\u003cbr\u003eDescription: An application passing AAD in multiple chunks of which some have\u003cbr\u003ezero length will have the previous AAD chunks effectively unauthenticated. Also,\u003cbr\u003eon context re-initialisation, the AAD was not reset, which meant that any AAD\u003cbr\u003eaccumulated from the previous context usage were also included in the AAD of the\u003cbr\u003enew message.\u003cbr\u003e\u003cbr\u003eThe fix makes a zero-length AAD update a no-op and clears any accumulated AAD\u003cbr\u003ewhenever the context is re-initialised with a key or a nonce.\u003cbr\u003eA re-initialisation that only changes parameters keeps the AAD.\u003cbr\u003e\u003cbr\u003eFIPS impact: no\u003cbr\u003eThe FIPS modules are not affected, as AES-GCM-SIV is not a FIPS approved\u003cbr\u003ealgorithm and is implemented only in the default provider, outside the\u003cbr\u003eOpenSSL FIPS module boundary."
}
],
"value": "Issue summary: The AES-GCM-SIV implementation treats a zero-length Additional\nAuthenticated Data (AAD) update as a reset of all the AAD supplied so far,\ninstead of leaving the AAD unchanged. An application that supplies its AAD in\nseveral fragments, one of which is empty, therefore produces or verifies\nmessages whose authentication tag does not cover the AAD supplied before\nthe empty fragment.\n\nImpact summary: Data an application intended to authenticate alongside a\nmessage is silently left unauthenticated. An attacker can forge the AAD of such\na message.\n\nCWE: CWE-325: Missing Cryptographic Step\n\nDescription: An application passing AAD in multiple chunks of which some have\nzero length will have the previous AAD chunks effectively unauthenticated. Also,\non context re-initialisation, the AAD was not reset, which meant that any AAD\naccumulated from the previous context usage were also included in the AAD of the\nnew message.\n\nThe fix makes a zero-length AAD update a no-op and clears any accumulated AAD\nwhenever the context is re-initialised with a key or a nonce.\nA re-initialisation that only changes parameters keeps the AAD.\n\nFIPS impact: no\nThe FIPS modules are not affected, as AES-GCM-SIV is not a FIPS approved\nalgorithm and is implemented only in the default provider, outside the\nOpenSSL FIPS module boundary."
}
],
"metrics": [
{
"format": "other",
"other": {
"content": {
"text": "Low"
},
"type": "https://openssl-library.org/policies/general/security-policy/"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-325",
"description": "CWE-325 Missing Cryptographic Step",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-10T18:15:49.358Z",
"orgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"shortName": "openssl"
},
"references": [
{
"name": "OpenSSL Advisory",
"tags": [
"vendor-advisory"
],
"url": "https://openssl-library.org/news/secadv/20261110.txt"
},
{
"name": "4.1.1 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/6747b1a278816dd7db46438040a70b0b5e5e0a90"
},
{
"name": "4.0.4 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/2f5fc833ff9b5bfe00b32f8b5c74f73c5773c682"
},
{
"name": "3.5.10 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/159e1de0c448d7b9f09ad768c8e141def4aa1eb4"
}
],
"source": {
"discovery": "UNKNOWN"
},
"title": "AES-GCM-SIV AAD Forgery After Zero-length Incremental AAD Update",
"x_generator": {
"engine": "Vulnogram 0.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"assignerShortName": "openssl",
"cveId": "CVE-2026-88823",
"datePublished": "2026-11-10T18:15:49.358Z",
"dateReserved": "2026-09-10T09:08:26.966Z",
"dateUpdated": "2026-11-16T19:14:47.256Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-88822 (GCVE-0-2026-88822)
Vulnerability from nvd – Published: 2026-11-10 18:15 – Updated: 2026-11-16 19:13
VLAI
EPSS
VEX
Title
QUIC Uses Uninitialized Stack Bytes During Automated Peer Detection
Summary
Issue summary: QUIC, when performing automated peer detection, may allow
uninitialized stack data to leak into the received address which is then used
as the destination for outgoing packets.
Impact summary: Applications using QUIC's automated peer detection mechanism
may receive an invalid address, leading to connection loss and disclosure of
uninitialized stack data to an attacker observing the outgoing network traffic.
CWE: CWE-457 (Use of Uninitialized Variable)
Description: The OpenSSL QUIC stack contains a feature in which, when using an
already connected socket, it will auto-detect the peer address during the SSL
handshake. This feature uses the getpeername() function, passing a buffer of
sufficient length to hold any supported address family, but passes a buffer
length that is only sized such that larger addresses, such as IPv6, cannot be
retrieved. The getpeername() function however, still returns the full address
length, which is accepted as the valid input buffer length, leading to the
address buffer containing uninitialized stack data instead of the actual peer
address. The invalid peer address is then used as destination for the outgoing
packets which leads to a connectivity breakage and a leakage of the
uninitialized stack data to passive network observers.
FIPS impact: no
The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this CVE as
the affected protocol is not implemented in the FIPS module.
Severity
6.5 (Medium)
SSVC
Exploitation: none
Automatable: no
Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-16 19:12 UTC
CWE
- CWE-457 - Use of Uninitialized Variable
Assigner
References
4 references
Impacted products
Date Public
2026-11-10 11:00
{
"containers": {
"adp": [
{
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "ADJACENT_NETWORK",
"availabilityImpact": "NONE",
"baseScore": 6.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "HIGH",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"version": "3.1"
}
},
{
"other": {
"content": {
"id": "CVE-2026-88822",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-16T19:12:36.825108Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-16T19:13:15.341Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "OpenSSL",
"vendor": "OpenSSL",
"versions": [
{
"lessThan": "4.1.1",
"status": "affected",
"version": "4.1.0",
"versionType": "semver"
},
{
"lessThan": "4.0.4",
"status": "affected",
"version": "4.0.0",
"versionType": "semver"
},
{
"lessThan": "3.5.10",
"status": "affected",
"version": "3.5.0",
"versionType": "semver"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "Jaehun Lee"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Neil Horman"
}
],
"datePublic": "2026-11-10T11:00:00.000Z",
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "Issue summary: QUIC, when performing automated peer detection, may allow\u003cbr\u003euninitialized stack data to leak into the received address which is then used\u003cbr\u003eas the destination for outgoing packets.\u003cbr\u003e\u003cbr\u003eImpact summary: Applications using QUIC\u0027s automated peer detection mechanism\u003cbr\u003emay receive an invalid address, leading to connection loss and disclosure of\u003cbr\u003euninitialized stack data to an attacker observing the outgoing network traffic.\u003cbr\u003e\u003cbr\u003eCWE: CWE-457 (Use of Uninitialized Variable)\u003cbr\u003e\u003cbr\u003eDescription: The OpenSSL QUIC stack contains a feature in which, when using an\u003cbr\u003ealready connected socket, it will auto-detect the peer address during the SSL\u003cbr\u003ehandshake. This feature uses the getpeername() function, passing a buffer of\u003cbr\u003esufficient length to hold any supported address family, but passes a buffer\u003cbr\u003elength that is only sized such that larger addresses, such as IPv6, cannot be\u003cbr\u003eretrieved. The getpeername() function however, still returns the full address\u003cbr\u003elength, which is accepted as the valid input buffer length, leading to the\u003cbr\u003eaddress buffer containing uninitialized stack data instead of the actual peer\u003cbr\u003eaddress. The invalid peer address is then used as destination for the outgoing\u003cbr\u003epackets which leads to a connectivity breakage and a leakage of the\u003cbr\u003euninitialized stack data to passive network observers.\u003cbr\u003e\u003cbr\u003eFIPS impact: no\u003cbr\u003eThe FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this CVE as\u003cbr\u003ethe affected protocol is not implemented in the FIPS module."
}
],
"value": "Issue summary: QUIC, when performing automated peer detection, may allow\nuninitialized stack data to leak into the received address which is then used\nas the destination for outgoing packets.\n\nImpact summary: Applications using QUIC\u0027s automated peer detection mechanism\nmay receive an invalid address, leading to connection loss and disclosure of\nuninitialized stack data to an attacker observing the outgoing network traffic.\n\nCWE: CWE-457 (Use of Uninitialized Variable)\n\nDescription: The OpenSSL QUIC stack contains a feature in which, when using an\nalready connected socket, it will auto-detect the peer address during the SSL\nhandshake. This feature uses the getpeername() function, passing a buffer of\nsufficient length to hold any supported address family, but passes a buffer\nlength that is only sized such that larger addresses, such as IPv6, cannot be\nretrieved. The getpeername() function however, still returns the full address\nlength, which is accepted as the valid input buffer length, leading to the\naddress buffer containing uninitialized stack data instead of the actual peer\naddress. The invalid peer address is then used as destination for the outgoing\npackets which leads to a connectivity breakage and a leakage of the\nuninitialized stack data to passive network observers.\n\nFIPS impact: no\nThe FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this CVE as\nthe affected protocol is not implemented in the FIPS module."
}
],
"metrics": [
{
"format": "other",
"other": {
"content": {
"text": "Low"
},
"type": "https://openssl-library.org/policies/general/security-policy/"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-457",
"description": "Use of Uninitialized Variable",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-10T18:15:38.961Z",
"orgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"shortName": "openssl"
},
"references": [
{
"name": "OpenSSL Advisory",
"tags": [
"vendor-advisory"
],
"url": "https://openssl-library.org/news/secadv/20261110.txt"
},
{
"name": "4.1.1 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/7b4f5344aa0401e7b777640050b5257ed2a70e88"
},
{
"name": "4.0.4 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/911eee8eb7550b95a206f1ad8cbdb986098982f3"
},
{
"name": "3.5.10 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/1a73dc590cbad62d6f0329ea4779eadaa8d8fd75"
}
],
"source": {
"discovery": "UNKNOWN"
},
"title": "QUIC Uses Uninitialized Stack Bytes During Automated Peer Detection",
"x_generator": {
"engine": "Vulnogram 0.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"assignerShortName": "openssl",
"cveId": "CVE-2026-88822",
"datePublished": "2026-11-10T18:15:38.961Z",
"dateReserved": "2026-09-10T09:08:26.966Z",
"dateUpdated": "2026-11-16T19:13:15.341Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-107496 (GCVE-0-2026-107496)
Vulnerability from nvd – Published: 2026-11-10 18:14 – Updated: 2026-11-16 19:11
VLAI
EPSS
VEX
Title
Infinite Loop in CMS_encrypt() With an EC Group Order of 1
Summary
Issue summary: Encrypting a CMS message to an EC certificate whose group order
is 1 may cause CMS_encrypt() or CMS_encrypt_ex() to loop indefinitely.
Impact summary: An attacker able to supply the recipient certificate to an
application performing CMS encryption can cause that application to loop
indefinitely, consuming CPU and resulting in Denial of Service.
CWE: CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop')
Description: CMS_encrypt() and CMS_encrypt_ex() encrypt a message to one or
more recipient certificates and, for an EC recipient, generate an ephemeral
key in the recipient's group. If the certificate declares a group order of 1,
random scalar generation can only produce zero. The key generation routine
then retries without limit while waiting for a nonzero private scalar, so the
call never returns.
The OpenSSL TLS and QUIC implementations do not use this path. An application
is exposed only if it calls CMS_encrypt() or CMS_encrypt_ex() with a recipient
certificate whose EC parameters are attacker-controlled. Certificates with
normal EC group orders do not trigger the loop.
OpenSSL 4.0 and later reject unknown explicit EC groups in default builds.
These versions are affected only when configured with the
enable-ec_explicit_curves option.
The result is a hang that consumes a CPU core until the process is
interrupted, a Denial of Service. The severity is Low because the attacker
must supply the recipient certificate and the application must choose to
encrypt to it; ordinary CMS encryption to trusted recipients is unaffected.
The fix makes EC key generation fail when the group has no valid nonzero
private scalar, instead of retrying indefinitely.
FIPS impact: no
The FIPS modules in 4.1, 4.0, 3.5 and 3.0 are not affected. The FIPS provider
does not support arbitrary explicit EC domain parameters, so an order-1 group
is rejected during key import before the vulnerable key generation path is
reached.
Severity
7.5 (High)
SSVC
Exploitation: none
Automatable: yes
Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-16 19:10 UTC
CWE
- CWE-835 - Loop with Unreachable Exit Condition ('Infinite Loop')
Assigner
References
4 references
Impacted products
Date Public
2026-11-10 11:00
{
"containers": {
"adp": [
{
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
}
},
{
"other": {
"content": {
"id": "CVE-2026-107496",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-16T19:10:30.589109Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-16T19:11:29.337Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "OpenSSL",
"vendor": "OpenSSL",
"versions": [
{
"lessThan": "4.1.1",
"status": "affected",
"version": "4.1.0",
"versionType": "semver"
},
{
"lessThan": "4.0.4",
"status": "affected",
"version": "4.0.0",
"versionType": "semver"
},
{
"lessThan": "3.5.10",
"status": "affected",
"version": "3.5.0",
"versionType": "semver"
},
{
"lessThan": "3.0.24",
"status": "affected",
"version": "3.0.0",
"versionType": "semver"
},
{
"lessThan": "1.1.1zk",
"status": "affected",
"version": "1.1.1",
"versionType": "custom"
},
{
"lessThan": "1.0.2zt",
"status": "affected",
"version": "1.0.2",
"versionType": "custom"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "Yinxi Liu"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Jakub Zelenka"
}
],
"datePublic": "2026-11-10T11:00:00.000Z",
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "Issue summary: Encrypting a CMS message to an EC certificate whose group order\u003cbr\u003eis 1 may cause CMS_encrypt() or CMS_encrypt_ex() to loop indefinitely.\u003cbr\u003e\u003cbr\u003eImpact summary: An attacker able to supply the recipient certificate to an\u003cbr\u003eapplication performing CMS encryption can cause that application to loop\u003cbr\u003eindefinitely, consuming CPU and resulting in Denial of Service.\u003cbr\u003e\u003cbr\u003eCWE: CWE-835: Loop with Unreachable Exit Condition (\u0027Infinite Loop\u0027)\u003cbr\u003e\u003cbr\u003eDescription: CMS_encrypt() and CMS_encrypt_ex() encrypt a message to one or\u003cbr\u003emore recipient certificates and, for an EC recipient, generate an ephemeral\u003cbr\u003ekey in the recipient\u0027s group. If the certificate declares a group order of 1,\u003cbr\u003erandom scalar generation can only produce zero. The key generation routine\u003cbr\u003ethen retries without limit while waiting for a nonzero private scalar, so the\u003cbr\u003ecall never returns.\u003cbr\u003e\u003cbr\u003eThe OpenSSL TLS and QUIC implementations do not use this path. An application\u003cbr\u003eis exposed only if it calls CMS_encrypt() or CMS_encrypt_ex() with a recipient\u003cbr\u003ecertificate whose EC parameters are attacker-controlled. Certificates with\u003cbr\u003enormal EC group orders do not trigger the loop.\u003cbr\u003e\u003cbr\u003eOpenSSL 4.0 and later reject unknown explicit EC groups in default builds.\u003cbr\u003eThese versions are affected only when configured with the\u003cbr\u003eenable-ec_explicit_curves option.\u003cbr\u003e\u003cbr\u003eThe result is a hang that consumes a CPU core until the process is\u003cbr\u003einterrupted, a Denial of Service. The severity is Low because the attacker\u003cbr\u003emust supply the recipient certificate and the application must choose to\u003cbr\u003eencrypt to it; ordinary CMS encryption to trusted recipients is unaffected.\u003cbr\u003e\u003cbr\u003eThe fix makes EC key generation fail when the group has no valid nonzero\u003cbr\u003eprivate scalar, instead of retrying indefinitely.\u003cbr\u003e\u003cbr\u003eFIPS impact: no\u003cbr\u003eThe FIPS modules in 4.1, 4.0, 3.5 and 3.0 are not affected. The FIPS provider\u003cbr\u003edoes not support arbitrary explicit EC domain parameters, so an order-1 group\u003cbr\u003eis rejected during key import before the vulnerable key generation path is\u003cbr\u003ereached."
}
],
"value": "Issue summary: Encrypting a CMS message to an EC certificate whose group order\nis 1 may cause CMS_encrypt() or CMS_encrypt_ex() to loop indefinitely.\n\nImpact summary: An attacker able to supply the recipient certificate to an\napplication performing CMS encryption can cause that application to loop\nindefinitely, consuming CPU and resulting in Denial of Service.\n\nCWE: CWE-835: Loop with Unreachable Exit Condition (\u0027Infinite Loop\u0027)\n\nDescription: CMS_encrypt() and CMS_encrypt_ex() encrypt a message to one or\nmore recipient certificates and, for an EC recipient, generate an ephemeral\nkey in the recipient\u0027s group. If the certificate declares a group order of 1,\nrandom scalar generation can only produce zero. The key generation routine\nthen retries without limit while waiting for a nonzero private scalar, so the\ncall never returns.\n\nThe OpenSSL TLS and QUIC implementations do not use this path. An application\nis exposed only if it calls CMS_encrypt() or CMS_encrypt_ex() with a recipient\ncertificate whose EC parameters are attacker-controlled. Certificates with\nnormal EC group orders do not trigger the loop.\n\nOpenSSL 4.0 and later reject unknown explicit EC groups in default builds.\nThese versions are affected only when configured with the\nenable-ec_explicit_curves option.\n\nThe result is a hang that consumes a CPU core until the process is\ninterrupted, a Denial of Service. The severity is Low because the attacker\nmust supply the recipient certificate and the application must choose to\nencrypt to it; ordinary CMS encryption to trusted recipients is unaffected.\n\nThe fix makes EC key generation fail when the group has no valid nonzero\nprivate scalar, instead of retrying indefinitely.\n\nFIPS impact: no\nThe FIPS modules in 4.1, 4.0, 3.5 and 3.0 are not affected. The FIPS provider\ndoes not support arbitrary explicit EC domain parameters, so an order-1 group\nis rejected during key import before the vulnerable key generation path is\nreached."
}
],
"metrics": [
{
"format": "other",
"other": {
"content": {
"text": "Low"
},
"type": "https://openssl-library.org/policies/general/security-policy/"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-835",
"description": "CWE-835 Loop with Unreachable Exit Condition (\u0027Infinite Loop\u0027)",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-10T18:14:18.207Z",
"orgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"shortName": "openssl"
},
"references": [
{
"name": "OpenSSL Advisory",
"tags": [
"vendor-advisory"
],
"url": "https://openssl-library.org/news/secadv/20261110.txt"
},
{
"name": "4.1.1 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/36e15b618decdff1b116eead6747718e6e729ad2"
},
{
"name": "4.0.4 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/a8531368ddb1f86d2a2782a8b693926bb67b59e7"
},
{
"name": "3.5.10 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/a0051cfe699bf5a047bc1c4faef65f80f7987366"
}
],
"source": {
"discovery": "UNKNOWN"
},
"title": "Infinite Loop in CMS_encrypt() With an EC Group Order of 1",
"x_generator": {
"engine": "Vulnogram 0.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"assignerShortName": "openssl",
"cveId": "CVE-2026-107496",
"datePublished": "2026-11-10T18:14:18.207Z",
"dateReserved": "2026-10-08T08:31:36.278Z",
"dateUpdated": "2026-11-16T19:11:29.337Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-95690 (GCVE-0-2026-95690)
Vulnerability from cvelistv5 – Published: 2026-11-18 11:44 – Updated: 2026-11-18 15:23
VLAI
EPSS
VEX
Summary
Receiving crafted out-of-sequence DTLS handshake fragments may cause OpenSSL to allocate a full message-length reassembly buffer for each buffered message, so a small amount of wire data consumes a large amount of memory.
Severity
5.3 (Medium)
SSVC
Exploitation: none
Automatable: yes
Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-18 13:50 UTC
CWE
- CWE-400 - Uncontrolled Resource Consumption
Assigner
References
2 references
Impacted products
{
"containers": {
"adp": [
{
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "LOW",
"baseScore": 5.3,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L",
"version": "3.1"
}
},
{
"other": {
"content": {
"id": "CVE-2026-95690",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-18T13:50:26.611679Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-400",
"description": "CWE-400 Uncontrolled Resource Consumption",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T15:23:34.371Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "OpenSSL",
"vendor": "OpenSSL",
"versions": [
{
"lessThan": "4.1.1",
"status": "affected",
"version": "4.1.0",
"versionType": "semver"
},
{
"lessThan": "4.0.4",
"status": "affected",
"version": "4.0.0",
"versionType": "semver"
},
{
"lessThan": "3.5.10",
"status": "affected",
"version": "3.5.0",
"versionType": "semver"
},
{
"lessThan": "3.0.24",
"status": "affected",
"version": "3.0.0",
"versionType": "semver"
},
{
"lessThan": "1.1.1zk",
"status": "affected",
"version": "1.1.1",
"versionType": "custom"
},
{
"lessThan": "1.0.2zt",
"status": "affected",
"version": "1.0.2",
"versionType": "custom"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "Receiving crafted out-of-sequence DTLS handshake fragments may cause OpenSSL to allocate a full message-length reassembly buffer for each buffered message, so a small amount of wire data consumes a large amount of memory."
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T11:44:16.564Z",
"orgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"shortName": "openssl"
},
"references": [
{
"name": "Fix PR for 4.1",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/pull/33620"
},
{
"name": "Fix PR for 4.0 and 3.5",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/pull/33729"
}
],
"x_generator": {
"engine": "cvelib 1.8.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"assignerShortName": "openssl",
"cveId": "CVE-2026-95690",
"datePublished": "2026-11-18T11:44:16.564Z",
"dateReserved": "2026-09-22T14:18:48.634Z",
"dateUpdated": "2026-11-18T15:23:34.371Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-84786 (GCVE-0-2026-84786)
Vulnerability from cvelistv5 – Published: 2026-11-18 11:43 – Updated: 2026-11-18 11:43
VLAI
EPSS
VEX
Summary
A DANE-enabled TLS client may crash by dereferencing a NULL pointer when processing an unusual combination of certificate and TLSA records.
Severity
No CVSS data available.
Assigner
References
1 reference
| URL | Tags |
|---|---|
| https://github.com/openssl/openssl/pull/33634 | patch |
Impacted products
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "OpenSSL",
"vendor": "OpenSSL",
"versions": [
{
"lessThan": "4.1.1",
"status": "affected",
"version": "4.1.0",
"versionType": "semver"
},
{
"lessThan": "4.0.4",
"status": "affected",
"version": "4.0.0",
"versionType": "semver"
},
{
"lessThan": "3.5.10",
"status": "affected",
"version": "3.5.0",
"versionType": "semver"
},
{
"lessThan": "3.0.24",
"status": "affected",
"version": "3.0.0",
"versionType": "semver"
},
{
"lessThan": "1.1.1zk",
"status": "affected",
"version": "1.1.1",
"versionType": "custom"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "A DANE-enabled TLS client may crash by dereferencing a NULL pointer when processing an unusual combination of certificate and TLSA records."
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T11:43:57.201Z",
"orgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"shortName": "openssl"
},
"references": [
{
"name": "Fix PR #33634",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/pull/33634"
}
],
"x_generator": {
"engine": "cvelib 1.8.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"assignerShortName": "openssl",
"cveId": "CVE-2026-84786",
"datePublished": "2026-11-18T11:43:57.201Z",
"dateReserved": "2026-09-02T10:14:02.262Z",
"dateUpdated": "2026-11-18T11:43:57.201Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-121482 (GCVE-0-2026-121482)
Vulnerability from cvelistv5 – Published: 2026-11-18 11:43 – Updated: 2026-11-18 11:43
VLAI
EPSS
VEX
Summary
Verifying a maliciously crafted CMS or PKCS#7 SignedData message with CRL checking enabled may consume excessive CPU time, growing with the square of the message size.
Severity
No CVSS data available.
Assigner
References
1 reference
| URL | Tags |
|---|---|
| https://github.com/openssl/openssl/pull/33546 | patch |
Impacted products
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "OpenSSL",
"vendor": "OpenSSL",
"versions": [
{
"lessThan": "4.1.1",
"status": "affected",
"version": "4.1.0",
"versionType": "semver"
},
{
"lessThan": "4.0.4",
"status": "affected",
"version": "4.0.0",
"versionType": "semver"
},
{
"lessThan": "3.5.10",
"status": "affected",
"version": "3.5.0",
"versionType": "semver"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "Verifying a maliciously crafted CMS or PKCS#7 SignedData message with CRL checking enabled may consume excessive CPU time, growing with the square of the message size."
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T11:43:42.786Z",
"orgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"shortName": "openssl"
},
"references": [
{
"name": "Fix PR #33546",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/pull/33546"
}
],
"x_generator": {
"engine": "cvelib 1.8.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"assignerShortName": "openssl",
"cveId": "CVE-2026-121482",
"datePublished": "2026-11-18T11:43:42.786Z",
"dateReserved": "2026-11-03T13:45:42.894Z",
"dateUpdated": "2026-11-18T11:43:42.786Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-121481 (GCVE-0-2026-121481)
Vulnerability from cvelistv5 – Published: 2026-11-18 11:43 – Updated: 2026-11-18 11:43
VLAI
EPSS
VEX
Summary
Calling EVP_EncodeBlock() with an input length close to INT_MAX may overflow the calculation of the encoded output size and write past the end of the caller-supplied output buffer.
Severity
No CVSS data available.
Assigner
References
1 reference
| URL | Tags |
|---|---|
| https://github.com/openssl/openssl/pull/33652 | patch |
Impacted products
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "OpenSSL",
"vendor": "OpenSSL",
"versions": [
{
"lessThan": "4.1.1",
"status": "affected",
"version": "4.1.0",
"versionType": "semver"
},
{
"lessThan": "4.0.4",
"status": "affected",
"version": "4.0.0",
"versionType": "semver"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "Calling EVP_EncodeBlock() with an input length close to INT_MAX may overflow the calculation of the encoded output size and write past the end of the caller-supplied output buffer."
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T11:43:33.634Z",
"orgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"shortName": "openssl"
},
"references": [
{
"name": "Fix PR #33652",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/pull/33652"
}
],
"x_generator": {
"engine": "cvelib 1.8.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"assignerShortName": "openssl",
"cveId": "CVE-2026-121481",
"datePublished": "2026-11-18T11:43:33.634Z",
"dateReserved": "2026-11-03T13:45:42.894Z",
"dateUpdated": "2026-11-18T11:43:33.634Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-107494 (GCVE-0-2026-107494)
Vulnerability from cvelistv5 – Published: 2026-11-18 11:43 – Updated: 2026-11-18 11:43
VLAI
EPSS
VEX
Summary
The QUIC stack queues a RETIRE_CONNECTION_ID frame also for retransmitted NEW_CONNECTION_ID frames. This allows a remote malicious QUIC stack to queue an unlimited number of RETIRE_CONNECTION_ID frames.
Severity
No CVSS data available.
Assigner
References
1 reference
| URL | Tags |
|---|---|
| https://github.com/openssl/openssl/pull/33544 | patch |
Impacted products
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "OpenSSL",
"vendor": "OpenSSL",
"versions": [
{
"lessThan": "4.1.1",
"status": "affected",
"version": "4.1.0",
"versionType": "semver"
},
{
"lessThan": "4.0.4",
"status": "affected",
"version": "4.0.0",
"versionType": "semver"
},
{
"lessThan": "3.5.10",
"status": "affected",
"version": "3.5.0",
"versionType": "semver"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "The QUIC stack queues a RETIRE_CONNECTION_ID frame also for retransmitted NEW_CONNECTION_ID frames. This allows a remote malicious QUIC stack to queue an unlimited number of RETIRE_CONNECTION_ID frames."
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T11:43:10.955Z",
"orgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"shortName": "openssl"
},
"references": [
{
"name": "Fix PR #33544",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/pull/33544"
}
],
"x_generator": {
"engine": "cvelib 1.8.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"assignerShortName": "openssl",
"cveId": "CVE-2026-107494",
"datePublished": "2026-11-18T11:43:10.955Z",
"dateReserved": "2026-10-08T08:31:36.278Z",
"dateUpdated": "2026-11-18T11:43:10.955Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-35190 (GCVE-0-2026-35190)
Vulnerability from cvelistv5 – Published: 2026-11-17 08:15 – Updated: 2026-11-17 16:52
VLAI
EPSS
VEX
Title
Out-of-Bounds Read in TLS 1.3 Key-Share Processing with Suite B Certificate Flag
Summary
Issue summary: A server configured with the Suite B certificate flag through
SSL_CTX_set_cert_flags() and with TLS 1.3 enabled may read past the end of a
fixed group list when it processes a ClientHello whose supported_groups and
key_share contain no Suite B group.
Impact summary: A remote client can send a ClientHello that makes the server
read past the end of a static array. The values read are never returned to the
client, so no memory is disclosed; on builds with sanitizers or hardened
allocators the read may crash the process, causing Denial of Service.
CWE: CWE-125: Out-of-bounds Read
Description: When the Suite B certificate flag is set, OpenSSL restricts the
accepted groups to P-256 and P-384 by substituting a fixed two-element list
for the configured group list. The tuple machinery used for key-share
selection was not updated for this substitution: tls1_get_group_tuples() still
returns the configured tuples, which by default describe eight groups. The
server-side walk in tls_parse_ctos_key_share() then advances through the
two-element list using those tuple counts without checking the cumulative
offset against the number of groups present.
Only applications that call SSL_CTX_set_cert_flags() with
SSL_CERT_FLAG_SUITEB_128_LOS and leave TLS 1.3 enabled are affected. The
openssl s_server -suiteB_128 option sets an X.509 verification parameter
instead, so the stock command line server is not vulnerable. Default
configurations do not reach this code.
A client that offers only groups outside the Suite B set, such as X25519,
forces every tuple to be walked and the read to run past the array. The bytes
read are compared against client group IDs and never sent back, so no memory
is disclosed. On builds with address sanitizers or hardened allocators the
read can abort the process; in ordinary release builds it reads a few bytes of
adjacent constant data.
FIPS impact: no
The affected code is outside the FIPS module boundary.
Severity
5.3 (Medium)
SSVC
Exploitation: none
Automatable: yes
Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-17 16:51 UTC
CWE
- CWE-125 - Out-of-bounds Read
Assigner
References
4 references
Impacted products
Date Public
2026-11-17 07:01
{
"containers": {
"adp": [
{
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.3,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
"version": "3.1"
}
},
{
"other": {
"content": {
"id": "CVE-2026-35190",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-17T16:51:09.335502Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-17T16:52:00.153Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "OpenSSL",
"vendor": "OpenSSL",
"versions": [
{
"lessThan": "4.1.1",
"status": "affected",
"version": "4.1.0",
"versionType": "semver"
},
{
"lessThan": "4.0.4",
"status": "affected",
"version": "4.0.0",
"versionType": "semver"
},
{
"lessThan": "3.5.10",
"status": "affected",
"version": "3.5.0",
"versionType": "semver"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "Laurent Gaffie (secorizon.com)"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Daniel Kubec"
}
],
"datePublic": "2026-11-17T07:01:24.000Z",
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "Issue summary: A server configured with the Suite B certificate flag through\u003cbr\u003eSSL_CTX_set_cert_flags() and with TLS 1.3 enabled may read past the end of a\u003cbr\u003efixed group list when it processes a ClientHello whose supported_groups and\u003cbr\u003ekey_share contain no Suite B group.\u003cbr\u003e\u003cbr\u003eImpact summary: A remote client can send a ClientHello that makes the server\u003cbr\u003eread past the end of a static array. The values read are never returned to the\u003cbr\u003eclient, so no memory is disclosed; on builds with sanitizers or hardened\u003cbr\u003eallocators the read may crash the process, causing Denial of Service.\u003cbr\u003e\u003cbr\u003eCWE: CWE-125: Out-of-bounds Read\u003cbr\u003e\u003cbr\u003eDescription: When the Suite B certificate flag is set, OpenSSL restricts the\u003cbr\u003eaccepted groups to P-256 and P-384 by substituting a fixed two-element list\u003cbr\u003efor the configured group list. The tuple machinery used for key-share\u003cbr\u003eselection was not updated for this substitution: tls1_get_group_tuples() still\u003cbr\u003ereturns the configured tuples, which by default describe eight groups. The\u003cbr\u003eserver-side walk in tls_parse_ctos_key_share() then advances through the\u003cbr\u003etwo-element list using those tuple counts without checking the cumulative\u003cbr\u003eoffset against the number of groups present.\u003cbr\u003e\u003cbr\u003eOnly applications that call SSL_CTX_set_cert_flags() with\u003cbr\u003eSSL_CERT_FLAG_SUITEB_128_LOS and leave TLS 1.3 enabled are affected. The\u003cbr\u003eopenssl s_server -suiteB_128 option sets an X.509 verification parameter\u003cbr\u003einstead, so the stock command line server is not vulnerable. Default\u003cbr\u003econfigurations do not reach this code.\u003cbr\u003e\u003cbr\u003eA client that offers only groups outside the Suite B set, such as X25519,\u003cbr\u003eforces every tuple to be walked and the read to run past the array. The bytes\u003cbr\u003eread are compared against client group IDs and never sent back, so no memory\u003cbr\u003eis disclosed. On builds with address sanitizers or hardened allocators the\u003cbr\u003eread can abort the process; in ordinary release builds it reads a few bytes of\u003cbr\u003eadjacent constant data.\u003cbr\u003e\u003cbr\u003eFIPS impact: no\u003cbr\u003eThe affected code is outside the FIPS module boundary."
}
],
"value": "Issue summary: A server configured with the Suite B certificate flag through\nSSL_CTX_set_cert_flags() and with TLS 1.3 enabled may read past the end of a\nfixed group list when it processes a ClientHello whose supported_groups and\nkey_share contain no Suite B group.\n\nImpact summary: A remote client can send a ClientHello that makes the server\nread past the end of a static array. The values read are never returned to the\nclient, so no memory is disclosed; on builds with sanitizers or hardened\nallocators the read may crash the process, causing Denial of Service.\n\nCWE: CWE-125: Out-of-bounds Read\n\nDescription: When the Suite B certificate flag is set, OpenSSL restricts the\naccepted groups to P-256 and P-384 by substituting a fixed two-element list\nfor the configured group list. The tuple machinery used for key-share\nselection was not updated for this substitution: tls1_get_group_tuples() still\nreturns the configured tuples, which by default describe eight groups. The\nserver-side walk in tls_parse_ctos_key_share() then advances through the\ntwo-element list using those tuple counts without checking the cumulative\noffset against the number of groups present.\n\nOnly applications that call SSL_CTX_set_cert_flags() with\nSSL_CERT_FLAG_SUITEB_128_LOS and leave TLS 1.3 enabled are affected. The\nopenssl s_server -suiteB_128 option sets an X.509 verification parameter\ninstead, so the stock command line server is not vulnerable. Default\nconfigurations do not reach this code.\n\nA client that offers only groups outside the Suite B set, such as X25519,\nforces every tuple to be walked and the read to run past the array. The bytes\nread are compared against client group IDs and never sent back, so no memory\nis disclosed. On builds with address sanitizers or hardened allocators the\nread can abort the process; in ordinary release builds it reads a few bytes of\nadjacent constant data.\n\nFIPS impact: no\nThe affected code is outside the FIPS module boundary."
}
],
"metrics": [
{
"format": "other",
"other": {
"content": {
"text": "Low"
},
"type": "https://openssl-library.org/policies/general/security-policy/"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-125",
"description": "Out-of-bounds Read",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-17T08:15:01.294Z",
"orgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"shortName": "openssl"
},
"references": [
{
"name": "OpenSSL Advisory",
"tags": [
"vendor-advisory"
],
"url": "https://openssl-library.org/news/secadv/20261117.txt"
},
{
"name": "4.1.1 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/ade64619df04056b3e5fd1c1befe9425a7c80eb6"
},
{
"name": "4.0.4 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/9a812981b927c5714b7c2e5d138618105cea2152"
},
{
"name": "3.5.10 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/9491b0d9cc7950af1f3dc89499bd5433b9cd4f43"
}
],
"source": {
"discovery": "UNKNOWN"
},
"title": "Out-of-Bounds Read in TLS 1.3 Key-Share Processing with Suite B Certificate Flag",
"x_generator": {
"engine": "Vulnogram 0.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"assignerShortName": "openssl",
"cveId": "CVE-2026-35190",
"datePublished": "2026-11-17T08:15:01.294Z",
"dateReserved": "2026-04-01T17:36:26.323Z",
"dateUpdated": "2026-11-17T16:52:00.153Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-124709 (GCVE-0-2026-124709)
Vulnerability from cvelistv5 – Published: 2026-11-17 08:14 – Updated: 2026-11-17 16:50
VLAI
EPSS
VEX
Title
Unbounded Memory Retention in QUIC Server for Rejected Streams
Summary
Issue summary: A QUIC server that rejects a stream opened by the peer may
retain that stream's state for the lifetime of the connection if the peer
resets the stream before the rejection is signalled, even though the peer's
stream credit is returned.
Impact summary: A remote client that completes a QUIC handshake can repeatedly
open and reset streams, causing server memory to grow without bound until the
process runs out of memory and every connection on it is lost. This is a
Denial of Service.
CWE: CWE-401: Missing Release of Memory after Effective Lifetime
Description: QUIC servers track each stream the peer opens. When the incoming
stream policy rejects a stream, OpenSSL schedules a STOP_SENDING frame, marks
the stream deleted and returns the peer's stream credit. A deleted stream is
collected only once its receive part is fully drained, which for a rejected
stream means the STOP_SENDING has been acknowledged. If the peer sends
RESET_STREAM first, the reset cancels the pending STOP_SENDING, so it is never
sent or acknowledged and the stream is never collected.
The default configuration reaches this path. Once a connection has a default
stream, meaning the application has read from or written to the connection as
the tutorial server does, the effective incoming stream policy rejects streams
the application does not accept. Applications that set the REJECT policy
explicitly are affected too.
Each retained stream costs about 300 bytes, and the peer's stream credit
window paces how quickly they accumulate. A client that keeps the connection
open and keeps opening and resetting streams grows server memory without
bound. The severity is Low because growth is slow, needs a long-lived
connection, and causes no memory corruption or disclosure.
FIPS impact: no
The affected code is outside the FIPS module boundary.
Severity
7.5 (High)
SSVC
Exploitation: none
Automatable: yes
Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-17 16:50 UTC
CWE
- CWE-401 - Missing Release of Memory after Effective Lifetime
Assigner
References
4 references
Impacted products
Date Public
2026-11-17 07:01
{
"containers": {
"adp": [
{
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
}
},
{
"other": {
"content": {
"id": "CVE-2026-124709",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-17T16:50:13.860911Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-17T16:50:38.539Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "OpenSSL",
"vendor": "OpenSSL",
"versions": [
{
"lessThan": "4.1.1",
"status": "affected",
"version": "4.1.0",
"versionType": "semver"
},
{
"lessThan": "4.0.4",
"status": "affected",
"version": "4.0.0",
"versionType": "semver"
},
{
"lessThan": "3.5.10",
"status": "affected",
"version": "3.5.0",
"versionType": "semver"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "Bhabani Sankar Das"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Bhabani Sankar Das"
}
],
"datePublic": "2026-11-17T07:01:24.000Z",
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "Issue summary: A QUIC server that rejects a stream opened by the peer may\u003cbr\u003eretain that stream\u0027s state for the lifetime of the connection if the peer\u003cbr\u003eresets the stream before the rejection is signalled, even though the peer\u0027s\u003cbr\u003estream credit is returned.\u003cbr\u003e\u003cbr\u003eImpact summary: A remote client that completes a QUIC handshake can repeatedly\u003cbr\u003eopen and reset streams, causing server memory to grow without bound until the\u003cbr\u003eprocess runs out of memory and every connection on it is lost. This is a\u003cbr\u003eDenial of Service.\u003cbr\u003e\u003cbr\u003eCWE: CWE-401: Missing Release of Memory after Effective Lifetime\u003cbr\u003e\u003cbr\u003eDescription: QUIC servers track each stream the peer opens. When the incoming\u003cbr\u003estream policy rejects a stream, OpenSSL schedules a STOP_SENDING frame, marks\u003cbr\u003ethe stream deleted and returns the peer\u0027s stream credit. A deleted stream is\u003cbr\u003ecollected only once its receive part is fully drained, which for a rejected\u003cbr\u003estream means the STOP_SENDING has been acknowledged. If the peer sends\u003cbr\u003eRESET_STREAM first, the reset cancels the pending STOP_SENDING, so it is never\u003cbr\u003esent or acknowledged and the stream is never collected.\u003cbr\u003e\u003cbr\u003eThe default configuration reaches this path. Once a connection has a default\u003cbr\u003estream, meaning the application has read from or written to the connection as\u003cbr\u003ethe tutorial server does, the effective incoming stream policy rejects streams\u003cbr\u003ethe application does not accept. Applications that set the REJECT policy\u003cbr\u003eexplicitly are affected too.\u003cbr\u003e\u003cbr\u003eEach retained stream costs about 300 bytes, and the peer\u0027s stream credit\u003cbr\u003ewindow paces how quickly they accumulate. A client that keeps the connection\u003cbr\u003eopen and keeps opening and resetting streams grows server memory without\u003cbr\u003ebound. The severity is Low because growth is slow, needs a long-lived\u003cbr\u003econnection, and causes no memory corruption or disclosure.\u003cbr\u003e\u003cbr\u003eFIPS impact: no\u003cbr\u003eThe affected code is outside the FIPS module boundary."
}
],
"value": "Issue summary: A QUIC server that rejects a stream opened by the peer may\nretain that stream\u0027s state for the lifetime of the connection if the peer\nresets the stream before the rejection is signalled, even though the peer\u0027s\nstream credit is returned.\n\nImpact summary: A remote client that completes a QUIC handshake can repeatedly\nopen and reset streams, causing server memory to grow without bound until the\nprocess runs out of memory and every connection on it is lost. This is a\nDenial of Service.\n\nCWE: CWE-401: Missing Release of Memory after Effective Lifetime\n\nDescription: QUIC servers track each stream the peer opens. When the incoming\nstream policy rejects a stream, OpenSSL schedules a STOP_SENDING frame, marks\nthe stream deleted and returns the peer\u0027s stream credit. A deleted stream is\ncollected only once its receive part is fully drained, which for a rejected\nstream means the STOP_SENDING has been acknowledged. If the peer sends\nRESET_STREAM first, the reset cancels the pending STOP_SENDING, so it is never\nsent or acknowledged and the stream is never collected.\n\nThe default configuration reaches this path. Once a connection has a default\nstream, meaning the application has read from or written to the connection as\nthe tutorial server does, the effective incoming stream policy rejects streams\nthe application does not accept. Applications that set the REJECT policy\nexplicitly are affected too.\n\nEach retained stream costs about 300 bytes, and the peer\u0027s stream credit\nwindow paces how quickly they accumulate. A client that keeps the connection\nopen and keeps opening and resetting streams grows server memory without\nbound. The severity is Low because growth is slow, needs a long-lived\nconnection, and causes no memory corruption or disclosure.\n\nFIPS impact: no\nThe affected code is outside the FIPS module boundary."
}
],
"metrics": [
{
"format": "other",
"other": {
"content": {
"text": "Low"
},
"type": "https://openssl-library.org/policies/general/security-policy/"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-401",
"description": "Missing Release of Memory after Effective Lifetime",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-17T08:14:35.674Z",
"orgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"shortName": "openssl"
},
"references": [
{
"name": "OpenSSL Advisory",
"tags": [
"vendor-advisory"
],
"url": "https://openssl-library.org/news/secadv/20261117.txt"
},
{
"name": "4.1.1 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/ead311df1037e7994a6d86c7e862d71ad59c52c7"
},
{
"name": "4.0.4 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/22291a6af12f158fbb13bfbd572a33dbdbf290d2"
},
{
"name": "3.5.10 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/f3acb0a3328046741479482c51cec815839e1b05"
}
],
"source": {
"discovery": "UNKNOWN"
},
"title": "Unbounded Memory Retention in QUIC Server for Rejected Streams",
"x_generator": {
"engine": "Vulnogram 0.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"assignerShortName": "openssl",
"cveId": "CVE-2026-124709",
"datePublished": "2026-11-17T08:14:35.674Z",
"dateReserved": "2026-11-09T10:45:57.951Z",
"dateUpdated": "2026-11-17T16:50:38.539Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-107493 (GCVE-0-2026-107493)
Vulnerability from cvelistv5 – Published: 2026-11-17 08:14 – Updated: 2026-11-17 16:49
VLAI
EPSS
VEX
Title
Use-After-Free in PEM_X509_INFO_read_bio_ex() when appending to a caller-supplied stack fails
Summary
Issue summary: When an application passes a stack to
PEM_X509_INFO_read_bio_ex() to add entries to, and reading fails,
OpenSSL frees every entry in the stack, both the old ones and any new
ones, but leaves them in the stack.
Impact summary: An application that passes an existing stack to
PEM_X509_INFO_read_bio_ex() and keeps using it after a failed read may
use memory that was already freed. This can cause a crash or, in
principle, memory corruption. Malformed PEM data can make the read fail,
but only applications that pass an existing stack are affected, and
OpenSSL itself does not do this.
CWE: CWE-416: Use After Free
Description: PEM_X509_INFO_read_bio_ex() reads certificates, CRLs and
private keys from PEM data and adds them to a stack of X509_INFO
structures. If the application passes a stack that is not NULL, the
function adds the new entries to it and must leave the entries that are
already there unchanged.
If reading fails, the function frees every entry in the stack. This
includes the entries that were there before the call, and the entries
added by the call. It does not remove these entries from the stack, so
the stack keeps pointers to freed memory. The failure can happen at any
point, even before any entry was added. A PEM item with invalid content
is enough. This also happens if the stack was empty: entries added
before the failure are freed but stay in the stack.
An application that then reads or frees the stack will use memory that
was already freed. This can crash the application or, in principle,
corrupt memory.
Only applications that pass a stack that is not NULL are affected.
OpenSSL itself never does this. Its own callers, including the code that
TLS uses to load CA certificates, always pass NULL. When the stack is
NULL, the function frees only the entries that it created itself, which
is safe. We expect that very few applications pass an existing stack. An
attacker can make the read fail with malformed PEM data, but cannot make
an application pass an existing stack.
The same problem affects PEM_X509_INFO_read_bio(), PEM_X509_INFO_read()
and PEM_X509_INFO_read_ex(), which use the same code. OpenSSL 1.1.1 and
1.0.2 have only the first two of these functions.
FIPS impact: no
The affected code is outside the FIPS module boundary.
Severity
7.7 (High)
SSVC
Exploitation: none
Automatable: no
Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-17 16:47 UTC
CWE
- CWE-416 - Use After Free
Assigner
References
4 references
Impacted products
Date Public
2026-11-17 07:01
{
"containers": {
"adp": [
{
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 7.7,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H",
"version": "3.1"
}
},
{
"other": {
"content": {
"id": "CVE-2026-107493",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-17T16:47:04.388261Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-17T16:49:16.589Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "OpenSSL",
"vendor": "OpenSSL",
"versions": [
{
"lessThan": "4.1.1",
"status": "affected",
"version": "4.1.0",
"versionType": "semver"
},
{
"lessThan": "4.0.4",
"status": "affected",
"version": "4.0.0",
"versionType": "semver"
},
{
"lessThan": "3.5.10",
"status": "affected",
"version": "3.5.0",
"versionType": "semver"
},
{
"lessThan": "3.0.24",
"status": "affected",
"version": "3.0.0",
"versionType": "semver"
},
{
"lessThan": "1.1.1zk",
"status": "affected",
"version": "1.1.1",
"versionType": "custom"
},
{
"lessThan": "1.0.2zt",
"status": "affected",
"version": "1.0.2",
"versionType": "custom"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "Filipe Casal (Trail of Bits)"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Viktor Dukhovni"
}
],
"datePublic": "2026-11-17T07:01:24.000Z",
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "Issue summary: When an application passes a stack to\u003cbr\u003ePEM_X509_INFO_read_bio_ex() to add entries to, and reading fails,\u003cbr\u003eOpenSSL frees every entry in the stack, both the old ones and any new\u003cbr\u003eones, but leaves them in the stack.\u003cbr\u003e\u003cbr\u003eImpact summary: An application that passes an existing stack to\u003cbr\u003ePEM_X509_INFO_read_bio_ex() and keeps using it after a failed read may\u003cbr\u003euse memory that was already freed. This can cause a crash or, in\u003cbr\u003eprinciple, memory corruption. Malformed PEM data can make the read fail,\u003cbr\u003ebut only applications that pass an existing stack are affected, and\u003cbr\u003eOpenSSL itself does not do this.\u003cbr\u003e\u003cbr\u003eCWE: CWE-416: Use After Free\u003cbr\u003e\u003cbr\u003eDescription: PEM_X509_INFO_read_bio_ex() reads certificates, CRLs and\u003cbr\u003eprivate keys from PEM data and adds them to a stack of X509_INFO\u003cbr\u003estructures. If the application passes a stack that is not NULL, the\u003cbr\u003efunction adds the new entries to it and must leave the entries that are\u003cbr\u003ealready there unchanged.\u003cbr\u003e\u003cbr\u003eIf reading fails, the function frees every entry in the stack. This\u003cbr\u003eincludes the entries that were there before the call, and the entries\u003cbr\u003eadded by the call. It does not remove these entries from the stack, so\u003cbr\u003ethe stack keeps pointers to freed memory. The failure can happen at any\u003cbr\u003epoint, even before any entry was added. A PEM item with invalid content\u003cbr\u003eis enough. This also happens if the stack was empty: entries added\u003cbr\u003ebefore the failure are freed but stay in the stack.\u003cbr\u003e\u003cbr\u003eAn application that then reads or frees the stack will use memory that\u003cbr\u003ewas already freed. This can crash the application or, in principle,\u003cbr\u003ecorrupt memory.\u003cbr\u003e\u003cbr\u003eOnly applications that pass a stack that is not NULL are affected.\u003cbr\u003eOpenSSL itself never does this. Its own callers, including the code that\u003cbr\u003eTLS uses to load CA certificates, always pass NULL. When the stack is\u003cbr\u003eNULL, the function frees only the entries that it created itself, which\u003cbr\u003eis safe. We expect that very few applications pass an existing stack. An\u003cbr\u003eattacker can make the read fail with malformed PEM data, but cannot make\u003cbr\u003ean application pass an existing stack.\u003cbr\u003e\u003cbr\u003eThe same problem affects PEM_X509_INFO_read_bio(), PEM_X509_INFO_read()\u003cbr\u003eand PEM_X509_INFO_read_ex(), which use the same code. OpenSSL 1.1.1 and\u003cbr\u003e1.0.2 have only the first two of these functions.\u003cbr\u003e\u003cbr\u003eFIPS impact: no\u003cbr\u003eThe affected code is outside the FIPS module boundary."
}
],
"value": "Issue summary: When an application passes a stack to\nPEM_X509_INFO_read_bio_ex() to add entries to, and reading fails,\nOpenSSL frees every entry in the stack, both the old ones and any new\nones, but leaves them in the stack.\n\nImpact summary: An application that passes an existing stack to\nPEM_X509_INFO_read_bio_ex() and keeps using it after a failed read may\nuse memory that was already freed. This can cause a crash or, in\nprinciple, memory corruption. Malformed PEM data can make the read fail,\nbut only applications that pass an existing stack are affected, and\nOpenSSL itself does not do this.\n\nCWE: CWE-416: Use After Free\n\nDescription: PEM_X509_INFO_read_bio_ex() reads certificates, CRLs and\nprivate keys from PEM data and adds them to a stack of X509_INFO\nstructures. If the application passes a stack that is not NULL, the\nfunction adds the new entries to it and must leave the entries that are\nalready there unchanged.\n\nIf reading fails, the function frees every entry in the stack. This\nincludes the entries that were there before the call, and the entries\nadded by the call. It does not remove these entries from the stack, so\nthe stack keeps pointers to freed memory. The failure can happen at any\npoint, even before any entry was added. A PEM item with invalid content\nis enough. This also happens if the stack was empty: entries added\nbefore the failure are freed but stay in the stack.\n\nAn application that then reads or frees the stack will use memory that\nwas already freed. This can crash the application or, in principle,\ncorrupt memory.\n\nOnly applications that pass a stack that is not NULL are affected.\nOpenSSL itself never does this. Its own callers, including the code that\nTLS uses to load CA certificates, always pass NULL. When the stack is\nNULL, the function frees only the entries that it created itself, which\nis safe. We expect that very few applications pass an existing stack. An\nattacker can make the read fail with malformed PEM data, but cannot make\nan application pass an existing stack.\n\nThe same problem affects PEM_X509_INFO_read_bio(), PEM_X509_INFO_read()\nand PEM_X509_INFO_read_ex(), which use the same code. OpenSSL 1.1.1 and\n1.0.2 have only the first two of these functions.\n\nFIPS impact: no\nThe affected code is outside the FIPS module boundary."
}
],
"metrics": [
{
"format": "other",
"other": {
"content": {
"text": "Low"
},
"type": "https://openssl-library.org/policies/general/security-policy/"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-416",
"description": "Use After Free",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-17T08:14:08.947Z",
"orgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"shortName": "openssl"
},
"references": [
{
"name": "OpenSSL Advisory",
"tags": [
"vendor-advisory"
],
"url": "https://openssl-library.org/news/secadv/20261117.txt"
},
{
"name": "4.1.1 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/c57a5ccf0c060755b5494a6870922b7c6cdd7dd8"
},
{
"name": "4.0.4 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/0486dfadfec558e1808f59d35a8d79e541c4e7d7"
},
{
"name": "3.5.10 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/c8f6d04f8e6d40b1bf83334e4a2ec9daf5943a3d"
}
],
"source": {
"discovery": "UNKNOWN"
},
"title": "Use-After-Free in PEM_X509_INFO_read_bio_ex() when appending to a caller-supplied stack fails",
"x_generator": {
"engine": "Vulnogram 0.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"assignerShortName": "openssl",
"cveId": "CVE-2026-107493",
"datePublished": "2026-11-17T08:14:08.947Z",
"dateReserved": "2026-10-08T08:31:36.278Z",
"dateUpdated": "2026-11-17T16:49:16.589Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-95692 (GCVE-0-2026-95692)
Vulnerability from cvelistv5 – Published: 2026-11-10 18:16 – Updated: 2026-11-16 19:08
VLAI
EPSS
VEX
Title
Out-of-Bounds Read and Incorrect IV Length Handling in AES-GCM-SIV
Summary
Issue summary: Setting an AES-GCM-SIV IV shorter than the expected nonce
length via EVP_CipherInit_ex() may trigger a heap out-of-bounds read.
Supplying a longer IV is silently truncated instead of rejected.
Impact summary: An application passing a caller-supplied IV of the wrong
length may crash or read beyond its buffer. Because trailing IV bytes are
ignored, an attacker who knows one message and tag may forge messages under a
different IV.
CWE: CWE-125: Out-of-bounds Read
Description: AES-GCM-SIV copies the caller-supplied IV or nonce into its
internal state using a copy whose length is taken from the expected nonce size
rather than from the length the caller actually provided. When the caller
passes a shorter IV, the copy reads past the end of the caller's buffer;
AddressSanitizer confirms a heap out-of-bounds read reached through
EVP_CipherInit_ex() into ossl_aes_gcm_siv_init(). When the caller passes a
longer IV, the implementation silently discards the trailing bytes instead of
rejecting the length.
The truncation breaks the binding between the IV and the computed
authentication tag. An attacker who has observed a message and its tag under
one IV can produce a message and tag that verify under a different IV whose
first bytes match, since the surplus bytes never influence the computation.
The message itself is unchanged, so this is a failure of IV commitment rather
than a classic existential forgery.
Only applications that call EVP_CipherInit_ex() (or the equivalent provider
cipher initialization) with an IV length other than the standard 12 bytes for
AES-GCM-SIV are affected. The severity is limited because the out-of-bounds
read is small and attacker-controlled only in length, and the forgery requires
an unusual IV length choice by the application.
FIPS impact: no
The FIPS modules are not affected by this issue, as AES-GCM-SIV is not an
approved algorithm.
Severity
7.5 (High)
SSVC
Exploitation: none
Automatable: yes
Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-16 19:08 UTC
CWE
- CWE-125 - Out-of-bounds Read
Assigner
References
4 references
Impacted products
Date Public
2026-11-10 11:00
{
"containers": {
"adp": [
{
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"version": "3.1"
}
},
{
"other": {
"content": {
"id": "CVE-2026-95692",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-16T19:08:03.379147Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-16T19:08:40.459Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "OpenSSL",
"vendor": "OpenSSL",
"versions": [
{
"lessThan": "4.1.1",
"status": "affected",
"version": "4.1.0",
"versionType": "semver"
},
{
"lessThan": "4.0.4",
"status": "affected",
"version": "4.0.0",
"versionType": "semver"
},
{
"lessThan": "3.5.10",
"status": "affected",
"version": "3.5.0",
"versionType": "semver"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "Billy Brumley (Rochester Institute of Technology)"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Billy Brumley (Rochester Institute of Technology)"
}
],
"datePublic": "2026-11-10T11:00:00.000Z",
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "Issue summary: Setting an AES-GCM-SIV IV shorter than the expected nonce\u003cbr\u003elength via EVP_CipherInit_ex() may trigger a heap out-of-bounds read.\u003cbr\u003eSupplying a longer IV is silently truncated instead of rejected.\u003cbr\u003e\u003cbr\u003eImpact summary: An application passing a caller-supplied IV of the wrong\u003cbr\u003elength may crash or read beyond its buffer. Because trailing IV bytes are\u003cbr\u003eignored, an attacker who knows one message and tag may forge messages under a\u003cbr\u003edifferent IV.\u003cbr\u003e\u003cbr\u003eCWE: CWE-125: Out-of-bounds Read\u003cbr\u003e\u003cbr\u003eDescription: AES-GCM-SIV copies the caller-supplied IV or nonce into its\u003cbr\u003einternal state using a copy whose length is taken from the expected nonce size\u003cbr\u003erather than from the length the caller actually provided. When the caller\u003cbr\u003epasses a shorter IV, the copy reads past the end of the caller\u0027s buffer;\u003cbr\u003eAddressSanitizer confirms a heap out-of-bounds read reached through\u003cbr\u003eEVP_CipherInit_ex() into ossl_aes_gcm_siv_init(). When the caller passes a\u003cbr\u003elonger IV, the implementation silently discards the trailing bytes instead of\u003cbr\u003erejecting the length.\u003cbr\u003e\u003cbr\u003eThe truncation breaks the binding between the IV and the computed\u003cbr\u003eauthentication tag. An attacker who has observed a message and its tag under\u003cbr\u003eone IV can produce a message and tag that verify under a different IV whose\u003cbr\u003efirst bytes match, since the surplus bytes never influence the computation.\u003cbr\u003eThe message itself is unchanged, so this is a failure of IV commitment rather\u003cbr\u003ethan a classic existential forgery.\u003cbr\u003e\u003cbr\u003eOnly applications that call EVP_CipherInit_ex() (or the equivalent provider\u003cbr\u003ecipher initialization) with an IV length other than the standard 12 bytes for\u003cbr\u003eAES-GCM-SIV are affected. The severity is limited because the out-of-bounds\u003cbr\u003eread is small and attacker-controlled only in length, and the forgery requires\u003cbr\u003ean unusual IV length choice by the application.\u003cbr\u003e\u003cbr\u003eFIPS impact: no\u003cbr\u003eThe FIPS modules are not affected by this issue, as AES-GCM-SIV is not an\u003cbr\u003eapproved algorithm."
}
],
"value": "Issue summary: Setting an AES-GCM-SIV IV shorter than the expected nonce\nlength via EVP_CipherInit_ex() may trigger a heap out-of-bounds read.\nSupplying a longer IV is silently truncated instead of rejected.\n\nImpact summary: An application passing a caller-supplied IV of the wrong\nlength may crash or read beyond its buffer. Because trailing IV bytes are\nignored, an attacker who knows one message and tag may forge messages under a\ndifferent IV.\n\nCWE: CWE-125: Out-of-bounds Read\n\nDescription: AES-GCM-SIV copies the caller-supplied IV or nonce into its\ninternal state using a copy whose length is taken from the expected nonce size\nrather than from the length the caller actually provided. When the caller\npasses a shorter IV, the copy reads past the end of the caller\u0027s buffer;\nAddressSanitizer confirms a heap out-of-bounds read reached through\nEVP_CipherInit_ex() into ossl_aes_gcm_siv_init(). When the caller passes a\nlonger IV, the implementation silently discards the trailing bytes instead of\nrejecting the length.\n\nThe truncation breaks the binding between the IV and the computed\nauthentication tag. An attacker who has observed a message and its tag under\none IV can produce a message and tag that verify under a different IV whose\nfirst bytes match, since the surplus bytes never influence the computation.\nThe message itself is unchanged, so this is a failure of IV commitment rather\nthan a classic existential forgery.\n\nOnly applications that call EVP_CipherInit_ex() (or the equivalent provider\ncipher initialization) with an IV length other than the standard 12 bytes for\nAES-GCM-SIV are affected. The severity is limited because the out-of-bounds\nread is small and attacker-controlled only in length, and the forgery requires\nan unusual IV length choice by the application.\n\nFIPS impact: no\nThe FIPS modules are not affected by this issue, as AES-GCM-SIV is not an\napproved algorithm."
}
],
"metrics": [
{
"format": "other",
"other": {
"content": {
"text": "Low"
},
"type": "https://openssl-library.org/policies/general/security-policy/"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-125",
"description": "CWE-125 Out-of-bounds Read",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-10T18:16:18.675Z",
"orgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"shortName": "openssl"
},
"references": [
{
"name": "OpenSSL Advisory",
"tags": [
"vendor-advisory"
],
"url": "https://openssl-library.org/news/secadv/20261110.txt"
},
{
"name": "4.1.1 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/70a47ac78b6f3be1b22fb1551bd0bfcff4f29613"
},
{
"name": "4.0.4 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/510872388f5d145cf870868b3d288a23822cb776"
},
{
"name": "3.5.10 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/257a3427aa0ef8d9dd2ef5b3e2d1c021a221b116"
}
],
"source": {
"discovery": "UNKNOWN"
},
"title": "Out-of-Bounds Read and Incorrect IV Length Handling in AES-GCM-SIV",
"x_generator": {
"engine": "Vulnogram 0.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"assignerShortName": "openssl",
"cveId": "CVE-2026-95692",
"datePublished": "2026-11-10T18:16:18.675Z",
"dateReserved": "2026-09-22T14:18:48.635Z",
"dateUpdated": "2026-11-16T19:08:40.459Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-95691 (GCVE-0-2026-95691)
Vulnerability from cvelistv5 – Published: 2026-11-10 18:16 – Updated: 2026-11-16 19:17
VLAI
EPSS
VEX
Title
Retransmitted QUIC CRYPTO Frames Can Cause DoS or One-byte Disclosure
Summary
Issue summary: A retransmitted QUIC CRYPTO frame can release packet storage
while the TLS record layer retains a direct pointer into that storage causing
use after free.
Impact summary: A malicious QUIC server can cause a heap-use-after-free read
in the OpenSSL QUIC client. The server can also identify one allocator-adjacent
byte through the client's protected Handshake response.
CWE: CWE-416: Use After Free
Description: During CRYPTO stream processing, a pointer into the first frame's
memory on the stream is lent to the TLS handshake processing. The memory
must remain stable until it is processed and released. However the processing
of retransmitted CRYPTO frames could release the memory if the retransmitted
frame fully overlapped the existing frame. This then causes use-after-free read
when the TLS handshake processing continues.
The use-after-free read can lead to a Denial-of-Service of the client
application or a minor leak of information about the heap memory contents
that might be overwritten with other data, subsequently allocated by
the application, to the peer.
FIPS impact: no
The FIPS module is not affected as the QUIC implementation is outside of
the OpenSSL FIPS module boundary.
Severity
8.1 (High)
SSVC
Exploitation: none
Automatable: no
Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-16 19:15 UTC
CWE
- CWE-416 - Use After Free
Assigner
References
4 references
Impacted products
Date Public
2026-11-10 11:00
{
"containers": {
"adp": [
{
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "ADJACENT_NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 8.1,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H",
"version": "3.1"
}
},
{
"other": {
"content": {
"id": "CVE-2026-95691",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-16T19:15:55.510879Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-16T19:17:17.580Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "OpenSSL",
"vendor": "OpenSSL",
"versions": [
{
"lessThan": "4.1.1",
"status": "affected",
"version": "4.1.0",
"versionType": "semver"
},
{
"lessThan": "4.0.4",
"status": "affected",
"version": "4.0.0",
"versionType": "semver"
},
{
"lessThan": "3.5.10",
"status": "affected",
"version": "3.5.0",
"versionType": "semver"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "Filipe Casal (Trail of Bits)"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Filipe Casal (Trail of Bits)"
}
],
"datePublic": "2026-11-10T11:00:00.000Z",
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "Issue summary: A retransmitted QUIC CRYPTO frame can release packet storage\u003cbr\u003ewhile the TLS record layer retains a direct pointer into that storage causing\u003cbr\u003euse after free.\u003cbr\u003e\u003cbr\u003eImpact summary: A malicious QUIC server can cause a heap-use-after-free read\u003cbr\u003ein the OpenSSL QUIC client. The server can also identify one allocator-adjacent\u003cbr\u003ebyte through the client\u0027s protected Handshake response.\u003cbr\u003e\u003cbr\u003eCWE: CWE-416: Use After Free\u003cbr\u003e\u003cbr\u003eDescription: During CRYPTO stream processing, a pointer into the first frame\u0027s\u003cbr\u003ememory on the stream is lent to the TLS handshake processing. The memory\u003cbr\u003emust remain stable until it is processed and released. However the processing\u003cbr\u003eof retransmitted CRYPTO frames could release the memory if the retransmitted\u003cbr\u003eframe fully overlapped the existing frame. This then causes use-after-free read\u003cbr\u003ewhen the TLS handshake processing continues.\u003cbr\u003e\u003cbr\u003eThe use-after-free read can lead to a Denial-of-Service of the client\u003cbr\u003eapplication or a minor leak of information about the heap memory contents\u003cbr\u003ethat might be overwritten with other data, subsequently allocated by\u003cbr\u003ethe application, to the peer.\u003cbr\u003e\u003cbr\u003eFIPS impact: no\u003cbr\u003eThe FIPS module is not affected as the QUIC implementation is outside of\u003cbr\u003ethe OpenSSL FIPS module boundary."
}
],
"value": "Issue summary: A retransmitted QUIC CRYPTO frame can release packet storage\nwhile the TLS record layer retains a direct pointer into that storage causing\nuse after free.\n\nImpact summary: A malicious QUIC server can cause a heap-use-after-free read\nin the OpenSSL QUIC client. The server can also identify one allocator-adjacent\nbyte through the client\u0027s protected Handshake response.\n\nCWE: CWE-416: Use After Free\n\nDescription: During CRYPTO stream processing, a pointer into the first frame\u0027s\nmemory on the stream is lent to the TLS handshake processing. The memory\nmust remain stable until it is processed and released. However the processing\nof retransmitted CRYPTO frames could release the memory if the retransmitted\nframe fully overlapped the existing frame. This then causes use-after-free read\nwhen the TLS handshake processing continues.\n\nThe use-after-free read can lead to a Denial-of-Service of the client\napplication or a minor leak of information about the heap memory contents\nthat might be overwritten with other data, subsequently allocated by\nthe application, to the peer.\n\nFIPS impact: no\nThe FIPS module is not affected as the QUIC implementation is outside of\nthe OpenSSL FIPS module boundary."
}
],
"metrics": [
{
"format": "other",
"other": {
"content": {
"text": "Low"
},
"type": "https://openssl-library.org/policies/general/security-policy/"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-416",
"description": "CWE-416 Use After Free",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-10T18:16:03.752Z",
"orgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"shortName": "openssl"
},
"references": [
{
"name": "OpenSSL Advisory",
"tags": [
"vendor-advisory"
],
"url": "https://openssl-library.org/news/secadv/20261110.txt"
},
{
"name": "4.1.1 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/dd90ceb99a3c2ddba336bb4a00be9ebabd84c2a1"
},
{
"name": "4.0.4 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/ec9d4de9d03989b29db5a3d7efdb4c285deaf386"
},
{
"name": "3.5.10 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/f6244675833e097c2429a40d1b206d95385bd42f"
}
],
"source": {
"discovery": "UNKNOWN"
},
"title": "Retransmitted QUIC CRYPTO Frames Can Cause DoS or One-byte Disclosure",
"x_generator": {
"engine": "Vulnogram 0.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"assignerShortName": "openssl",
"cveId": "CVE-2026-95691",
"datePublished": "2026-11-10T18:16:03.752Z",
"dateReserved": "2026-09-22T14:18:48.635Z",
"dateUpdated": "2026-11-16T19:17:17.580Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-88823 (GCVE-0-2026-88823)
Vulnerability from cvelistv5 – Published: 2026-11-10 18:15 – Updated: 2026-11-16 19:14
VLAI
EPSS
VEX
Title
AES-GCM-SIV AAD Forgery After Zero-length Incremental AAD Update
Summary
Issue summary: The AES-GCM-SIV implementation treats a zero-length Additional
Authenticated Data (AAD) update as a reset of all the AAD supplied so far,
instead of leaving the AAD unchanged. An application that supplies its AAD in
several fragments, one of which is empty, therefore produces or verifies
messages whose authentication tag does not cover the AAD supplied before
the empty fragment.
Impact summary: Data an application intended to authenticate alongside a
message is silently left unauthenticated. An attacker can forge the AAD of such
a message.
CWE: CWE-325: Missing Cryptographic Step
Description: An application passing AAD in multiple chunks of which some have
zero length will have the previous AAD chunks effectively unauthenticated. Also,
on context re-initialisation, the AAD was not reset, which meant that any AAD
accumulated from the previous context usage were also included in the AAD of the
new message.
The fix makes a zero-length AAD update a no-op and clears any accumulated AAD
whenever the context is re-initialised with a key or a nonce.
A re-initialisation that only changes parameters keeps the AAD.
FIPS impact: no
The FIPS modules are not affected, as AES-GCM-SIV is not a FIPS approved
algorithm and is implemented only in the default provider, outside the
OpenSSL FIPS module boundary.
Severity
7.5 (High)
SSVC
Exploitation: none
Automatable: yes
Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-16 19:14 UTC
CWE
- CWE-325 - Missing Cryptographic Step
Assigner
References
4 references
Impacted products
Date Public
2026-11-10 11:05
{
"containers": {
"adp": [
{
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
"version": "3.1"
}
},
{
"other": {
"content": {
"id": "CVE-2026-88823",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-16T19:14:15.207846Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-16T19:14:47.256Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "OpenSSL",
"vendor": "OpenSSL",
"versions": [
{
"lessThan": "4.1.1",
"status": "affected",
"version": "4.1.0",
"versionType": "semver"
},
{
"lessThan": "4.0.4",
"status": "affected",
"version": "4.0.0",
"versionType": "semver"
},
{
"lessThan": "3.5.10",
"status": "affected",
"version": "3.5.0",
"versionType": "semver"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "J\u00e9r\u00e9my Jean (ANSSI)"
},
{
"lang": "en",
"type": "reporter",
"value": "Bhargava Shastry"
},
{
"lang": "en",
"type": "reporter",
"value": "Jonathan Bateman (Rochester Institute of Technology)"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Daniel Kubec"
}
],
"datePublic": "2026-11-10T11:05:35.000Z",
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "Issue summary: The AES-GCM-SIV implementation treats a zero-length Additional\u003cbr\u003eAuthenticated Data (AAD) update as a reset of all the AAD supplied so far,\u003cbr\u003einstead of leaving the AAD unchanged. An application that supplies its AAD in\u003cbr\u003eseveral fragments, one of which is empty, therefore produces or verifies\u003cbr\u003emessages whose authentication tag does not cover the AAD supplied before\u003cbr\u003ethe empty fragment.\u003cbr\u003e\u003cbr\u003eImpact summary: Data an application intended to authenticate alongside a\u003cbr\u003emessage is silently left unauthenticated. An attacker can forge the AAD of such\u003cbr\u003ea message.\u003cbr\u003e\u003cbr\u003eCWE: CWE-325: Missing Cryptographic Step\u003cbr\u003e\u003cbr\u003eDescription: An application passing AAD in multiple chunks of which some have\u003cbr\u003ezero length will have the previous AAD chunks effectively unauthenticated. Also,\u003cbr\u003eon context re-initialisation, the AAD was not reset, which meant that any AAD\u003cbr\u003eaccumulated from the previous context usage were also included in the AAD of the\u003cbr\u003enew message.\u003cbr\u003e\u003cbr\u003eThe fix makes a zero-length AAD update a no-op and clears any accumulated AAD\u003cbr\u003ewhenever the context is re-initialised with a key or a nonce.\u003cbr\u003eA re-initialisation that only changes parameters keeps the AAD.\u003cbr\u003e\u003cbr\u003eFIPS impact: no\u003cbr\u003eThe FIPS modules are not affected, as AES-GCM-SIV is not a FIPS approved\u003cbr\u003ealgorithm and is implemented only in the default provider, outside the\u003cbr\u003eOpenSSL FIPS module boundary."
}
],
"value": "Issue summary: The AES-GCM-SIV implementation treats a zero-length Additional\nAuthenticated Data (AAD) update as a reset of all the AAD supplied so far,\ninstead of leaving the AAD unchanged. An application that supplies its AAD in\nseveral fragments, one of which is empty, therefore produces or verifies\nmessages whose authentication tag does not cover the AAD supplied before\nthe empty fragment.\n\nImpact summary: Data an application intended to authenticate alongside a\nmessage is silently left unauthenticated. An attacker can forge the AAD of such\na message.\n\nCWE: CWE-325: Missing Cryptographic Step\n\nDescription: An application passing AAD in multiple chunks of which some have\nzero length will have the previous AAD chunks effectively unauthenticated. Also,\non context re-initialisation, the AAD was not reset, which meant that any AAD\naccumulated from the previous context usage were also included in the AAD of the\nnew message.\n\nThe fix makes a zero-length AAD update a no-op and clears any accumulated AAD\nwhenever the context is re-initialised with a key or a nonce.\nA re-initialisation that only changes parameters keeps the AAD.\n\nFIPS impact: no\nThe FIPS modules are not affected, as AES-GCM-SIV is not a FIPS approved\nalgorithm and is implemented only in the default provider, outside the\nOpenSSL FIPS module boundary."
}
],
"metrics": [
{
"format": "other",
"other": {
"content": {
"text": "Low"
},
"type": "https://openssl-library.org/policies/general/security-policy/"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-325",
"description": "CWE-325 Missing Cryptographic Step",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-10T18:15:49.358Z",
"orgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"shortName": "openssl"
},
"references": [
{
"name": "OpenSSL Advisory",
"tags": [
"vendor-advisory"
],
"url": "https://openssl-library.org/news/secadv/20261110.txt"
},
{
"name": "4.1.1 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/6747b1a278816dd7db46438040a70b0b5e5e0a90"
},
{
"name": "4.0.4 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/2f5fc833ff9b5bfe00b32f8b5c74f73c5773c682"
},
{
"name": "3.5.10 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/159e1de0c448d7b9f09ad768c8e141def4aa1eb4"
}
],
"source": {
"discovery": "UNKNOWN"
},
"title": "AES-GCM-SIV AAD Forgery After Zero-length Incremental AAD Update",
"x_generator": {
"engine": "Vulnogram 0.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"assignerShortName": "openssl",
"cveId": "CVE-2026-88823",
"datePublished": "2026-11-10T18:15:49.358Z",
"dateReserved": "2026-09-10T09:08:26.966Z",
"dateUpdated": "2026-11-16T19:14:47.256Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-88822 (GCVE-0-2026-88822)
Vulnerability from cvelistv5 – Published: 2026-11-10 18:15 – Updated: 2026-11-16 19:13
VLAI
EPSS
VEX
Title
QUIC Uses Uninitialized Stack Bytes During Automated Peer Detection
Summary
Issue summary: QUIC, when performing automated peer detection, may allow
uninitialized stack data to leak into the received address which is then used
as the destination for outgoing packets.
Impact summary: Applications using QUIC's automated peer detection mechanism
may receive an invalid address, leading to connection loss and disclosure of
uninitialized stack data to an attacker observing the outgoing network traffic.
CWE: CWE-457 (Use of Uninitialized Variable)
Description: The OpenSSL QUIC stack contains a feature in which, when using an
already connected socket, it will auto-detect the peer address during the SSL
handshake. This feature uses the getpeername() function, passing a buffer of
sufficient length to hold any supported address family, but passes a buffer
length that is only sized such that larger addresses, such as IPv6, cannot be
retrieved. The getpeername() function however, still returns the full address
length, which is accepted as the valid input buffer length, leading to the
address buffer containing uninitialized stack data instead of the actual peer
address. The invalid peer address is then used as destination for the outgoing
packets which leads to a connectivity breakage and a leakage of the
uninitialized stack data to passive network observers.
FIPS impact: no
The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this CVE as
the affected protocol is not implemented in the FIPS module.
Severity
6.5 (Medium)
SSVC
Exploitation: none
Automatable: no
Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-16 19:12 UTC
CWE
- CWE-457 - Use of Uninitialized Variable
Assigner
References
4 references
Impacted products
Date Public
2026-11-10 11:00
{
"containers": {
"adp": [
{
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "ADJACENT_NETWORK",
"availabilityImpact": "NONE",
"baseScore": 6.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "HIGH",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"version": "3.1"
}
},
{
"other": {
"content": {
"id": "CVE-2026-88822",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-16T19:12:36.825108Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-16T19:13:15.341Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "OpenSSL",
"vendor": "OpenSSL",
"versions": [
{
"lessThan": "4.1.1",
"status": "affected",
"version": "4.1.0",
"versionType": "semver"
},
{
"lessThan": "4.0.4",
"status": "affected",
"version": "4.0.0",
"versionType": "semver"
},
{
"lessThan": "3.5.10",
"status": "affected",
"version": "3.5.0",
"versionType": "semver"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "Jaehun Lee"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Neil Horman"
}
],
"datePublic": "2026-11-10T11:00:00.000Z",
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "Issue summary: QUIC, when performing automated peer detection, may allow\u003cbr\u003euninitialized stack data to leak into the received address which is then used\u003cbr\u003eas the destination for outgoing packets.\u003cbr\u003e\u003cbr\u003eImpact summary: Applications using QUIC\u0027s automated peer detection mechanism\u003cbr\u003emay receive an invalid address, leading to connection loss and disclosure of\u003cbr\u003euninitialized stack data to an attacker observing the outgoing network traffic.\u003cbr\u003e\u003cbr\u003eCWE: CWE-457 (Use of Uninitialized Variable)\u003cbr\u003e\u003cbr\u003eDescription: The OpenSSL QUIC stack contains a feature in which, when using an\u003cbr\u003ealready connected socket, it will auto-detect the peer address during the SSL\u003cbr\u003ehandshake. This feature uses the getpeername() function, passing a buffer of\u003cbr\u003esufficient length to hold any supported address family, but passes a buffer\u003cbr\u003elength that is only sized such that larger addresses, such as IPv6, cannot be\u003cbr\u003eretrieved. The getpeername() function however, still returns the full address\u003cbr\u003elength, which is accepted as the valid input buffer length, leading to the\u003cbr\u003eaddress buffer containing uninitialized stack data instead of the actual peer\u003cbr\u003eaddress. The invalid peer address is then used as destination for the outgoing\u003cbr\u003epackets which leads to a connectivity breakage and a leakage of the\u003cbr\u003euninitialized stack data to passive network observers.\u003cbr\u003e\u003cbr\u003eFIPS impact: no\u003cbr\u003eThe FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this CVE as\u003cbr\u003ethe affected protocol is not implemented in the FIPS module."
}
],
"value": "Issue summary: QUIC, when performing automated peer detection, may allow\nuninitialized stack data to leak into the received address which is then used\nas the destination for outgoing packets.\n\nImpact summary: Applications using QUIC\u0027s automated peer detection mechanism\nmay receive an invalid address, leading to connection loss and disclosure of\nuninitialized stack data to an attacker observing the outgoing network traffic.\n\nCWE: CWE-457 (Use of Uninitialized Variable)\n\nDescription: The OpenSSL QUIC stack contains a feature in which, when using an\nalready connected socket, it will auto-detect the peer address during the SSL\nhandshake. This feature uses the getpeername() function, passing a buffer of\nsufficient length to hold any supported address family, but passes a buffer\nlength that is only sized such that larger addresses, such as IPv6, cannot be\nretrieved. The getpeername() function however, still returns the full address\nlength, which is accepted as the valid input buffer length, leading to the\naddress buffer containing uninitialized stack data instead of the actual peer\naddress. The invalid peer address is then used as destination for the outgoing\npackets which leads to a connectivity breakage and a leakage of the\nuninitialized stack data to passive network observers.\n\nFIPS impact: no\nThe FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this CVE as\nthe affected protocol is not implemented in the FIPS module."
}
],
"metrics": [
{
"format": "other",
"other": {
"content": {
"text": "Low"
},
"type": "https://openssl-library.org/policies/general/security-policy/"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-457",
"description": "Use of Uninitialized Variable",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-10T18:15:38.961Z",
"orgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"shortName": "openssl"
},
"references": [
{
"name": "OpenSSL Advisory",
"tags": [
"vendor-advisory"
],
"url": "https://openssl-library.org/news/secadv/20261110.txt"
},
{
"name": "4.1.1 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/7b4f5344aa0401e7b777640050b5257ed2a70e88"
},
{
"name": "4.0.4 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/911eee8eb7550b95a206f1ad8cbdb986098982f3"
},
{
"name": "3.5.10 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/1a73dc590cbad62d6f0329ea4779eadaa8d8fd75"
}
],
"source": {
"discovery": "UNKNOWN"
},
"title": "QUIC Uses Uninitialized Stack Bytes During Automated Peer Detection",
"x_generator": {
"engine": "Vulnogram 0.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"assignerShortName": "openssl",
"cveId": "CVE-2026-88822",
"datePublished": "2026-11-10T18:15:38.961Z",
"dateReserved": "2026-09-10T09:08:26.966Z",
"dateUpdated": "2026-11-16T19:13:15.341Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-107496 (GCVE-0-2026-107496)
Vulnerability from cvelistv5 – Published: 2026-11-10 18:14 – Updated: 2026-11-16 19:11
VLAI
EPSS
VEX
Title
Infinite Loop in CMS_encrypt() With an EC Group Order of 1
Summary
Issue summary: Encrypting a CMS message to an EC certificate whose group order
is 1 may cause CMS_encrypt() or CMS_encrypt_ex() to loop indefinitely.
Impact summary: An attacker able to supply the recipient certificate to an
application performing CMS encryption can cause that application to loop
indefinitely, consuming CPU and resulting in Denial of Service.
CWE: CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop')
Description: CMS_encrypt() and CMS_encrypt_ex() encrypt a message to one or
more recipient certificates and, for an EC recipient, generate an ephemeral
key in the recipient's group. If the certificate declares a group order of 1,
random scalar generation can only produce zero. The key generation routine
then retries without limit while waiting for a nonzero private scalar, so the
call never returns.
The OpenSSL TLS and QUIC implementations do not use this path. An application
is exposed only if it calls CMS_encrypt() or CMS_encrypt_ex() with a recipient
certificate whose EC parameters are attacker-controlled. Certificates with
normal EC group orders do not trigger the loop.
OpenSSL 4.0 and later reject unknown explicit EC groups in default builds.
These versions are affected only when configured with the
enable-ec_explicit_curves option.
The result is a hang that consumes a CPU core until the process is
interrupted, a Denial of Service. The severity is Low because the attacker
must supply the recipient certificate and the application must choose to
encrypt to it; ordinary CMS encryption to trusted recipients is unaffected.
The fix makes EC key generation fail when the group has no valid nonzero
private scalar, instead of retrying indefinitely.
FIPS impact: no
The FIPS modules in 4.1, 4.0, 3.5 and 3.0 are not affected. The FIPS provider
does not support arbitrary explicit EC domain parameters, so an order-1 group
is rejected during key import before the vulnerable key generation path is
reached.
Severity
7.5 (High)
SSVC
Exploitation: none
Automatable: yes
Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-16 19:10 UTC
CWE
- CWE-835 - Loop with Unreachable Exit Condition ('Infinite Loop')
Assigner
References
4 references
Impacted products
Date Public
2026-11-10 11:00
{
"containers": {
"adp": [
{
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
}
},
{
"other": {
"content": {
"id": "CVE-2026-107496",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-16T19:10:30.589109Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-16T19:11:29.337Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "OpenSSL",
"vendor": "OpenSSL",
"versions": [
{
"lessThan": "4.1.1",
"status": "affected",
"version": "4.1.0",
"versionType": "semver"
},
{
"lessThan": "4.0.4",
"status": "affected",
"version": "4.0.0",
"versionType": "semver"
},
{
"lessThan": "3.5.10",
"status": "affected",
"version": "3.5.0",
"versionType": "semver"
},
{
"lessThan": "3.0.24",
"status": "affected",
"version": "3.0.0",
"versionType": "semver"
},
{
"lessThan": "1.1.1zk",
"status": "affected",
"version": "1.1.1",
"versionType": "custom"
},
{
"lessThan": "1.0.2zt",
"status": "affected",
"version": "1.0.2",
"versionType": "custom"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "Yinxi Liu"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Jakub Zelenka"
}
],
"datePublic": "2026-11-10T11:00:00.000Z",
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "Issue summary: Encrypting a CMS message to an EC certificate whose group order\u003cbr\u003eis 1 may cause CMS_encrypt() or CMS_encrypt_ex() to loop indefinitely.\u003cbr\u003e\u003cbr\u003eImpact summary: An attacker able to supply the recipient certificate to an\u003cbr\u003eapplication performing CMS encryption can cause that application to loop\u003cbr\u003eindefinitely, consuming CPU and resulting in Denial of Service.\u003cbr\u003e\u003cbr\u003eCWE: CWE-835: Loop with Unreachable Exit Condition (\u0027Infinite Loop\u0027)\u003cbr\u003e\u003cbr\u003eDescription: CMS_encrypt() and CMS_encrypt_ex() encrypt a message to one or\u003cbr\u003emore recipient certificates and, for an EC recipient, generate an ephemeral\u003cbr\u003ekey in the recipient\u0027s group. If the certificate declares a group order of 1,\u003cbr\u003erandom scalar generation can only produce zero. The key generation routine\u003cbr\u003ethen retries without limit while waiting for a nonzero private scalar, so the\u003cbr\u003ecall never returns.\u003cbr\u003e\u003cbr\u003eThe OpenSSL TLS and QUIC implementations do not use this path. An application\u003cbr\u003eis exposed only if it calls CMS_encrypt() or CMS_encrypt_ex() with a recipient\u003cbr\u003ecertificate whose EC parameters are attacker-controlled. Certificates with\u003cbr\u003enormal EC group orders do not trigger the loop.\u003cbr\u003e\u003cbr\u003eOpenSSL 4.0 and later reject unknown explicit EC groups in default builds.\u003cbr\u003eThese versions are affected only when configured with the\u003cbr\u003eenable-ec_explicit_curves option.\u003cbr\u003e\u003cbr\u003eThe result is a hang that consumes a CPU core until the process is\u003cbr\u003einterrupted, a Denial of Service. The severity is Low because the attacker\u003cbr\u003emust supply the recipient certificate and the application must choose to\u003cbr\u003eencrypt to it; ordinary CMS encryption to trusted recipients is unaffected.\u003cbr\u003e\u003cbr\u003eThe fix makes EC key generation fail when the group has no valid nonzero\u003cbr\u003eprivate scalar, instead of retrying indefinitely.\u003cbr\u003e\u003cbr\u003eFIPS impact: no\u003cbr\u003eThe FIPS modules in 4.1, 4.0, 3.5 and 3.0 are not affected. The FIPS provider\u003cbr\u003edoes not support arbitrary explicit EC domain parameters, so an order-1 group\u003cbr\u003eis rejected during key import before the vulnerable key generation path is\u003cbr\u003ereached."
}
],
"value": "Issue summary: Encrypting a CMS message to an EC certificate whose group order\nis 1 may cause CMS_encrypt() or CMS_encrypt_ex() to loop indefinitely.\n\nImpact summary: An attacker able to supply the recipient certificate to an\napplication performing CMS encryption can cause that application to loop\nindefinitely, consuming CPU and resulting in Denial of Service.\n\nCWE: CWE-835: Loop with Unreachable Exit Condition (\u0027Infinite Loop\u0027)\n\nDescription: CMS_encrypt() and CMS_encrypt_ex() encrypt a message to one or\nmore recipient certificates and, for an EC recipient, generate an ephemeral\nkey in the recipient\u0027s group. If the certificate declares a group order of 1,\nrandom scalar generation can only produce zero. The key generation routine\nthen retries without limit while waiting for a nonzero private scalar, so the\ncall never returns.\n\nThe OpenSSL TLS and QUIC implementations do not use this path. An application\nis exposed only if it calls CMS_encrypt() or CMS_encrypt_ex() with a recipient\ncertificate whose EC parameters are attacker-controlled. Certificates with\nnormal EC group orders do not trigger the loop.\n\nOpenSSL 4.0 and later reject unknown explicit EC groups in default builds.\nThese versions are affected only when configured with the\nenable-ec_explicit_curves option.\n\nThe result is a hang that consumes a CPU core until the process is\ninterrupted, a Denial of Service. The severity is Low because the attacker\nmust supply the recipient certificate and the application must choose to\nencrypt to it; ordinary CMS encryption to trusted recipients is unaffected.\n\nThe fix makes EC key generation fail when the group has no valid nonzero\nprivate scalar, instead of retrying indefinitely.\n\nFIPS impact: no\nThe FIPS modules in 4.1, 4.0, 3.5 and 3.0 are not affected. The FIPS provider\ndoes not support arbitrary explicit EC domain parameters, so an order-1 group\nis rejected during key import before the vulnerable key generation path is\nreached."
}
],
"metrics": [
{
"format": "other",
"other": {
"content": {
"text": "Low"
},
"type": "https://openssl-library.org/policies/general/security-policy/"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-835",
"description": "CWE-835 Loop with Unreachable Exit Condition (\u0027Infinite Loop\u0027)",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-10T18:14:18.207Z",
"orgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"shortName": "openssl"
},
"references": [
{
"name": "OpenSSL Advisory",
"tags": [
"vendor-advisory"
],
"url": "https://openssl-library.org/news/secadv/20261110.txt"
},
{
"name": "4.1.1 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/36e15b618decdff1b116eead6747718e6e729ad2"
},
{
"name": "4.0.4 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/a8531368ddb1f86d2a2782a8b693926bb67b59e7"
},
{
"name": "3.5.10 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/a0051cfe699bf5a047bc1c4faef65f80f7987366"
}
],
"source": {
"discovery": "UNKNOWN"
},
"title": "Infinite Loop in CMS_encrypt() With an EC Group Order of 1",
"x_generator": {
"engine": "Vulnogram 0.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"assignerShortName": "openssl",
"cveId": "CVE-2026-107496",
"datePublished": "2026-11-10T18:14:18.207Z",
"dateReserved": "2026-10-08T08:31:36.278Z",
"dateUpdated": "2026-11-16T19:11:29.337Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CERTFR-2026-AVI-1554
Vulnerability from certfr_avis - Published: 2026-11-17 - Updated: 2026-11-17
De multiples vulnérabilités ont été découvertes dans OpenSSL. Elles permettent à un attaquant de provoquer un déni de service à distance.
Solutions
Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
Impacted products
References
| Title | Publication Time | Tags | |||
|---|---|---|---|---|---|
|
|||||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [
{
"description": "OpenSSL versions 3.5.x ant\u00e9rieures \u00e0 3.5.10",
"product": {
"name": "OpenSSL",
"vendor": {
"name": "OpenSSL",
"scada": false
}
}
},
{
"description": "OpenSSL versions 4.0.x ant\u00e9rieures \u00e0 4.0.4",
"product": {
"name": "OpenSSL",
"vendor": {
"name": "OpenSSL",
"scada": false
}
}
},
{
"description": "OpenSSL versions 4.1.x ant\u00e9rieures \u00e0 4.1.1",
"product": {
"name": "OpenSSL",
"vendor": {
"name": "OpenSSL",
"scada": false
}
}
}
],
"affected_systems_content": "",
"content": "## Solutions\n\nSe r\u00e9f\u00e9rer au bulletin de s\u00e9curit\u00e9 de l\u0027\u00e9diteur pour l\u0027obtention des correctifs (cf. section Documentation).",
"cves": [
{
"name": "CVE-2026-124709",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-124709"
},
{
"name": "CVE-2026-35190",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-35190"
},
{
"name": "CVE-2026-107493",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-107493"
}
],
"initial_release_date": "2026-11-17T00:00:00",
"last_revision_date": "2026-11-17T00:00:00",
"links": [],
"reference": "CERTFR-2026-AVI-1554",
"revisions": [
{
"description": "Version initiale",
"revision_date": "2026-11-17T00:00:00.000000"
}
],
"risks": [
{
"description": "D\u00e9ni de service \u00e0 distance"
}
],
"summary": "De multiples vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 d\u00e9couvertes dans OpenSSL. Elles permettent \u00e0 un attaquant de provoquer un d\u00e9ni de service \u00e0 distance.",
"title": "Multiples vuln\u00e9rabilit\u00e9s dans OpenSSL",
"vendor_advisories": [
{
"published_at": "2026-11-17",
"title": "Bulletin de s\u00e9curit\u00e9 OpenSSL",
"url": "https://openssl-library.org/news/secadv/20261117.txt"
}
]
}
CERTFR-2026-AVI-1496
Vulnerability from certfr_avis - Published: 2026-11-10 - Updated: 2026-11-10
De multiples vulnérabilités ont été découvertes dans OpenSSL. Certaines d'entre elles permettent à un attaquant de provoquer un déni de service à distance, une atteinte à la confidentialité des données et un contournement de la politique de sécurité.
Solutions
Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
Impacted products
| Vendor | Product | Description | ||
|---|---|---|---|---|
| OpenSSL | OpenSSL | OpenSSL versions 3.0.x antérieures à 3.0.24 | ||
| OpenSSL | OpenSSL | OpenSSL versions 1.1.1x antérieures à 1.1.1zk | ||
| OpenSSL | OpenSSL | OpenSSL versions 3.5.x antérieures à 3.5.10 | ||
| OpenSSL | OpenSSL | OpenSSL versions 1.0.2x antérieures à 1.0.2zt | ||
| OpenSSL | OpenSSL | OpenSSL versions 4.0.x antérieures à 4.0.4 | ||
| OpenSSL | OpenSSL | OpenSSL versions 4.1.x antérieures à 4.1.1 |
References
| Title | Publication Time | Tags | |||
|---|---|---|---|---|---|
|
|||||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [
{
"description": "OpenSSL versions 3.0.x ant\u00e9rieures \u00e0 3.0.24",
"product": {
"name": "OpenSSL",
"vendor": {
"name": "OpenSSL",
"scada": false
}
}
},
{
"description": "OpenSSL versions 1.1.1x ant\u00e9rieures \u00e0 1.1.1zk",
"product": {
"name": "OpenSSL",
"vendor": {
"name": "OpenSSL",
"scada": false
}
}
},
{
"description": "OpenSSL versions 3.5.x ant\u00e9rieures \u00e0 3.5.10",
"product": {
"name": "OpenSSL",
"vendor": {
"name": "OpenSSL",
"scada": false
}
}
},
{
"description": "OpenSSL versions 1.0.2x ant\u00e9rieures \u00e0 1.0.2zt",
"product": {
"name": "OpenSSL",
"vendor": {
"name": "OpenSSL",
"scada": false
}
}
},
{
"description": "OpenSSL versions 4.0.x ant\u00e9rieures \u00e0 4.0.4",
"product": {
"name": "OpenSSL",
"vendor": {
"name": "OpenSSL",
"scada": false
}
}
},
{
"description": "OpenSSL versions 4.1.x ant\u00e9rieures \u00e0 4.1.1",
"product": {
"name": "OpenSSL",
"vendor": {
"name": "OpenSSL",
"scada": false
}
}
}
],
"affected_systems_content": "",
"content": "## Solutions\n\nSe r\u00e9f\u00e9rer au bulletin de s\u00e9curit\u00e9 de l\u0027\u00e9diteur pour l\u0027obtention des correctifs (cf. section Documentation).",
"cves": [
{
"name": "CVE-2026-95692",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-95692"
},
{
"name": "CVE-2026-88822",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-88822"
},
{
"name": "CVE-2026-88823",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-88823"
},
{
"name": "CVE-2026-95691",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-95691"
},
{
"name": "CVE-2026-107496",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-107496"
}
],
"initial_release_date": "2026-11-10T00:00:00",
"last_revision_date": "2026-11-10T00:00:00",
"links": [],
"reference": "CERTFR-2026-AVI-1496",
"revisions": [
{
"description": "Version initiale",
"revision_date": "2026-11-10T00:00:00.000000"
}
],
"risks": [
{
"description": "D\u00e9ni de service \u00e0 distance"
},
{
"description": "Contournement de la politique de s\u00e9curit\u00e9"
},
{
"description": "Atteinte \u00e0 la confidentialit\u00e9 des donn\u00e9es"
}
],
"summary": "De multiples vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 d\u00e9couvertes dans OpenSSL. Certaines d\u0027entre elles permettent \u00e0 un attaquant de provoquer un d\u00e9ni de service \u00e0 distance, une atteinte \u00e0 la confidentialit\u00e9 des donn\u00e9es et un contournement de la politique de s\u00e9curit\u00e9.",
"title": "Multiples vuln\u00e9rabilit\u00e9s dans OpenSSL",
"vendor_advisories": [
{
"published_at": "2026-11-10",
"title": "Bulletin de s\u00e9curit\u00e9 OpenSSL",
"url": "https://openssl-library.org/news/secadv/20261110.txt"
}
]
}
GCVE-1988-2026-0540
Vulnerability from gna-1988 – Published: 2026-11-02 10:03 – Updated: 2026-11-02 10:03
VLAI
EPSS
VEX
Title
[Bugtraq] [SECURITY] [DSA 6531-1] openssl security update
Summary
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
- -------------------------------------------------------------------------
Debian Security Advisory DSA-6531-1 security@debian.org
https://www.debian.org/security/ Salvatore Bonaccorso
September 30, 2026 https://www.debian.org/security/faq
- -------------------------------------------------------------------------
Package : openssl
CVE ID : CVE-2026-35189 CVE-2026-35191 CVE-2026-42772 CVE-2026-54872
CVE-2026-54873 CVE-2026-54875 CVE-2026-72897 CVE-2026-75804
CVE-2026-75805 CVE-2026-75806 CVE-2026-77696 CVE-2026-84782
CVE-2026-84784
Multiple vulnerabilities have been discovered in OpenSSL, a Secure
Sockets Layer toolkit, which could result in denial of service,
information disclosure or potentially recovery of private keys.
Additional details can be found in the upstream advisories:
https://openssl-library.org/news/secadv/20260929.txt
For the stable distribution (trixie), these problems have been fixed in
version 3.5.7-1~deb13u3.
We recommend that you upgrade your openssl packages.
For the detailed security status of openssl please refer to its security
tracker page at:
https://security-tracker.debian.org/tracker/openssl
Further information about Debian Security Advisories, how to apply
these updates to your system and frequently asked questions can be
found at: https://www.debian.org/security/
Mailing list: debian-security-announce@lists.debian.org
-----BEGIN PGP SIGNATURE-----
iQKTBAEBCgB9FiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmq8pmxfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQACgkQBUy48xND
z0R1Hg//av61un8iGouMa0xpTCL+lxgx5QQScEvZ+PJileOLB3gwANP9LVDmGNSV
0x7nzd/WHsrIpswEuYzhlJxRC5f41y4fbM/98IKl+lBXoqZHatMvin0tII+SrfFI
Oimt8I1V8swT9aFZG5voZTiEbkhxLYH5MwF+CDF1VTBksHwaKU0SR1lp+MhEGlYA
kOhU5g47PzMHQ7tBO57/M/HjXp/9YJY6e2M8V+c+cT7LLcO5Tk06czx6XqU/dJHL
zeBNfiJ8L8OzTBoqFjZe3h4ee1X5zdDX4XDVs00yHnh8FmLpaQ1XDJeBrEYpq5TY
4sqFC1LXjK+gW+DoJ7CtWzya3nrPZA9TriPBKb51qIyevPAmIureKStwM+RTB80S
N00xCDYIWljw41ijLhtWCn5WKCZehwknOipWSJMZox428DnqJgiawsmoUOvXZhtd
rVM7RoR9pJIMXQIarmRTy5CZU6Ajo6ON7gxRZOa/qZBaBtQaeGreDlPjMkX6GPfu
Tx005K6R+bepTKy4myT06UwES1k8JYVXz6AJyEzXGIHs41B+Wo9+82ACyb1viJit
pVu+nALQ/Qgx1K6wHx23LQ5yyAEbzSfRPEqGYlJ6pY5PsT1hg10t/54vv6ss/5lg
LQUupWBf2JQwpRzJTnMN0xVDnJSL+CArB/uumd4sNCYv1dTup+Y=
=7/5m
-----END PGP SIGNATURE-----
Severity
No CVSS data available.
Assigner
References
6 references
Impacted products
1 product
| Vendor | Product | Version | |
|---|---|---|---|
| Openssl | security update |
Affected:
unknown
|
Relationships
reference
GCVE-1988-2026-0540 (this record)
- related CVE-2026-35189
- related CVE-2026-35191
- related CVE-2026-42772
- related CVE-2026-54872
- related CVE-2026-54873
- related CVE-2026-54875
- related CVE-2026-72897
- related CVE-2026-75804
- related CVE-2026-75805
- related CVE-2026-75806
- related CVE-2026-77696
- related CVE-2026-84782
- related CVE-2026-84784
{
"containers": {
"cna": {
"affected": [
{
"product": "security update",
"vendor": "Openssl",
"versions": [
{
"status": "affected",
"version": "unknown"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Salvatore Bonaccorso"
}
],
"descriptions": [
{
"lang": "en",
"value": "-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA512\n- -------------------------------------------------------------------------\nDebian Security Advisory DSA-6531-1 security@debian.org\nhttps://www.debian.org/security/ Salvatore Bonaccorso\nSeptember 30, 2026 https://www.debian.org/security/faq\n- -------------------------------------------------------------------------\nPackage : openssl\nCVE ID : CVE-2026-35189 CVE-2026-35191 CVE-2026-42772 CVE-2026-54872\nCVE-2026-54873 CVE-2026-54875 CVE-2026-72897 CVE-2026-75804\nCVE-2026-75805 CVE-2026-75806 CVE-2026-77696 CVE-2026-84782\nCVE-2026-84784\nMultiple vulnerabilities have been discovered in OpenSSL, a Secure\nSockets Layer toolkit, which could result in denial of service,\ninformation disclosure or potentially recovery of private keys.\nAdditional details can be found in the upstream advisories:\nhttps://openssl-library.org/news/secadv/20260929.txt\nFor the stable distribution (trixie), these problems have been fixed in\nversion 3.5.7-1~deb13u3.\nWe recommend that you upgrade your openssl packages.\nFor the detailed security status of openssl please refer to its security\ntracker page at:\nhttps://security-tracker.debian.org/tracker/openssl\nFurther information about Debian Security Advisories, how to apply\nthese updates to your system and frequently asked questions can be\nfound at: https://www.debian.org/security/\nMailing list: debian-security-announce@lists.debian.org\n-----BEGIN PGP SIGNATURE-----\niQKTBAEBCgB9FiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmq8pmxfFIAAAAAALgAo\naXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2\nNDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQACgkQBUy48xND\nz0R1Hg//av61un8iGouMa0xpTCL+lxgx5QQScEvZ+PJileOLB3gwANP9LVDmGNSV\n0x7nzd/WHsrIpswEuYzhlJxRC5f41y4fbM/98IKl+lBXoqZHatMvin0tII+SrfFI\nOimt8I1V8swT9aFZG5voZTiEbkhxLYH5MwF+CDF1VTBksHwaKU0SR1lp+MhEGlYA\nkOhU5g47PzMHQ7tBO57/M/HjXp/9YJY6e2M8V+c+cT7LLcO5Tk06czx6XqU/dJHL\nzeBNfiJ8L8OzTBoqFjZe3h4ee1X5zdDX4XDVs00yHnh8FmLpaQ1XDJeBrEYpq5TY\n4sqFC1LXjK+gW+DoJ7CtWzya3nrPZA9TriPBKb51qIyevPAmIureKStwM+RTB80S\nN00xCDYIWljw41ijLhtWCn5WKCZehwknOipWSJMZox428DnqJgiawsmoUOvXZhtd\nrVM7RoR9pJIMXQIarmRTy5CZU6Ajo6ON7gxRZOa/qZBaBtQaeGreDlPjMkX6GPfu\nTx005K6R+bepTKy4myT06UwES1k8JYVXz6AJyEzXGIHs41B+Wo9+82ACyb1viJit\npVu+nALQ/Qgx1K6wHx23LQ5yyAEbzSfRPEqGYlJ6pY5PsT1hg10t/54vv6ss/5lg\nLQUupWBf2JQwpRzJTnMN0xVDnJSL+CArB/uumd4sNCYv1dTup+Y=\n=7/5m\n-----END PGP SIGNATURE-----"
}
],
"providerMetadata": {
"dateUpdated": "2026-11-02T10:03:01Z",
"orgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
"shortName": "VULNARCHIVE"
},
"references": [
{
"tags": [
"technical-description"
],
"url": "https://vuln.freearchive.org/archive/item/01a9ee1ffbf14934dbe51fdad43c8d6576563e4bbad6651ba0d380538bd7c266"
},
{
"tags": [
"technical-description"
],
"url": "https://lists.securityfocus.com/hyperkitty/list/bugtraq@securityfocus.com/message/VBF6OGQJZYX76I55ZYFJSRDFQX2BZCZ6/"
},
{
"url": "https://openssl-library.org/news/secadv/20260929.txt"
},
{
"url": "https://security-tracker.debian.org/tracker/openssl"
},
{
"url": "https://www.debian.org/security/"
},
{
"url": "https://www.debian.org/security/faq"
}
],
"source": {
"defect": [
"E1xBnVs-00000000ll9-1gGZ%40seger.debian.org"
],
"discovery": "EXTERNAL"
},
"title": "[Bugtraq] [SECURITY] [DSA 6531-1] openssl security update",
"x_gcve": [
{
"recordType": "reference",
"relationships": [
{
"destId": "CVE-2026-35189",
"type": "related"
},
{
"destId": "CVE-2026-35191",
"type": "related"
},
{
"destId": "CVE-2026-42772",
"type": "related"
},
{
"destId": "CVE-2026-54872",
"type": "related"
},
{
"destId": "CVE-2026-54873",
"type": "related"
},
{
"destId": "CVE-2026-54875",
"type": "related"
},
{
"destId": "CVE-2026-72897",
"type": "related"
},
{
"destId": "CVE-2026-75804",
"type": "related"
},
{
"destId": "CVE-2026-75805",
"type": "related"
},
{
"destId": "CVE-2026-75806",
"type": "related"
},
{
"destId": "CVE-2026-77696",
"type": "related"
},
{
"destId": "CVE-2026-84782",
"type": "related"
},
{
"destId": "CVE-2026-84784",
"type": "related"
}
],
"vulnId": "GCVE-1988-2026-0540",
"x_vulnarchive": {
"archiveUrl": "https://vuln.freearchive.org/archive/item/01a9ee1ffbf14934dbe51fdad43c8d6576563e4bbad6651ba0d380538bd7c266",
"automated": true,
"contentSha256": "01a9ee1ffbf14934dbe51fdad43c8d6576563e4bbad6651ba0d380538bd7c266",
"evidenceScore": 6,
"messageId": "E1xBnVs-00000000ll9-1gGZ%40seger.debian.org",
"originalUrl": "https://lists.securityfocus.com/hyperkitty/list/bugtraq@securityfocus.com/message/VBF6OGQJZYX76I55ZYFJSRDFQX2BZCZ6/",
"policy": "vulnarchive-1",
"sourceFormat": "text/html",
"sourcePublishedAt": "2026-11-02T10:03:01Z"
}
},
{
"recordType": "advisory",
"vulnId": "gcve-1988-2026-0540"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
"assignerShortName": "VULNARCHIVE",
"datePublished": "2026-11-02T10:03:01Z",
"dateUpdated": "2026-11-02T10:03:01Z",
"state": "PUBLISHED",
"vulnId": "GCVE-1988-2026-0540"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
GCVE-1988-2026-0536
Vulnerability from gna-1988 – Published: 2026-11-02 10:02 – Updated: 2026-11-02 10:02
VLAI
EPSS
VEX
Title
[Bugtraq] [SECURITY] [DSA 6465-1] openssl security update
Summary
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
- -------------------------------------------------------------------------
Debian Security Advisory DSA-6465-1 security@debian.org
https://www.debian.org/security/ Salvatore Bonaccorso
August 25, 2026 https://www.debian.org/security/faq
- -------------------------------------------------------------------------
Package : openssl
CVE ID : CVE-2026-14456 CVE-2026-14457 CVE-2026-18798 CVE-2026-54874
CVE-2026-63072 CVE-2026-63073 CVE-2026-63074 CVE-2026-63075
CVE-2026-63076 CVE-2026-75803
Debian Bug : 1144615 1145172
Multiple vulnerabilities have been discovered in OpenSSL, a Secure
Sockets Layer toolkit, which may result in denial of service.
Additional details can be found in the upstream advisories:
https://openssl-library.org/news/secadv/20260813.txt
https://openssl-library.org/news/secadv/20260825.txt
For the stable distribution (trixie), these problems have been fixed in
version 3.5.7-1~deb13u2.
We recommend that you upgrade your openssl packages.
For the detailed security status of openssl please refer to its security
tracker page at:
https://security-tracker.debian.org/tracker/openssl
Further information about Debian Security Advisories, how to apply
these updates to your system and frequently asked questions can be
found at: https://www.debian.org/security/
Mailing list: debian-security-announce@lists.debian.org
-----BEGIN PGP SIGNATURE-----
iQKTBAEBCgB9FiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmqN5alfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQACgkQBUy48xND
z0QBqRAAlXIilJWwjS0VS1pgroaCFUNGhL1HrTsBIIrnnrWTUOeD19fFLvvcVK5B
j1UaT/jurxSp6Bkre7NrQFzLlXk6xvRWTR2dxv9K1q29lYgPwpVjfO25kdQ2LWeg
0n0qA4Kb394Evtf9lmb3KMNrrRJHc9DmuXZDQWAjsNRwVxBEaJ+yN9Im92CcQQQb
CUgVYzlx+mvBfPTGgStTFJjMXT/pTaVz+WDHbfEc5WM8tRe3YYb+e+/vOdA4jrEv
UKdH1M+fNg1gB7+cCr8QyTQiTMvz2BxwBuI7jlK67FFZL322SqON4chQRXleWp86
imyBANOP4dRdMV1aYGT38VZYjoURwuvLR77ZhyLe1c927YcIkXe11K0HMwq9DeXv
o+TQQTf1qJN8Zd0sQuz88/d6T9jtzRgFvNkZpiXXy3nQrKnE0FAfZuGCyniiie9b
VipvzWLxfpeEH9TW9hotwCVyv395RRaWM6m8UuQI4J+3yVTUY4S+nO4aHo5Wi5HN
WeYxaFZSKYTUlsjAGMgYGm5aH4TtAFoHxzTTzsvvArKPDpFukZH4Ux+t9adydwTZ
KRxmHmEWcLYKchZksLymvOCKrG57LTAqJi+CVi+oJAc23RqYyZy1tEdB8hSQ6s2S
sTk0pcwjB5xk4BZXdDr/8nmqivlfJA3eFDO0K9P/l9CFK280MQw=
=IuuF
-----END PGP SIGNATURE-----
Severity
No CVSS data available.
Assigner
References
7 references
Impacted products
1 product
| Vendor | Product | Version | |
|---|---|---|---|
| Openssl | security update |
Affected:
unknown
|
Relationships
reference
GCVE-1988-2026-0536 (this record)
- related CVE-2026-14456
- related CVE-2026-14457
- related CVE-2026-18798
- related CVE-2026-54874
- related CVE-2026-63072
- related CVE-2026-63073
- related CVE-2026-63074
- related CVE-2026-63075
- related CVE-2026-63076
- related CVE-2026-75803
{
"containers": {
"cna": {
"affected": [
{
"product": "security update",
"vendor": "Openssl",
"versions": [
{
"status": "affected",
"version": "unknown"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Salvatore Bonaccorso"
}
],
"descriptions": [
{
"lang": "en",
"value": "-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA512\n- -------------------------------------------------------------------------\nDebian Security Advisory DSA-6465-1 security@debian.org\nhttps://www.debian.org/security/ Salvatore Bonaccorso\nAugust 25, 2026 https://www.debian.org/security/faq\n- -------------------------------------------------------------------------\nPackage : openssl\nCVE ID : CVE-2026-14456 CVE-2026-14457 CVE-2026-18798 CVE-2026-54874\nCVE-2026-63072 CVE-2026-63073 CVE-2026-63074 CVE-2026-63075\nCVE-2026-63076 CVE-2026-75803\nDebian Bug : 1144615 1145172\nMultiple vulnerabilities have been discovered in OpenSSL, a Secure\nSockets Layer toolkit, which may result in denial of service.\nAdditional details can be found in the upstream advisories:\nhttps://openssl-library.org/news/secadv/20260813.txt\nhttps://openssl-library.org/news/secadv/20260825.txt\nFor the stable distribution (trixie), these problems have been fixed in\nversion 3.5.7-1~deb13u2.\nWe recommend that you upgrade your openssl packages.\nFor the detailed security status of openssl please refer to its security\ntracker page at:\nhttps://security-tracker.debian.org/tracker/openssl\nFurther information about Debian Security Advisories, how to apply\nthese updates to your system and frequently asked questions can be\nfound at: https://www.debian.org/security/\nMailing list: debian-security-announce@lists.debian.org\n-----BEGIN PGP SIGNATURE-----\niQKTBAEBCgB9FiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmqN5alfFIAAAAAALgAo\naXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2\nNDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQACgkQBUy48xND\nz0QBqRAAlXIilJWwjS0VS1pgroaCFUNGhL1HrTsBIIrnnrWTUOeD19fFLvvcVK5B\nj1UaT/jurxSp6Bkre7NrQFzLlXk6xvRWTR2dxv9K1q29lYgPwpVjfO25kdQ2LWeg\n0n0qA4Kb394Evtf9lmb3KMNrrRJHc9DmuXZDQWAjsNRwVxBEaJ+yN9Im92CcQQQb\nCUgVYzlx+mvBfPTGgStTFJjMXT/pTaVz+WDHbfEc5WM8tRe3YYb+e+/vOdA4jrEv\nUKdH1M+fNg1gB7+cCr8QyTQiTMvz2BxwBuI7jlK67FFZL322SqON4chQRXleWp86\nimyBANOP4dRdMV1aYGT38VZYjoURwuvLR77ZhyLe1c927YcIkXe11K0HMwq9DeXv\no+TQQTf1qJN8Zd0sQuz88/d6T9jtzRgFvNkZpiXXy3nQrKnE0FAfZuGCyniiie9b\nVipvzWLxfpeEH9TW9hotwCVyv395RRaWM6m8UuQI4J+3yVTUY4S+nO4aHo5Wi5HN\nWeYxaFZSKYTUlsjAGMgYGm5aH4TtAFoHxzTTzsvvArKPDpFukZH4Ux+t9adydwTZ\nKRxmHmEWcLYKchZksLymvOCKrG57LTAqJi+CVi+oJAc23RqYyZy1tEdB8hSQ6s2S\nsTk0pcwjB5xk4BZXdDr/8nmqivlfJA3eFDO0K9P/l9CFK280MQw=\n=IuuF\n-----END PGP SIGNATURE-----"
}
],
"providerMetadata": {
"dateUpdated": "2026-11-02T10:02:57Z",
"orgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
"shortName": "VULNARCHIVE"
},
"references": [
{
"tags": [
"technical-description"
],
"url": "https://vuln.freearchive.org/archive/item/90780217511ba9473775d7daca7f41ec65f1b70f96cb131ad057bb14544f2f64"
},
{
"tags": [
"technical-description"
],
"url": "https://lists.securityfocus.com/hyperkitty/list/bugtraq@securityfocus.com/message/F67TVJDJLUTSXDZPLED7P57UK4ORENKV/"
},
{
"url": "https://openssl-library.org/news/secadv/20260813.txt"
},
{
"url": "https://openssl-library.org/news/secadv/20260825.txt"
},
{
"url": "https://security-tracker.debian.org/tracker/openssl"
},
{
"url": "https://www.debian.org/security/"
},
{
"url": "https://www.debian.org/security/faq"
}
],
"source": {
"defect": [
"E1wywMA-00000005YZP-0RlG%40seger.debian.org"
],
"discovery": "EXTERNAL"
},
"title": "[Bugtraq] [SECURITY] [DSA 6465-1] openssl security update",
"x_gcve": [
{
"recordType": "reference",
"relationships": [
{
"destId": "CVE-2026-14456",
"type": "related"
},
{
"destId": "CVE-2026-14457",
"type": "related"
},
{
"destId": "CVE-2026-18798",
"type": "related"
},
{
"destId": "CVE-2026-54874",
"type": "related"
},
{
"destId": "CVE-2026-63072",
"type": "related"
},
{
"destId": "CVE-2026-63073",
"type": "related"
},
{
"destId": "CVE-2026-63074",
"type": "related"
},
{
"destId": "CVE-2026-63075",
"type": "related"
},
{
"destId": "CVE-2026-63076",
"type": "related"
},
{
"destId": "CVE-2026-75803",
"type": "related"
}
],
"vulnId": "GCVE-1988-2026-0536",
"x_vulnarchive": {
"archiveUrl": "https://vuln.freearchive.org/archive/item/90780217511ba9473775d7daca7f41ec65f1b70f96cb131ad057bb14544f2f64",
"automated": true,
"contentSha256": "90780217511ba9473775d7daca7f41ec65f1b70f96cb131ad057bb14544f2f64",
"evidenceScore": 6,
"messageId": "E1wywMA-00000005YZP-0RlG%40seger.debian.org",
"originalUrl": "https://lists.securityfocus.com/hyperkitty/list/bugtraq@securityfocus.com/message/F67TVJDJLUTSXDZPLED7P57UK4ORENKV/",
"policy": "vulnarchive-1",
"sourceFormat": "text/html",
"sourcePublishedAt": "2026-11-02T10:02:57Z"
}
},
{
"recordType": "advisory",
"vulnId": "gcve-1988-2026-0536"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
"assignerShortName": "VULNARCHIVE",
"datePublished": "2026-11-02T10:02:57Z",
"dateUpdated": "2026-11-02T10:02:57Z",
"state": "PUBLISHED",
"vulnId": "GCVE-1988-2026-0536"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}