{"grype_matches":[{"artifact":{"id":"633df08c5490c16b","cpes":["cpe:2.3:a:python3-pip-wheel:python3-pip-wheel:21.3.1-2.amzn2023.0.21:*:*:*:*:*:*:*","cpe:2.3:a:python3-pip-wheel:python3_pip_wheel:21.3.1-2.amzn2023.0.21:*:*:*:*:*:*:*","cpe:2.3:a:python3_pip_wheel:python3-pip-wheel:21.3.1-2.amzn2023.0.21:*:*:*:*:*:*:*","cpe:2.3:a:python3_pip_wheel:python3_pip_wheel:21.3.1-2.amzn2023.0.21:*:*:*:*:*:*:*","cpe:2.3:a:amazonlinux:python3-pip-wheel:21.3.1-2.amzn2023.0.21:*:*:*:*:*:*:*","cpe:2.3:a:amazonlinux:python3_pip_wheel:21.3.1-2.amzn2023.0.21:*:*:*:*:*:*:*","cpe:2.3:a:python3-pip:python3-pip-wheel:21.3.1-2.amzn2023.0.21:*:*:*:*:*:*:*","cpe:2.3:a:python3-pip:python3_pip_wheel:21.3.1-2.amzn2023.0.21:*:*:*:*:*:*:*","cpe:2.3:a:python3_pip:python3-pip-wheel:21.3.1-2.amzn2023.0.21:*:*:*:*:*:*:*","cpe:2.3:a:python3_pip:python3_pip_wheel:21.3.1-2.amzn2023.0.21:*:*:*:*:*:*:*","cpe:2.3:a:python3:python3-pip-wheel:21.3.1-2.amzn2023.0.21:*:*:*:*:*:*:*","cpe:2.3:a:python3:python3_pip_wheel:21.3.1-2.amzn2023.0.21:*:*:*:*:*:*:*"],"name":"python3-pip-wheel","purl":"pkg:rpm/amzn/python3-pip-wheel@21.3.1-2.amzn2023.0.21?arch=noarch&distro=amzn-2023&upstream=python-pip-21.3.1-2.amzn2023.0.21.src.rpm","type":"rpm","version":"21.3.1-2.amzn2023.0.21","language":"","licenses":["MIT and Python and ASL 2.0 and BSD and ISC and LGPLv2 and MPLv2.0 and (ASL 2.0 or BSD)"],"metadata":{"epoch":null,"architecture":"noarch","modularityLabel":""},"locations":[{"path":"/var/lib/rpm/rpmdb.sqlite","layerID":"sha256:36ecccff5cdfa790aa570cb6cbe04b052333d62b672dac330d047934181da1ac","accessPath":"/var/lib/rpm/rpmdb.sqlite","annotations":{"evidence":"primary"}}],"upstreams":[{"name":"python-pip","version":"21.3.1-2.amzn2023.0.21"}],"metadataType":"RpmMetadata"},"matchDetails":[{"fix":{"suggestedVersion":"21.3.1-2.amzn2023.0.22"},"type":"exact-direct-match","found":{"vulnerabilityID":"ALAS2023-2026-3175","versionConstraint":"< 21.3.1-2.amzn2023.0.22 (rpm)"},"matcher":"rpm-matcher","searchedBy":{"distro":{"type":"amazonlinux","version":"2023"},"package":{"name":"python3-pip-wheel","version":"0:21.3.1-2.amzn2023.0.21"},"namespace":"amazon:distro:amazonlinux:2023"}},{"fix":{"suggestedVersion":"21.3.1-2.amzn2023.0.22"},"type":"exact-indirect-match","found":{"vulnerabilityID":"ALAS2023-2026-3175","versionConstraint":"< 21.3.1-2.amzn2023.0.22 (rpm)"},"matcher":"rpm-matcher","searchedBy":{"distro":{"type":"amazonlinux","version":"2023"},"package":{"name":"python-pip","version":"21.3.1-2.amzn2023.0.21"},"namespace":"amazon:distro:amazonlinux:2023"}}],"vulnerability":{"id":"ALAS2023-2026-3175","fix":{"state":"fixed","versions":["21.3.1-2.amzn2023.0.22"],"available":[{"date":"2026-10-12","kind":"advisory","version":"21.3.1-2.amzn2023.0.22"}]},"cvss":[],"cwes":[{"cve":"CVE-2026-97689","cwe":"CWE-770","type":"Secondary","source":"security-advisories@github.com"}],"epss":[{"cve":"CVE-2026-97689","date":"2026-10-19","epss":0.00335,"percentile":0.25374}],"risk":0.25125,"urls":[],"severity":"High","namespace":"amazon:distro:amazonlinux:2023","advisories":[],"dataSource":"https://alas.aws.amazon.com/AL2023/ALAS2023-2026-3175.html","description":"urllib3 is an HTTP client library for Python. From 1.10.3 until 2.8.0, the HTTPResponse.read_chunked and HTTPResponse.stream methods can allocate unbounded memory because the streaming chunk parser buffers the chunk-size field until newline or EOF without a length bound. The trigger is that a malicious server returns Transfer-Encoding: chunked followed by a very long run of bytes without a newline. The attack mechanism is that a malicious HTTP server sends a very long unterminated chunk-size line. The impact is that unbounded memory allocation can exhaust the client process. This issue is fixed in version 2.8.0. (CVE-2026-97689)"},"relatedVulnerabilities":[{"id":"CVE-2026-97689","cvss":[{"type":"Primary","source":"nvd@nist.gov","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","metrics":{"baseScore":7.5,"impactScore":3.6,"exploitabilityScore":3.9},"version":"3.1","vendorMetadata":{}},{"type":"Secondary","source":"security-advisories@github.com","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","metrics":{"baseScore":8.9},"version":"4.0","vendorMetadata":{}}],"cwes":[{"cve":"CVE-2026-97689","cwe":"CWE-770","type":"Secondary","source":"security-advisories@github.com"}],"epss":[{"cve":"CVE-2026-97689","date":"2026-10-19","epss":0.00335,"percentile":0.25374}],"urls":["https://github.com/urllib3/urllib3/commit/cd770b059b543be29298ea5c52afb0b1b090f5ed","https://github.com/urllib3/urllib3/releases/tag/2.8.0","https://github.com/urllib3/urllib3/security/advisories/GHSA-vxq7-64xx-v4gw"],"severity":"High","namespace":"nvd:cpe","dataSource":"https://nvd.nist.gov/vuln/detail/CVE-2026-97689","description":"urllib3 is an HTTP client library for Python. From 1.10.3 until 2.8.0, the HTTPResponse.read_chunked and HTTPResponse.stream methods can allocate unbounded memory because the streaming chunk parser buffers the chunk-size field until newline or EOF without a length bound. The trigger is that a malicious server returns Transfer-Encoding: chunked followed by a very long run of bytes without a newline. The attack mechanism is that a malicious HTTP server sends a very long unterminated chunk-size line. The impact is that unbounded memory allocation can exhaust the client process. This issue is fixed in version 2.8.0."}]},{"artifact":{"id":"eb34485cee60d766","cpes":["cpe:2.3:a:openssl-fips-provider-latest:openssl-fips-provider-latest:1\\:3.5.8-1.amzn2023.0.1:*:*:*:*:*:*:*","cpe:2.3:a:openssl-fips-provider-latest:openssl_fips_provider_latest:1\\:3.5.8-1.amzn2023.0.1:*:*:*:*:*:*:*","cpe:2.3:a:openssl_fips_provider_latest:openssl-fips-provider-latest:1\\:3.5.8-1.amzn2023.0.1:*:*:*:*:*:*:*","cpe:2.3:a:openssl_fips_provider_latest:openssl_fips_provider_latest:1\\:3.5.8-1.amzn2023.0.1:*:*:*:*:*:*:*","cpe:2.3:a:openssl-fips-provider:openssl-fips-provider-latest:1\\:3.5.8-1.amzn2023.0.1:*:*:*:*:*:*:*","cpe:2.3:a:openssl-fips-provider:openssl_fips_provider_latest:1\\:3.5.8-1.amzn2023.0.1:*:*:*:*:*:*:*","cpe:2.3:a:openssl_fips_provider:openssl-fips-provider-latest:1\\:3.5.8-1.amzn2023.0.1:*:*:*:*:*:*:*","cpe:2.3:a:openssl_fips_provider:openssl_fips_provider_latest:1\\:3.5.8-1.amzn2023.0.1:*:*:*:*:*:*:*","cpe:2.3:a:openssl-fips:openssl-fips-provider-latest:1\\:3.5.8-1.amzn2023.0.1:*:*:*:*:*:*:*","cpe:2.3:a:openssl-fips:openssl_fips_provider_latest:1\\:3.5.8-1.amzn2023.0.1:*:*:*:*:*:*:*","cpe:2.3:a:openssl_fips:openssl-fips-provider-latest:1\\:3.5.8-1.amzn2023.0.1:*:*:*:*:*:*:*","cpe:2.3:a:openssl_fips:openssl_fips_provider_latest:1\\:3.5.8-1.amzn2023.0.1:*:*:*:*:*:*:*","cpe:2.3:a:amazonlinux:openssl-fips-provider-latest:1\\:3.5.8-1.amzn2023.0.1:*:*:*:*:*:*:*","cpe:2.3:a:amazonlinux:openssl_fips_provider_latest:1\\:3.5.8-1.amzn2023.0.1:*:*:*:*:*:*:*","cpe:2.3:a:openssl:openssl-fips-provider-latest:1\\:3.5.8-1.amzn2023.0.1:*:*:*:*:*:*:*","cpe:2.3:a:openssl:openssl_fips_provider_latest:1\\:3.5.8-1.amzn2023.0.1:*:*:*:*:*:*:*"],"name":"openssl-fips-provider-latest","purl":"pkg:rpm/amzn/openssl-fips-provider-latest@3.5.8-1.amzn2023.0.1?arch=x86_64&distro=amzn-2023&epoch=1&upstream=openssl-3.5.8-1.amzn2023.0.1.src.rpm","type":"rpm","version":"1:3.5.8-1.amzn2023.0.1","language":"","licenses":["ASL 2.0"],"metadata":{"epoch":1,"architecture":"x86_64","modularityLabel":""},"locations":[{"path":"/var/lib/rpm/rpmdb.sqlite","layerID":"sha256:36ecccff5cdfa790aa570cb6cbe04b052333d62b672dac330d047934181da1ac","accessPath":"/var/lib/rpm/rpmdb.sqlite","annotations":{"evidence":"primary"}}],"upstreams":[{"name":"openssl","version":"3.5.8-1.amzn2023.0.1"}],"metadataType":"RpmMetadata"},"matchDetails":[{"fix":{"suggestedVersion":"3.5.8-1.amzn2023.0.3"},"type":"exact-direct-match","found":{"vulnerabilityID":"ALAS2023-2026-3204","versionConstraint":"< 3.5.8-1.amzn2023.0.3 (rpm)"},"matcher":"rpm-matcher","searchedBy":{"distro":{"type":"amazonlinux","version":"2023"},"package":{"name":"openssl-fips-provider-latest","version":"1:3.5.8-1.amzn2023.0.1"},"namespace":"amazon:distro:amazonlinux:2023"}},{"fix":{"suggestedVersion":"3.5.8-1.amzn2023.0.3"},"type":"exact-indirect-match","found":{"vulnerabilityID":"ALAS2023-2026-3204","versionConstraint":"< 3.5.8-1.amzn2023.0.3 (rpm)"},"matcher":"rpm-matcher","searchedBy":{"distro":{"type":"amazonlinux","version":"2023"},"package":{"name":"openssl","version":"3.5.8-1.amzn2023.0.1"},"namespace":"amazon:distro:amazonlinux:2023"}}],"vulnerability":{"id":"ALAS2023-2026-3204","fix":{"state":"fixed","versions":["3.5.8-1.amzn2023.0.3"],"available":[{"date":"2026-10-12","kind":"advisory","version":"3.5.8-1.amzn2023.0.3"}]},"cvss":[],"cwes":[{"cve":"CVE-2026-35189","cwe":"CWE-770","type":"Secondary","source":"openssl-security@openssl.org"},{"cve":"CVE-2026-35191","cwe":"CWE-440","type":"Secondary","source":"openssl-security@openssl.org"},{"cve":"CVE-2026-42772","cwe":"CWE-407","type":"Secondary","source":"openssl-security@openssl.org"},{"cve":"CVE-2026-54872","cwe":"CWE-208","type":"Secondary","source":"openssl-security@openssl.org"},{"cve":"CVE-2026-54873","cwe":"CWE-770","type":"Secondary","source":"openssl-security@openssl.org"},{"cve":"CVE-2026-72897","cwe":"CWE-787","type":"Secondary","source":"openssl-security@openssl.org"},{"cve":"CVE-2026-75804","cwe":"CWE-770","type":"Secondary","source":"openssl-security@openssl.org"},{"cve":"CVE-2026-75805","cwe":"CWE-476","type":"Secondary","source":"openssl-security@openssl.org"},{"cve":"CVE-2026-75806","cwe":"CWE-1284","type":"Secondary","source":"openssl-security@openssl.org"},{"cve":"CVE-2026-84782","cwe":"CWE-125","type":"Secondary","source":"openssl-security@openssl.org"},{"cve":"CVE-2026-84784","cwe":"CWE-770","type":"Secondary","source":"openssl-security@openssl.org"}],"epss":[{"cve":"CVE-2026-35189","date":"2026-10-19","epss":0.00267,"percentile":0.17666},{"cve":"CVE-2026-35191","date":"2026-10-19","epss":0.00357,"percentile":0.27986},{"cve":"CVE-2026-42772","date":"2026-10-19","epss":0.0033,"percentile":0.24601},{"cve":"CVE-2026-54872","date":"2026-10-19","epss":0.00263,"percentile":0.16964},{"cve":"CVE-2026-54873","date":"2026-10-19","epss":0.00462,"percentile":0.38743},{"cve":"CVE-2026-72897","date":"2026-10-19","epss":0.00266,"percentile":0.17333},{"cve":"CVE-2026-75804","date":"2026-10-19","epss":0.00352,"percentile":0.2736},{"cve":"CVE-2026-75805","date":"2026-10-19","epss":0.00222,"percentile":0.11962},{"cve":"CVE-2026-75806","date":"2026-10-19","epss":0.00387,"percentile":0.3128},{"cve":"CVE-2026-84782","date":"2026-10-19","epss":0.0039,"percentile":0.31687},{"cve":"CVE-2026-84784","date":"2026-10-19","epss":0.00403,"percentile":0.33142}],"risk":0.20024999999999998,"urls":[],"severity":"High","namespace":"amazon:distro:amazonlinux:2023","advisories":[],"dataSource":"https://alas.aws.amazon.com/AL2023/ALAS2023-2026-3204.html","description":"Issue summary: A certificate with many nameRelativeToCRLIssuer CRLdistribution points causes disproportionate heap growth when OpenSSL cachesX.509 extensions.Impact summary: Receiving a crafted certificate from a malicious peer can leadto significant memory pressure and possible Denial of Service in clients orin servers that solicit client certificates.CWE: CWE-770: Allocation of Resources Without Limits or ThrottlingDescription: A certificate or a set of certificates that fits under the limit forsize of certificates accepted from the peer (~100 KiB) can result in allocationof several hundred MiB of resident memory on the receiving sideduring a normal TLS handshake.  This may be enough to crash the client orserver, if multiple concurrent connections lead to similarly large memoryallocations.The fix postpones processing of the CRL distribution points extensions incertificates to the time when the processed value is required for CRL processing.This avoids keeping large memory allocations for a long time when suchcertificates are received.FIPS impact: noThe affected code is outside the FIPS module boundary. (CVE-2026-35189)Issue summary: The OpenSSL QUIC server, when configured to not preform addressvalidation, can be forced to count incoming packets multiple times in itsunvalidated credit computation, leading to a violation of the RFC 9000unvalidated connection amplification limit of 3 times the amount of datareceived.Impact summary: A remote attacker able to spoof packets to a server using theOpenSSL QUIC implementation might use the server for an amplification ofa DDoS attack.CWE: CWE-440: Expected Behavior ViolationDescription: OpenSSL's QUIC stack, when operating as a server, enforces clientaddress validation (RFC 9000, Section 8), to confirm the peer address is notused for a traffic amplification attack.  If this feature is disabled on theserver, the QUIC stack limits the amount of server data that can be sent to 3times the amount of data received from the peer address, until such time as theTLS handshake is completed.The OpenSSL QUIC server, when operating in non-validation mode, adds thelength of the whole datagram received to the unvalidated credit limit whenprocessing each QUIC packet in the datagram. A remote peer may,after establishing a connection with an initial client hello frame, send asubsequent datagram containing multiple QUIC packets, leading the server toaccount the entire datagram length for each packet in the datagram, resultingin the server believing that the peer has sent more data than it actually has,thereby violating the 3x amplification limit mandated by the RFC.FIPS impact: noAs the QUIC stack lives outside the FIPS module boundary, no FIPS modulesare affected by this CVE. (CVE-2026-35191)Issue summary: The QUIC stream reassembly algorithm performance deterioratesprogressively as packets are arriving out of order. The worst case hasa quadratic complexity proportional to the number of stream frames kept inthe buffer for the received stream data.Impact summary: A remote QUIC peer that completes the handshake can createa connection-scoped CPU pressure and potentially a Denial of Service usingcompliant STREAM frames inside the advertised receive window, with lowattacker bandwidth.CWE: CWE-407: Inefficient Algorithmic ComplexityDescription: OpenSSL manages received QUIC stream fragments using adoubly-linked list. While it optimizes for append operations (at the end ofthe list), it falls back to a head-to-tail linear search for any fragmentthat does not immediately follow the current `tail`.By manipulating the sequence of offsets, an attacker can force the serverto perform O(n^2) operations, consuming excessive CPU time for theQUIC process.FIPS impact: noThe FIPS module is not affected as the QUIC implementation is outside ofthe OpenSSL FIPS module boundary. (CVE-2026-42772)Issue summary: The generic elliptic-curve scalar multiplication used forECDSA and SM2 signature operations with curves that do not have a dedicatedimplementation leaks information about the secret nonce through timing.Impact summary: An attacker able to measure signing times may learninformation about the per-signature secret nonce, which over many signaturescan, via a lattice / Hidden Number Problem attack, lead to recovery of theprivate key.CWE: CWE-208: Observable Timing DiscrepancyDescription: The generic elliptic-curve scalar multiplication used forcurves that do not have a dedicated constant-time implementation pads thesecret scalar with non-constant-time BIGNUM operations, so the time takendepends on the value of the secret scalar derived from the ECDSA and SM2 nonce.The leak is very small; observing it requires a large number ofmeasurements. The effect is largest for curves whose group order lieson a machine-word boundary, such as brainpoolP384r1.Applications using ECDSA signing over the Brainpool and other generic primecurves, and SM2 signing on platforms that use the generic implementation,are vulnerable to this issue.The NIST curves P-256, P-384 and P-521 use dedicated constant-timeimplementations and are not affected.FIPS Impact: noThe FIPS modules are not affected: the approved NIST curves used in the FIPSprovider have dedicated constant-time implementations and do not use theaffected code path. (CVE-2026-54872)Issue summary: QUIC process may keep memory for QUIC packetbuffer for much longer period than necessary.Impact summary: Remote peer can exploit this vulnerabilityby sending maliciously crafted packets, making the localQUIC stack to keep the memory for packet buffers allocated.The time for which the memory remains allocated is entirelyunder the control of the potentially malicious remote peer.CWE: CWE-770: Allocation of Resources Without Limits or ThrottlingDescription: To save copy operation from the packet buffer to thestream reassemble buffer the QUIC stack leaves the stream dataon the packet buffer waiting to be copied to a buffer providedby the local receiving application. The QUIC stack releasesa reference to the packet buffer only after the data are copiedto the application buffer. This design is more efficient forlegitimate data transfers but enables an attacker to allocate a lotmore memory than actually required by the data kept in the receivingstream buffer.To mitigate the vulnerability, the QUIC stack now calculatesand monitors memory overhead for every stream. The memory overheadfor a single stream frame is calculated as a difference between thesize of the whole packet that carries the stream frame and the sizeof the stream frame itself. The memory overhead for a single streamframe is added to the total (cumulative) memory overhead QUIC stackkeeps for each stream. Once the cumulative memory overhead exceeds64kB, the QUIC stack moves the stream frame data from the packetbuffer to the stream buffer, starting with the next packet received.FIPS impact: noThe FIPS module is not affected as the QUIC implementation is outside ofthe OpenSSL FIPS module boundary. (CVE-2026-54873)Issue summary: A TLS server that calls SSL_set_SSL_CTX() to switch aconnection to a different SSL_CTX part way through a handshake may accessmemory beyond the end of an internal array if the replacement context knowsabout more provider signature algorithms than the context the connection wascreated from. Applications which never call SSL_set_SSL_CTX() are notaffected.Impact summary: A remote peer may be able to cause a small out-of-boundsread, and in some circumstances a fixed-value out-of-bounds write, on theserver heap. This may lead to a Denial of Service.CWE: CWE-787: Out-of-bounds WriteDescription: A TLS connection records how many certificate slots it haswhen it is created, taken from the SSL_CTX that created it: the built-incertificate types plus one slot for each provider TLS-SIGALG entry thatcontext was aware of. That count sizes an internal array of per-slotcertificate validity flags.An application may replace a connection's SSL_CTX part way through thehandshake by calling SSL_set_SSL_CTX(), most commonly from a servernamecallback in order to serve a different virtual host. Doing so did notrefresh the recorded count. A provider signature algorithm's slot index isits position in the list of whichever context resolves it, so if thereplacement context is aware of more of them than the original, analgorithm offered by the peer can resolve to an index beyond the end of thearray. Processing the peer's signature algorithms then reads one four byteword past the end for each such algorithm and, where the word read is zero,writes a fixed value over it. A peer offering many of them can corrupt heapmetadata and abort the process.Only provider signature algorithms which occupy one of the excess slots,and which the server also has configured, have this effect. Codepoints thereplacement context does not recognise are discarded without being resolvedto a slot, and provider signature algorithms are usable only from TLS 1.3.The two contexts must therefore be aware of different numbers of providersignature algorithms, which requires separate library contexts, a providerloaded between the two being created, or providers which differ in whatthey advertise - in 4.0, for example, the default provider advertises SM2where the FIPS provider does not. A deployment meeting the condition isalso unable to negotiate the affected algorithms with legitimate clients,since the same stale count hides the corresponding certificates, so themisconfiguration is likely to be noticed. For that reason, and because theconfiguration is not the default, this issue has been assessed as Lowseverity.FIPS impact: noNo FIPS modules are affected by this issue as the affected code is outsidethe OpenSSL FIPS module boundary. (CVE-2026-72897)Issue summary: OpenSSL QUIC stack does not enforce connectionlevel flow control for streams. Remote peers may send more bytesas long as they fit within the stream flow control limits.Impact summary: A malicious remote peer may exploit the lack of connectionflow control for streams to make the QUIC stack receive ~100MB of memoryinstead of 768 KiB (default flow control window size).CWE: CWE-770: Allocation of Resources Without Limits or ThrottlingDescription: The local QUIC stack advertises two flow control limitsto its remote peer: stream flow control limit and connection flowcontrol limit. The remote peer must follow both limits when transmittingstream data.Whenever the local QUIC stack receives a stream frame, it validatesthat the size of the received stream frame stays within flow control limits.If either limit is exceeded (stream level or connection level), thenthe QUIC stack must close the connection with a flow control error.The vulnerable OpenSSL QUIC stack enforces the stream-level but notthe connection-level limit. To exploit the issue, three conditions must be met:- the remote peer opens several streams- each stream must stay within the stream-level flow control limit- there must be no zero-offset byte sent on any of the streams(to prevent the vulnerable QUIC stack from consuming data).By meeting the conditions above, the remote peer may make the local stackallocate 2 x MAX_STREAMS x (stream flow control limit) bytesof memory. MAX_STREAMS defaults to 100, and the limit applies to bothbidirectional and unidirectional streams, making it 200 in total. The defaultflow control window for a stream is 512kB. The remote peer mayforce the vulnerable QUIC stack to allocate 100MB of heap per connection.FIPS impact: noThe FIPS module is not affected as the QUIC implementation is outside ofthe OpenSSL FIPS module boundary. (CVE-2026-75804)Issue summary: A CMP client that requests certificate revocation on the basisof a PKCS#10 CSR may dereference a NULL pointer and terminate abnormally whenprocessing a crafted revocation response.Impact summary: The NULL pointer dereference happens on a read whichleads to a crash and a Denial of Service for the affected client application.CWE: CWE-476: NULL-pointer dereferenceDescription: A CMP client revoking a certificate has to tell the server whichcertificate to revoke, and may do so by supplying a PKCS#10 CSR instead of thecertificate itself or its issuer name and serial number. This is'openssl cmp -cmd rr -csr <file>' on the command line, orOSSL_CMP_exec_RR_ses() with the certificate supplied viaOSSL_CMP_CTX_set1_p10CSR() through the API.A CSR does not contain the issuer name and serial number of the certificate,so the client does not send them. A server may optionally name thecertificate it revoked in its response, and the client then compares thatname against what it sent. Having sent neither an issuer name nor a serialnumber, it has nothing to compare against, and a server returning a speciallycrafted name causes the client to read from a NULL pointer and crash.The revocation response is checked for valid message protection beforethe affected code is reached, so an attacker must be a malicious orcompromised CMP server, or a man-in-the-middle in possession of thesecret used for message protection. Clients that identify the certificateto be revoked by a certificate or by issuer and serial number ratherthan by a PKCS#10 CSR are not affected.FIPS impact: noNo FIPS modules are affected by this issue, as the CMP protocolimplementation is outside the OpenSSL FIPS module boundary. (CVE-2026-75805)Issue summary: An established DTLS 1.2 association using an AEAD cipher suitecan be terminated by a single unauthenticated datagram whose encryptedfragment is shorter than the mandatory explicit IV and authentication tagoverhead.Impact summary: An attacker who can send a datagram that is routed to anexisting DTLS 1.2 association can tear that association down without knowingany key material. This is a Denial of Service limited to the targetedassociation. There is no memory safety or confidentiality impact.CWE: CWE-1284: Improper Validation of Specified Quantity in InputDescription: In TLS 1.2 and DTLS 1.2 every record protected by an AEAD ciphersuite carries an explicit IV followed by the ciphertext and an authenticationtag. When decrypting such a record the record layer passed the record length tothe cipher implementation before checking that the record was long enough tocontain the explicit IV and the tag. For a record shorter than that overhead thecipher implementation rejected the impossible length, and the record layertreated this as an internal failure and raised a fatal internal_error alertinstead of treating the record as one that failed authentication.In TLS 1.2 the same record causes a fatal internal_error alert instead of theexpected bad_record_mac alert. Since any undecryptable record alreadyterminates a TLS connection, this is a protocol conformance issue rather thana security issue in TLS.The fix validates the record length against the explicit IV and tag lengthbefore any AEAD processing, so that TLS reports bad_record_mac and DTLSsilently discards the record.FIPS impact: noThe affected code is outside the FIPS module boundary. (CVE-2026-75806)A flaw was found in OpenSSL. The Datagram Transport Layer Security (DTLS) retransmission mechanism fails to properly handle handshake message writes that are suspended before completion. A remote attacker could exploit this vulnerability during handshake message retransmission, causing OpenSSL to read past the message buffer or overwrite internal state required to resume writing. This issue can result in information disclosure through out-of-bounds memory reads or cause a Denial of Service (DoS) by crashing the process. (CVE-2026-84782)Issue summary: A malicious remote peer may flood the local QUICstack with NEW_CONNECTION_ID frames by avoiding a limit check onhow many connection IDs the remote QUIC stack can use.Impact summary: The local QUIC stack sends a RETIRE_CONN_ID framefor every NEW_CONNECTION_ID frame it receives. The RETIRE_CONN_IDframe is dispatched via the Control Frame Queue (CFQ). If the remotepeer also withholds ACKs, then it can force the local stackto allocate ~400MB (depending on ACK delay).CWE: CWE-770: Allocation of Resources Without Limits or ThrottlingDescription: RFC 9000 sections 5.1.1 and 5.1.2 [1] describe the mechanismby which a remote peer can notify the local QUIC stack to change thedestination connection ID (a.k.a. CID) the local stack uses toidentify the connection at the remote peer. Each CID is associatedwith a sequence number. The sequence number is transmittedin NEW_CONNECTION_ID and RETIRE_CONNECTION_ID frames to identify the CIDwhich is being either associated with a connection or retired.The remote peer sends a NEW_CONNECTION_ID frame to let the local stack knowa new CID is being associated with an existing connection. TheNEW_CONNECTION_ID frame carries the new CID, its sequence number, and theretire-prior-to number. The retire-prior-to identifies existingCIDs that are to be retired. The local QUIC stack must send aRETIRE_CONNECTION_ID for every destination CID whose sequence numberis less than retire-prior-to. The CID becomes retired after thelocal stack receives an ACK for its RETIRE_CONNECTION_ID frame.Although the OpenSSL QUIC stack supports at most one destination CIDfor every connection, it can be tricked into processing more thanone RETIRE_CONNECTION_ID frame per connection. The OpenSSL QUICstack currently retires the destination CID as soon as it receivesthe NEW_CONNECTION_ID, while in fact the destination CID mustbe retired after an ACK for the RETIRE_CONNECTION_ID frame is received.Correcting the flawed logic also fixes the backlog growth.[1] https://datatracker.ietf.org/doc/html/rfc9000#name-issuing-connection-idsFIPS impact: noThe FIPS module is not affected as the QUIC implementation is outside ofthe OpenSSL FIPS module boundary. (CVE-2026-84784)"},"relatedVulnerabilities":[{"id":"CVE-2026-35189","cvss":[{"type":"Secondary","source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","metrics":{"baseScore":5.3,"impactScore":1.5,"exploitabilityScore":3.9},"version":"3.1","vendorMetadata":{}}],"cwes":[{"cve":"CVE-2026-35189","cwe":"CWE-770","type":"Secondary","source":"openssl-security@openssl.org"}],"epss":[{"cve":"CVE-2026-35189","date":"2026-10-19","epss":0.00267,"percentile":0.17666}],"urls":["https://github.com/openssl/openssl/commit/2b93c73b2c70ddc4c61c5e4bfaaa6bd71379eb84","https://github.com/openssl/openssl/commit/3842516cc15e8b2cf55747011045e77547e71d89","https://github.com/openssl/openssl/commit/8e0efc7549b7ff8246d40e585e3fd604f728473f","https://github.com/openssl/openssl/commit/c72ae182cac17a82e4246c6ecd4e9c4ec3586ec9","https://openssl-library.org/news/secadv/20260929.txt"],"severity":"Medium","namespace":"nvd:cpe","dataSource":"https://nvd.nist.gov/vuln/detail/CVE-2026-35189","description":"Issue summary: A certificate with many nameRelativeToCRLIssuer CRL\ndistribution points causes disproportionate heap growth when OpenSSL caches\nX.509 extensions.\n\nImpact summary: Receiving a crafted certificate from a malicious peer can lead\nto significant memory pressure and possible Denial of Service in clients or\nin servers that solicit client certificates.\n\nCWE: CWE-770: Allocation of Resources Without Limits or Throttling\n\nDescription: A certificate or a set of certificates that fits under the limit for\nsize of certificates accepted from the peer (~100 KiB) can result in allocation\nof several hundred MiB of resident memory on the receiving side\nduring a normal TLS handshake.  This may be enough to crash the client or\nserver, if multiple concurrent connections lead to similarly large memory\nallocations.\n\nThe fix postpones processing of the CRL distribution points extensions in\ncertificates to the time when the processed value is required for CRL processing.\nThis avoids keeping large memory allocations for a long time when such\ncertificates are received.\n\nFIPS impact: no\nThe affected code is outside the FIPS module boundary."},{"id":"CVE-2026-35191","cvss":[{"type":"Secondary","source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L","metrics":{"baseScore":3.7,"impactScore":1.5,"exploitabilityScore":2.3},"version":"3.1","vendorMetadata":{}}],"cwes":[{"cve":"CVE-2026-35191","cwe":"CWE-440","type":"Secondary","source":"openssl-security@openssl.org"}],"epss":[{"cve":"CVE-2026-35191","date":"2026-10-19","epss":0.00357,"percentile":0.27986}],"urls":["https://github.com/openssl/openssl/commit/0fe4442d4f8ea3af8a174046dae176e0d4717239","https://github.com/openssl/openssl/commit/2de4c35fb13fc58f43fd8dc1d261700472ce72e5","https://github.com/openssl/openssl/commit/e44292e58b090014232ef75bd400393851b24d1a","https://openssl-library.org/news/secadv/20260929.txt"],"severity":"Low","namespace":"nvd:cpe","dataSource":"https://nvd.nist.gov/vuln/detail/CVE-2026-35191","description":"Issue summary: The OpenSSL QUIC server, when configured to not preform address\nvalidation, can be forced to count incoming packets multiple times in its\nunvalidated credit computation, leading to a violation of the RFC 9000\nunvalidated connection amplification limit of 3 times the amount of data\nreceived.\n\nImpact summary: A remote attacker able to spoof packets to a server using the\nOpenSSL QUIC implementation might use the server for an amplification of\na DDoS attack.\n\nCWE: CWE-440: Expected Behavior Violation \n\nDescription: OpenSSL's QUIC stack, when operating as a server, enforces client\naddress validation (RFC 9000, Section 8), to confirm the peer address is not\nused for a traffic amplification attack.  If this feature is disabled on the\nserver, the QUIC stack limits the amount of server data that can be sent to 3\ntimes the amount of data received from the peer address, until such time as the\nTLS handshake is completed.\n\nThe OpenSSL QUIC server, when operating in non-validation mode, adds the\nlength of the whole datagram received to the unvalidated credit limit when\nprocessing each QUIC packet in the datagram. A remote peer may,\nafter establishing a connection with an initial client hello frame, send a\nsubsequent datagram containing multiple QUIC packets, leading the server to\naccount the entire datagram length for each packet in the datagram, resulting\nin the server believing that the peer has sent more data than it actually has,\nthereby violating the 3x amplification limit mandated by the RFC.\n\nFIPS impact: no\nAs the QUIC stack lives outside the FIPS module boundary, no FIPS modules\nare affected by this CVE."},{"id":"CVE-2026-42772","cvss":[{"type":"Secondary","source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","metrics":{"baseScore":5.3,"impactScore":1.5,"exploitabilityScore":3.9},"version":"3.1","vendorMetadata":{}}],"cwes":[{"cve":"CVE-2026-42772","cwe":"CWE-407","type":"Secondary","source":"openssl-security@openssl.org"}],"epss":[{"cve":"CVE-2026-42772","date":"2026-10-19","epss":0.0033,"percentile":0.24601}],"urls":["https://github.com/openssl/openssl/commit/32d0ed8afe1b8c3e7ece725b44663da3d7087a09","https://github.com/openssl/openssl/commit/ca8402e273af4de5b3f04fa61a0f0c02ce3ae20e","https://github.com/openssl/openssl/commit/eb2becc0a4baea7f3050a247834d0e5c2ebe1773","https://github.com/openssl/openssl/commit/f42ae513bbda513b3c121d54834040ee4a0eae1a","https://openssl-library.org/news/secadv/20260929.txt"],"severity":"Medium","namespace":"nvd:cpe","dataSource":"https://nvd.nist.gov/vuln/detail/CVE-2026-42772","description":"Issue summary: The QUIC stream reassembly algorithm performance deteriorates\nprogressively as packets are arriving out of order. The worst case has\na quadratic complexity proportional to the number of stream frames kept in\nthe buffer for the received stream data.\n\nImpact summary: A remote QUIC peer that completes the handshake can create\na connection-scoped CPU pressure and potentially a Denial of Service using\ncompliant STREAM frames inside the advertised receive window, with low\nattacker bandwidth.\n\nCWE: CWE-407: Inefficient Algorithmic Complexity\n\nDescription: OpenSSL manages received QUIC stream fragments using a\ndoubly-linked list. While it optimizes for append operations (at the end of\nthe list), it falls back to a head-to-tail linear search for any fragment\nthat does not immediately follow the current `tail`.\n\nBy manipulating the sequence of offsets, an attacker can force the server\nto perform O(n^2) operations, consuming excessive CPU time for the\nQUIC process.\n\nFIPS impact: no\nThe FIPS module is not affected as the QUIC implementation is outside of\nthe OpenSSL FIPS module boundary."},{"id":"CVE-2026-54872","cvss":[{"type":"Secondary","source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N","metrics":{"baseScore":3.7,"impactScore":1.5,"exploitabilityScore":2.3},"version":"3.1","vendorMetadata":{}}],"cwes":[{"cve":"CVE-2026-54872","cwe":"CWE-208","type":"Secondary","source":"openssl-security@openssl.org"}],"epss":[{"cve":"CVE-2026-54872","date":"2026-10-19","epss":0.00263,"percentile":0.16964}],"urls":["https://github.com/openssl/openssl/commit/1a5bee8dc57430a2be69cd1ffe7fec6a62f4f179","https://github.com/openssl/openssl/commit/3f7e1363dccec6f7732bb9e9fa471bb6e4aa68cb","https://github.com/openssl/openssl/commit/7d83bc7764999dfd91b83b4f0815b45390422afd","https://github.com/openssl/openssl/commit/8166827a78aad164a07aa86dea2b425403ced471","https://openssl-library.org/news/secadv/20260929.txt"],"severity":"Low","namespace":"nvd:cpe","dataSource":"https://nvd.nist.gov/vuln/detail/CVE-2026-54872","description":"Issue summary: The generic elliptic-curve scalar multiplication used for\nECDSA and SM2 signature operations with curves that do not have a dedicated\nimplementation leaks information about the secret nonce through timing.\n\nImpact summary: An attacker able to measure signing times may learn\ninformation about the per-signature secret nonce, which over many signatures\ncan, via a lattice / Hidden Number Problem attack, lead to recovery of the\nprivate key.\n\nCWE: CWE-208: Observable Timing Discrepancy\n\nDescription: The generic elliptic-curve scalar multiplication used for\ncurves that do not have a dedicated constant-time implementation pads the\nsecret scalar with non-constant-time BIGNUM operations, so the time taken\ndepends on the value of the secret scalar derived from the ECDSA and SM2 nonce.\n\nThe leak is very small; observing it requires a large number of\nmeasurements. The effect is largest for curves whose group order lies\non a machine-word boundary, such as brainpoolP384r1.\n\nApplications using ECDSA signing over the Brainpool and other generic prime\ncurves, and SM2 signing on platforms that use the generic implementation,\nare vulnerable to this issue.\n\nThe NIST curves P-256, P-384 and P-521 use dedicated constant-time\nimplementations and are not affected.\n\nFIPS Impact: no\nThe FIPS modules are not affected: the approved NIST curves used in the FIPS\nprovider have dedicated constant-time implementations and do not use the\naffected code path."},{"id":"CVE-2026-54873","cvss":[{"type":"Secondary","source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","metrics":{"baseScore":7.5,"impactScore":3.6,"exploitabilityScore":3.9},"version":"3.1","vendorMetadata":{}}],"cwes":[{"cve":"CVE-2026-54873","cwe":"CWE-770","type":"Secondary","source":"openssl-security@openssl.org"}],"epss":[{"cve":"CVE-2026-54873","date":"2026-10-19","epss":0.00462,"percentile":0.38743}],"urls":["https://github.com/openssl/openssl/commit/1f643b8bc735487b500a1f68a7fb3a22d5e38e23","https://github.com/openssl/openssl/commit/279e7ee1392af98785746788168749491c74bd53","https://github.com/openssl/openssl/commit/3ea6213e050e938ecbbf8c4eff32bec2736780eb","https://github.com/openssl/openssl/commit/7127fb10888b49711c63128a09e524c0d2d5d0b2","https://openssl-library.org/news/secadv/20260929.txt"],"severity":"High","namespace":"nvd:cpe","dataSource":"https://nvd.nist.gov/vuln/detail/CVE-2026-54873","description":"Issue summary: QUIC process may keep memory for QUIC packet\nbuffer for much longer period than necessary.\n\nImpact summary: Remote peer can exploit this vulnerability\nby sending maliciously crafted packets, making the local\nQUIC stack to keep the memory for packet buffers allocated.\nThe time for which the memory remains allocated is entirely\nunder the control of the potentially malicious remote peer.\n\nCWE: CWE-770: Allocation of Resources Without Limits or Throttling\n\nDescription: To save copy operation from the packet buffer to the\nstream reassemble buffer the QUIC stack leaves the stream data\non the packet buffer waiting to be copied to a buffer provided\nby the local receiving application. The QUIC stack releases\na reference to the packet buffer only after the data are copied\nto the application buffer. This design is more efficient for\nlegitimate data transfers but enables an attacker to allocate a lot\nmore memory than actually required by the data kept in the receiving\nstream buffer.\n\nTo mitigate the vulnerability, the QUIC stack now calculates\nand monitors memory overhead for every stream. The memory overhead\nfor a single stream frame is calculated as a difference between the\nsize of the whole packet that carries the stream frame and the size\nof the stream frame itself. The memory overhead for a single stream\nframe is added to the total (cumulative) memory overhead QUIC stack\nkeeps for each stream. Once the cumulative memory overhead exceeds\n64kB, the QUIC stack moves the stream frame data from the packet\nbuffer to the stream buffer, starting with the next packet received.\n\nFIPS impact: no\nThe FIPS module is not affected as the QUIC implementation is outside of\nthe OpenSSL FIPS module boundary."},{"id":"CVE-2026-72897","cvss":[{"type":"Secondary","source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","metrics":{"baseScore":7.5,"impactScore":3.6,"exploitabilityScore":3.9},"version":"3.1","vendorMetadata":{}}],"cwes":[{"cve":"CVE-2026-72897","cwe":"CWE-787","type":"Secondary","source":"openssl-security@openssl.org"}],"epss":[{"cve":"CVE-2026-72897","date":"2026-10-19","epss":0.00266,"percentile":0.17333}],"urls":["https://github.com/openssl/openssl/commit/00646e5085a0d12d29e0d2f9b9bc5f7111a50922","https://github.com/openssl/openssl/commit/4135f553c9d3ba4a09fe752f5d30af2a6a092b2e","https://github.com/openssl/openssl/commit/9c54d209486f6b1ad79fe2179c40f13200fa4f61","https://github.com/openssl/openssl/commit/e87ed26b298a74d8ba61a53e9c7bcd1acac6b814","https://openssl-library.org/news/secadv/20260929.txt"],"severity":"High","namespace":"nvd:cpe","dataSource":"https://nvd.nist.gov/vuln/detail/CVE-2026-72897","description":"Issue summary: A TLS server that calls SSL_set_SSL_CTX() to switch a\nconnection to a different SSL_CTX part way through a handshake may access\nmemory beyond the end of an internal array if the replacement context knows\nabout more provider signature algorithms than the context the connection was\ncreated from. Applications which never call SSL_set_SSL_CTX() are not\naffected.\n\nImpact summary: A remote peer may be able to cause a small out-of-bounds\nread, and in some circumstances a fixed-value out-of-bounds write, on the\nserver heap. This may lead to a Denial of Service.\n\nCWE: CWE-787: Out-of-bounds Write\n\nDescription: A TLS connection records how many certificate slots it has\nwhen it is created, taken from the SSL_CTX that created it: the built-in\ncertificate types plus one slot for each provider TLS-SIGALG entry that\ncontext was aware of. That count sizes an internal array of per-slot\ncertificate validity flags.\n\nAn application may replace a connection's SSL_CTX part way through the\nhandshake by calling SSL_set_SSL_CTX(), most commonly from a servername\ncallback in order to serve a different virtual host. Doing so did not\nrefresh the recorded count. A provider signature algorithm's slot index is\nits position in the list of whichever context resolves it, so if the\nreplacement context is aware of more of them than the original, an\nalgorithm offered by the peer can resolve to an index beyond the end of the\narray. Processing the peer's signature algorithms then reads one four byte\nword past the end for each such algorithm and, where the word read is zero,\nwrites a fixed value over it. A peer offering many of them can corrupt heap\nmetadata and abort the process.\n\nOnly provider signature algorithms which occupy one of the excess slots,\nand which the server also has configured, have this effect. Codepoints the\nreplacement context does not recognise are discarded without being resolved\nto a slot, and provider signature algorithms are usable only from TLS 1.3.\n\nThe two contexts must therefore be aware of different numbers of provider\nsignature algorithms, which requires separate library contexts, a provider\nloaded between the two being created, or providers which differ in what\nthey advertise - in 4.0, for example, the default provider advertises SM2\nwhere the FIPS provider does not. A deployment meeting the condition is\nalso unable to negotiate the affected algorithms with legitimate clients,\nsince the same stale count hides the corresponding certificates, so the\nmisconfiguration is likely to be noticed. For that reason, and because the\nconfiguration is not the default, this issue has been assessed as Low\nseverity.\n\nFIPS impact: no\nNo FIPS modules are affected by this issue as the affected code is outside\nthe OpenSSL FIPS module boundary."},{"id":"CVE-2026-75804","cvss":[{"type":"Secondary","source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","metrics":{"baseScore":5.3,"impactScore":1.5,"exploitabilityScore":3.9},"version":"3.1","vendorMetadata":{}}],"cwes":[{"cve":"CVE-2026-75804","cwe":"CWE-770","type":"Secondary","source":"openssl-security@openssl.org"}],"epss":[{"cve":"CVE-2026-75804","date":"2026-10-19","epss":0.00352,"percentile":0.2736}],"urls":["https://github.com/openssl/openssl/commit/2e8f54666b3fb7b05ff5f58aa6cac9285163654e","https://github.com/openssl/openssl/commit/4533ee8a5686c953ed3b644738ac4bdf20806538","https://github.com/openssl/openssl/commit/64d3102fb5b54311e92517f26ba00169d719e74a","https://github.com/openssl/openssl/commit/f9eaecf5bdd6692da052bc65b0332af2a938ac03","https://openssl-library.org/news/secadv/20260929.txt"],"severity":"Medium","namespace":"nvd:cpe","dataSource":"https://nvd.nist.gov/vuln/detail/CVE-2026-75804","description":"Issue summary: OpenSSL QUIC stack does not enforce connection\nlevel flow control for streams. Remote peers may send more bytes\nas long as they fit within the stream flow control limits.\n\nImpact summary: A malicious remote peer may exploit the lack of connection\nflow control for streams to make the QUIC stack receive ~100MB of memory\ninstead of 768 KiB (default flow control window size).\n\nCWE: CWE-770: Allocation of Resources Without Limits or Throttling\n\nDescription: The local QUIC stack advertises two flow control limits\nto its remote peer: stream flow control limit and connection flow\ncontrol limit. The remote peer must follow both limits when transmitting\nstream data.\n\nWhenever the local QUIC stack receives a stream frame, it validates\nthat the size of the received stream frame stays within flow control limits.\nIf either limit is exceeded (stream level or connection level), then\nthe QUIC stack must close the connection with a flow control error.\n\nThe vulnerable OpenSSL QUIC stack enforces the stream-level but not\nthe connection-level limit. To exploit the issue, three conditions must be met:\n  - the remote peer opens several streams\n  - each stream must stay within the stream-level flow control limit\n  - there must be no zero-offset byte sent on any of the streams\n    (to prevent the vulnerable QUIC stack from consuming data).\nBy meeting the conditions above, the remote peer may make the local stack\nallocate 2 x MAX_STREAMS x (stream flow control limit) bytes\nof memory. MAX_STREAMS defaults to 100, and the limit applies to both\nbidirectional and unidirectional streams, making it 200 in total. The default\nflow control window for a stream is 512kB. The remote peer may\nforce the vulnerable QUIC stack to allocate 100MB of heap per connection.\n\nFIPS impact: no\nThe FIPS module is not affected as the QUIC implementation is outside of\nthe OpenSSL FIPS module boundary."},{"id":"CVE-2026-75805","cvss":[{"type":"Secondary","source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","metrics":{"baseScore":5.3,"impactScore":1.5,"exploitabilityScore":3.9},"version":"3.1","vendorMetadata":{}}],"cwes":[{"cve":"CVE-2026-75805","cwe":"CWE-476","type":"Secondary","source":"openssl-security@openssl.org"}],"epss":[{"cve":"CVE-2026-75805","date":"2026-10-19","epss":0.00222,"percentile":0.11962}],"urls":["https://github.com/openssl/openssl/commit/7588db7fef14209c3caa3a101d11a02006b19166","https://github.com/openssl/openssl/commit/7ca0ccb5172a577e9b87267d77bfe21e5481a5e7","https://github.com/openssl/openssl/commit/9eb2a8a9b86136cdb39d6d7d50644dd66941cdc3","https://github.com/openssl/openssl/commit/abf02872a4b71767ecc72293424420f5b009190f","https://openssl-library.org/news/secadv/20260929.txt"],"severity":"Medium","namespace":"nvd:cpe","dataSource":"https://nvd.nist.gov/vuln/detail/CVE-2026-75805","description":"Issue summary: A CMP client that requests certificate revocation on the basis\nof a PKCS#10 CSR may dereference a NULL pointer and terminate abnormally when\nprocessing a crafted revocation response. \n\nImpact summary: The NULL pointer dereference happens on a read which \nleads to a crash and a Denial of Service for the affected client application.\n\nCWE: CWE-476: NULL-pointer dereference\n\nDescription: A CMP client revoking a certificate has to tell the server which\ncertificate to revoke, and may do so by supplying a PKCS#10 CSR instead of the\ncertificate itself or its issuer name and serial number. This is\n'openssl cmp -cmd rr -csr <file>' on the command line, or\nOSSL_CMP_exec_RR_ses() with the certificate supplied via\nOSSL_CMP_CTX_set1_p10CSR() through the API.\n\nA CSR does not contain the issuer name and serial number of the certificate,\nso the client does not send them. A server may optionally name the\ncertificate it revoked in its response, and the client then compares that\nname against what it sent. Having sent neither an issuer name nor a serial\nnumber, it has nothing to compare against, and a server returning a specially\ncrafted name causes the client to read from a NULL pointer and crash.\n\nThe revocation response is checked for valid message protection before\nthe affected code is reached, so an attacker must be a malicious or\ncompromised CMP server, or a man-in-the-middle in possession of the\nsecret used for message protection. Clients that identify the certificate\nto be revoked by a certificate or by issuer and serial number rather\nthan by a PKCS#10 CSR are not affected.\n\nFIPS impact: no\nNo FIPS modules are affected by this issue, as the CMP protocol\nimplementation is outside the OpenSSL FIPS module boundary."},{"id":"CVE-2026-75806","cvss":[{"type":"Secondary","source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","metrics":{"baseScore":5.3,"impactScore":1.5,"exploitabilityScore":3.9},"version":"3.1","vendorMetadata":{}}],"cwes":[{"cve":"CVE-2026-75806","cwe":"CWE-1284","type":"Secondary","source":"openssl-security@openssl.org"}],"epss":[{"cve":"CVE-2026-75806","date":"2026-10-19","epss":0.00387,"percentile":0.3128}],"urls":["https://github.com/openssl/openssl/commit/04728a289a823e68137f88da016cb9ede307217d","https://github.com/openssl/openssl/commit/050b275cd671a6eed1d6457642d41a5a77aab972","https://github.com/openssl/openssl/commit/3a4589d015a9049d47b66f186cf50a8711343a1d","https://github.com/openssl/openssl/commit/5af82fefbaf2b5fec2fc0e1d87f112844902f01d","https://openssl-library.org/news/secadv/20260929.txt"],"severity":"Medium","namespace":"nvd:cpe","dataSource":"https://nvd.nist.gov/vuln/detail/CVE-2026-75806","description":"Issue summary: An established DTLS 1.2 association using an AEAD cipher suite\ncan be terminated by a single unauthenticated datagram whose encrypted\nfragment is shorter than the mandatory explicit IV and authentication tag\noverhead.\n\nImpact summary: An attacker who can send a datagram that is routed to an\nexisting DTLS 1.2 association can tear that association down without knowing\nany key material. This is a Denial of Service limited to the targeted\nassociation. There is no memory safety or confidentiality impact.\n\nCWE: CWE-1284: Improper Validation of Specified Quantity in Input\n\nDescription: In TLS 1.2 and DTLS 1.2 every record protected by an AEAD cipher\nsuite carries an explicit IV followed by the ciphertext and an authentication\ntag. When decrypting such a record the record layer passed the record length to\nthe cipher implementation before checking that the record was long enough to\ncontain the explicit IV and the tag. For a record shorter than that overhead the\ncipher implementation rejected the impossible length, and the record layer\ntreated this as an internal failure and raised a fatal internal_error alert\ninstead of treating the record as one that failed authentication.\n\nIn TLS 1.2 the same record causes a fatal internal_error alert instead of the\nexpected bad_record_mac alert. Since any undecryptable record already\nterminates a TLS connection, this is a protocol conformance issue rather than\na security issue in TLS.\n\nThe fix validates the record length against the explicit IV and tag length\nbefore any AEAD processing, so that TLS reports bad_record_mac and DTLS\nsilently discards the record.\n\nFIPS impact: no\nThe affected code is outside the FIPS module boundary."},{"id":"CVE-2026-84782","cvss":[{"type":"Secondary","source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H","metrics":{"baseScore":8.2,"impactScore":4.3,"exploitabilityScore":3.9},"version":"3.1","vendorMetadata":{}}],"cwes":[{"cve":"CVE-2026-84782","cwe":"CWE-125","type":"Secondary","source":"openssl-security@openssl.org"}],"epss":[{"cve":"CVE-2026-84782","date":"2026-10-19","epss":0.0039,"percentile":0.31687}],"urls":["https://github.com/openssl/openssl/commit/906cf0ef1c85ca40ce69163e9086d6d3fe292943","https://github.com/openssl/openssl/commit/9f6b34422af7eb5dac61322e33dac1ae989fa628","https://github.com/openssl/openssl/commit/a383dafdd754eb5b22bf45e37e1bff9d07277a58","https://github.com/openssl/openssl/commit/d951e02ede8f6a6ff8150546db44b34f0518192c","https://openssl-library.org/news/secadv/20260929.txt"],"severity":"High","namespace":"nvd:cpe","dataSource":"https://nvd.nist.gov/vuln/detail/CVE-2026-84782","description":"Issue summary: The DTLS retransmission logic does not correctly handle\na handshake message write that is suspended part-way through.\nThe retransmitted message can be read past the message buffer and\nthe retransmission overwrites the internal state the suspended write\nneeds to resume correctly.\n\nImpact summary: The retransmitted message can disclose a heap memory\nto the peer as plaintext handshake data or cause a crash and a Denial\nof Service when the read reaches an unmapped memory region.\n\nCWE: CWE-125: Out-of-bounds Read\n\nDescription: DTLS handshake messages can be written out in multiple\nfragments, and a write can suspend mid-message (returning WANT_WRITE)\nif the underlying transport temporarily cannot accept more data. While\nsuch a write is suspended, the DTLS retransmission timer may\nindependently fire and ask the retransmission logic to resend an\nearlier, already-acknowledged-as-sent message from its retransmit\nqueue.\n\nThe retransmission logic reused the same internal buffer and position\ntracking as the message that was still being written, without\nresetting the position back to the start of the message being\nretransmitted. As a result the retransmission was read starting from\nwherever the suspended write had left off, producing a mislabelled\nmessage whose body was leftover bytes from the other, larger message\nstill in flight - content that was never meant to be sent at that\npoint, and which could run past the end of the allocated buffer.\n\nSeparately, even when the retransmission is positioned correctly,\nallowing it to run to completion while another write is suspended\noverwrites the same shared bookkeeping that the suspended write\ndepends on to resume. When the application later resumes the\nsuspended write (via a subsequent SSL_read(), SSL_write(),\nSSL_accept(), or SSL_connect() call), it finds that bookkeeping in a\nstate inconsistent with the message and aborts the process in\na debugging build.\n\nThe fix resets the retransmission's read position to the start of the\nmessage before resending, and skips retransmission entirely whenever a\nhandshake write is still suspended, deferring to the next call that\nresumes it instead.\n\nFIPS impact: no\nThe affected code is outside the FIPS module boundary."},{"id":"CVE-2026-84784","cvss":[{"type":"Secondary","source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","metrics":{"baseScore":7.5,"impactScore":3.6,"exploitabilityScore":3.9},"version":"3.1","vendorMetadata":{}}],"cwes":[{"cve":"CVE-2026-84784","cwe":"CWE-770","type":"Secondary","source":"openssl-security@openssl.org"}],"epss":[{"cve":"CVE-2026-84784","date":"2026-10-19","epss":0.00403,"percentile":0.33142}],"urls":["https://github.com/openssl/openssl/commit/4685c914b0d410b1034f40b547c95bc95e7a380a","https://github.com/openssl/openssl/commit/9a30fe0fba195c14e5b87bf93c0d0fdb70373806","https://github.com/openssl/openssl/commit/dba3c48d653c64fcbc9070a17a0ee2b3e2f3af1f","https://github.com/openssl/openssl/commit/e9e5155833fa968bee50024bf9ca3a185ab599fe","https://openssl-library.org/news/secadv/20260929.txt"],"severity":"High","namespace":"nvd:cpe","dataSource":"https://nvd.nist.gov/vuln/detail/CVE-2026-84784","description":"Issue summary: A malicious remote peer may flood the local QUIC\nstack with NEW_CONNECTION_ID frames by avoiding a limit check on\nhow many connection IDs the remote QUIC stack can use.\n\nImpact summary: The local QUIC stack sends a RETIRE_CONN_ID frame\nfor every NEW_CONNECTION_ID frame it receives. The RETIRE_CONN_ID\nframe is dispatched via the Control Frame Queue (CFQ). If the remote\npeer also withholds ACKs, then it can force the local stack\nto allocate ~400MB (depending on ACK delay).\n\nCWE: CWE-770: Allocation of Resources Without Limits or Throttling\n\nDescription: RFC 9000 sections 5.1.1 and 5.1.2 [1] describe the mechanism\nby which a remote peer can notify the local QUIC stack to change the\ndestination connection ID (a.k.a. CID) the local stack uses to\nidentify the connection at the remote peer. Each CID is associated\nwith a sequence number. The sequence number is transmitted\nin NEW_CONNECTION_ID and RETIRE_CONNECTION_ID frames to identify the CID\nwhich is being either associated with a connection or retired.\n\nThe remote peer sends a NEW_CONNECTION_ID frame to let the local stack know\na new CID is being associated with an existing connection. The\nNEW_CONNECTION_ID frame carries the new CID, its sequence number, and the\nretire-prior-to number. The retire-prior-to identifies existing\nCIDs that are to be retired. The local QUIC stack must send a\nRETIRE_CONNECTION_ID for every destination CID whose sequence number\nis less than retire-prior-to. The CID becomes retired after the\nlocal stack receives an ACK for its RETIRE_CONNECTION_ID frame.\n\nAlthough the OpenSSL QUIC stack supports at most one destination CID\nfor every connection, it can be tricked into processing more than\none RETIRE_CONNECTION_ID frame per connection. The OpenSSL QUIC\nstack currently retires the destination CID as soon as it receives\nthe NEW_CONNECTION_ID, while in fact the destination CID must\nbe retired after an ACK for the RETIRE_CONNECTION_ID frame is received.\nCorrecting the flawed logic also fixes the backlog growth.\n\n[1] https://datatracker.ietf.org/doc/html/rfc9000#name-issuing-connection-ids\n\nFIPS impact: no\nThe FIPS module is not affected as the QUIC implementation is outside of\nthe OpenSSL FIPS module boundary."}]},{"artifact":{"id":"f20fb8ae84b31212","cpes":["cpe:2.3:a:openssl-libs:openssl-libs:1\\:3.5.8-1.amzn2023.0.1:*:*:*:*:*:*:*","cpe:2.3:a:openssl-libs:openssl_libs:1\\:3.5.8-1.amzn2023.0.1:*:*:*:*:*:*:*","cpe:2.3:a:openssl_libs:openssl-libs:1\\:3.5.8-1.amzn2023.0.1:*:*:*:*:*:*:*","cpe:2.3:a:openssl_libs:openssl_libs:1\\:3.5.8-1.amzn2023.0.1:*:*:*:*:*:*:*","cpe:2.3:a:amazonlinux:openssl-libs:1\\:3.5.8-1.amzn2023.0.1:*:*:*:*:*:*:*","cpe:2.3:a:amazonlinux:openssl_libs:1\\:3.5.8-1.amzn2023.0.1:*:*:*:*:*:*:*","cpe:2.3:a:openssl:openssl-libs:1\\:3.5.8-1.amzn2023.0.1:*:*:*:*:*:*:*","cpe:2.3:a:openssl:openssl_libs:1\\:3.5.8-1.amzn2023.0.1:*:*:*:*:*:*:*"],"name":"openssl-libs","purl":"pkg:rpm/amzn/openssl-libs@3.5.8-1.amzn2023.0.1?arch=x86_64&distro=amzn-2023&epoch=1&upstream=openssl-3.5.8-1.amzn2023.0.1.src.rpm","type":"rpm","version":"1:3.5.8-1.amzn2023.0.1","language":"","licenses":["ASL 2.0"],"metadata":{"epoch":1,"architecture":"x86_64","modularityLabel":""},"locations":[{"path":"/var/lib/rpm/rpmdb.sqlite","layerID":"sha256:36ecccff5cdfa790aa570cb6cbe04b052333d62b672dac330d047934181da1ac","accessPath":"/var/lib/rpm/rpmdb.sqlite","annotations":{"evidence":"primary"}}],"upstreams":[{"name":"openssl","version":"3.5.8-1.amzn2023.0.1"}],"metadataType":"RpmMetadata"},"matchDetails":[{"fix":{"suggestedVersion":"3.5.8-1.amzn2023.0.3"},"type":"exact-direct-match","found":{"vulnerabilityID":"ALAS2023-2026-3204","versionConstraint":"< 3.5.8-1.amzn2023.0.3 (rpm)"},"matcher":"rpm-matcher","searchedBy":{"distro":{"type":"amazonlinux","version":"2023"},"package":{"name":"openssl-libs","version":"1:3.5.8-1.amzn2023.0.1"},"namespace":"amazon:distro:amazonlinux:2023"}},{"fix":{"suggestedVersion":"3.5.8-1.amzn2023.0.3"},"type":"exact-indirect-match","found":{"vulnerabilityID":"ALAS2023-2026-3204","versionConstraint":"< 3.5.8-1.amzn2023.0.3 (rpm)"},"matcher":"rpm-matcher","searchedBy":{"distro":{"type":"amazonlinux","version":"2023"},"package":{"name":"openssl","version":"3.5.8-1.amzn2023.0.1"},"namespace":"amazon:distro:amazonlinux:2023"}}],"vulnerability":{"id":"ALAS2023-2026-3204","fix":{"state":"fixed","versions":["3.5.8-1.amzn2023.0.3"],"available":[{"date":"2026-10-12","kind":"advisory","version":"3.5.8-1.amzn2023.0.3"}]},"cvss":[],"cwes":[{"cve":"CVE-2026-35189","cwe":"CWE-770","type":"Secondary","source":"openssl-security@openssl.org"},{"cve":"CVE-2026-35191","cwe":"CWE-440","type":"Secondary","source":"openssl-security@openssl.org"},{"cve":"CVE-2026-42772","cwe":"CWE-407","type":"Secondary","source":"openssl-security@openssl.org"},{"cve":"CVE-2026-54872","cwe":"CWE-208","type":"Secondary","source":"openssl-security@openssl.org"},{"cve":"CVE-2026-54873","cwe":"CWE-770","type":"Secondary","source":"openssl-security@openssl.org"},{"cve":"CVE-2026-72897","cwe":"CWE-787","type":"Secondary","source":"openssl-security@openssl.org"},{"cve":"CVE-2026-75804","cwe":"CWE-770","type":"Secondary","source":"openssl-security@openssl.org"},{"cve":"CVE-2026-75805","cwe":"CWE-476","type":"Secondary","source":"openssl-security@openssl.org"},{"cve":"CVE-2026-75806","cwe":"CWE-1284","type":"Secondary","source":"openssl-security@openssl.org"},{"cve":"CVE-2026-84782","cwe":"CWE-125","type":"Secondary","source":"openssl-security@openssl.org"},{"cve":"CVE-2026-84784","cwe":"CWE-770","type":"Secondary","source":"openssl-security@openssl.org"}],"epss":[{"cve":"CVE-2026-35189","date":"2026-10-19","epss":0.00267,"percentile":0.17666},{"cve":"CVE-2026-35191","date":"2026-10-19","epss":0.00357,"percentile":0.27986},{"cve":"CVE-2026-42772","date":"2026-10-19","epss":0.0033,"percentile":0.24601},{"cve":"CVE-2026-54872","date":"2026-10-19","epss":0.00263,"percentile":0.16964},{"cve":"CVE-2026-54873","date":"2026-10-19","epss":0.00462,"percentile":0.38743},{"cve":"CVE-2026-72897","date":"2026-10-19","epss":0.00266,"percentile":0.17333},{"cve":"CVE-2026-75804","date":"2026-10-19","epss":0.00352,"percentile":0.2736},{"cve":"CVE-2026-75805","date":"2026-10-19","epss":0.00222,"percentile":0.11962},{"cve":"CVE-2026-75806","date":"2026-10-19","epss":0.00387,"percentile":0.3128},{"cve":"CVE-2026-84782","date":"2026-10-19","epss":0.0039,"percentile":0.31687},{"cve":"CVE-2026-84784","date":"2026-10-19","epss":0.00403,"percentile":0.33142}],"risk":0.20024999999999998,"urls":[],"severity":"High","namespace":"amazon:distro:amazonlinux:2023","advisories":[],"dataSource":"https://alas.aws.amazon.com/AL2023/ALAS2023-2026-3204.html","description":"Issue summary: A certificate with many nameRelativeToCRLIssuer CRLdistribution points causes disproportionate heap growth when OpenSSL cachesX.509 extensions.Impact summary: Receiving a crafted certificate from a malicious peer can leadto significant memory pressure and possible Denial of Service in clients orin servers that solicit client certificates.CWE: CWE-770: Allocation of Resources Without Limits or ThrottlingDescription: A certificate or a set of certificates that fits under the limit forsize of certificates accepted from the peer (~100 KiB) can result in allocationof several hundred MiB of resident memory on the receiving sideduring a normal TLS handshake.  This may be enough to crash the client orserver, if multiple concurrent connections lead to similarly large memoryallocations.The fix postpones processing of the CRL distribution points extensions incertificates to the time when the processed value is required for CRL processing.This avoids keeping large memory allocations for a long time when suchcertificates are received.FIPS impact: noThe affected code is outside the FIPS module boundary. (CVE-2026-35189)Issue summary: The OpenSSL QUIC server, when configured to not preform addressvalidation, can be forced to count incoming packets multiple times in itsunvalidated credit computation, leading to a violation of the RFC 9000unvalidated connection amplification limit of 3 times the amount of datareceived.Impact summary: A remote attacker able to spoof packets to a server using theOpenSSL QUIC implementation might use the server for an amplification ofa DDoS attack.CWE: CWE-440: Expected Behavior ViolationDescription: OpenSSL's QUIC stack, when operating as a server, enforces clientaddress validation (RFC 9000, Section 8), to confirm the peer address is notused for a traffic amplification attack.  If this feature is disabled on theserver, the QUIC stack limits the amount of server data that can be sent to 3times the amount of data received from the peer address, until such time as theTLS handshake is completed.The OpenSSL QUIC server, when operating in non-validation mode, adds thelength of the whole datagram received to the unvalidated credit limit whenprocessing each QUIC packet in the datagram. A remote peer may,after establishing a connection with an initial client hello frame, send asubsequent datagram containing multiple QUIC packets, leading the server toaccount the entire datagram length for each packet in the datagram, resultingin the server believing that the peer has sent more data than it actually has,thereby violating the 3x amplification limit mandated by the RFC.FIPS impact: noAs the QUIC stack lives outside the FIPS module boundary, no FIPS modulesare affected by this CVE. (CVE-2026-35191)Issue summary: The QUIC stream reassembly algorithm performance deterioratesprogressively as packets are arriving out of order. The worst case hasa quadratic complexity proportional to the number of stream frames kept inthe buffer for the received stream data.Impact summary: A remote QUIC peer that completes the handshake can createa connection-scoped CPU pressure and potentially a Denial of Service usingcompliant STREAM frames inside the advertised receive window, with lowattacker bandwidth.CWE: CWE-407: Inefficient Algorithmic ComplexityDescription: OpenSSL manages received QUIC stream fragments using adoubly-linked list. While it optimizes for append operations (at the end ofthe list), it falls back to a head-to-tail linear search for any fragmentthat does not immediately follow the current `tail`.By manipulating the sequence of offsets, an attacker can force the serverto perform O(n^2) operations, consuming excessive CPU time for theQUIC process.FIPS impact: noThe FIPS module is not affected as the QUIC implementation is outside ofthe OpenSSL FIPS module boundary. (CVE-2026-42772)Issue summary: The generic elliptic-curve scalar multiplication used forECDSA and SM2 signature operations with curves that do not have a dedicatedimplementation leaks information about the secret nonce through timing.Impact summary: An attacker able to measure signing times may learninformation about the per-signature secret nonce, which over many signaturescan, via a lattice / Hidden Number Problem attack, lead to recovery of theprivate key.CWE: CWE-208: Observable Timing DiscrepancyDescription: The generic elliptic-curve scalar multiplication used forcurves that do not have a dedicated constant-time implementation pads thesecret scalar with non-constant-time BIGNUM operations, so the time takendepends on the value of the secret scalar derived from the ECDSA and SM2 nonce.The leak is very small; observing it requires a large number ofmeasurements. The effect is largest for curves whose group order lieson a machine-word boundary, such as brainpoolP384r1.Applications using ECDSA signing over the Brainpool and other generic primecurves, and SM2 signing on platforms that use the generic implementation,are vulnerable to this issue.The NIST curves P-256, P-384 and P-521 use dedicated constant-timeimplementations and are not affected.FIPS Impact: noThe FIPS modules are not affected: the approved NIST curves used in the FIPSprovider have dedicated constant-time implementations and do not use theaffected code path. (CVE-2026-54872)Issue summary: QUIC process may keep memory for QUIC packetbuffer for much longer period than necessary.Impact summary: Remote peer can exploit this vulnerabilityby sending maliciously crafted packets, making the localQUIC stack to keep the memory for packet buffers allocated.The time for which the memory remains allocated is entirelyunder the control of the potentially malicious remote peer.CWE: CWE-770: Allocation of Resources Without Limits or ThrottlingDescription: To save copy operation from the packet buffer to thestream reassemble buffer the QUIC stack leaves the stream dataon the packet buffer waiting to be copied to a buffer providedby the local receiving application. The QUIC stack releasesa reference to the packet buffer only after the data are copiedto the application buffer. This design is more efficient forlegitimate data transfers but enables an attacker to allocate a lotmore memory than actually required by the data kept in the receivingstream buffer.To mitigate the vulnerability, the QUIC stack now calculatesand monitors memory overhead for every stream. The memory overheadfor a single stream frame is calculated as a difference between thesize of the whole packet that carries the stream frame and the sizeof the stream frame itself. The memory overhead for a single streamframe is added to the total (cumulative) memory overhead QUIC stackkeeps for each stream. Once the cumulative memory overhead exceeds64kB, the QUIC stack moves the stream frame data from the packetbuffer to the stream buffer, starting with the next packet received.FIPS impact: noThe FIPS module is not affected as the QUIC implementation is outside ofthe OpenSSL FIPS module boundary. (CVE-2026-54873)Issue summary: A TLS server that calls SSL_set_SSL_CTX() to switch aconnection to a different SSL_CTX part way through a handshake may accessmemory beyond the end of an internal array if the replacement context knowsabout more provider signature algorithms than the context the connection wascreated from. Applications which never call SSL_set_SSL_CTX() are notaffected.Impact summary: A remote peer may be able to cause a small out-of-boundsread, and in some circumstances a fixed-value out-of-bounds write, on theserver heap. This may lead to a Denial of Service.CWE: CWE-787: Out-of-bounds WriteDescription: A TLS connection records how many certificate slots it haswhen it is created, taken from the SSL_CTX that created it: the built-incertificate types plus one slot for each provider TLS-SIGALG entry thatcontext was aware of. That count sizes an internal array of per-slotcertificate validity flags.An application may replace a connection's SSL_CTX part way through thehandshake by calling SSL_set_SSL_CTX(), most commonly from a servernamecallback in order to serve a different virtual host. Doing so did notrefresh the recorded count. A provider signature algorithm's slot index isits position in the list of whichever context resolves it, so if thereplacement context is aware of more of them than the original, analgorithm offered by the peer can resolve to an index beyond the end of thearray. Processing the peer's signature algorithms then reads one four byteword past the end for each such algorithm and, where the word read is zero,writes a fixed value over it. A peer offering many of them can corrupt heapmetadata and abort the process.Only provider signature algorithms which occupy one of the excess slots,and which the server also has configured, have this effect. Codepoints thereplacement context does not recognise are discarded without being resolvedto a slot, and provider signature algorithms are usable only from TLS 1.3.The two contexts must therefore be aware of different numbers of providersignature algorithms, which requires separate library contexts, a providerloaded between the two being created, or providers which differ in whatthey advertise - in 4.0, for example, the default provider advertises SM2where the FIPS provider does not. A deployment meeting the condition isalso unable to negotiate the affected algorithms with legitimate clients,since the same stale count hides the corresponding certificates, so themisconfiguration is likely to be noticed. For that reason, and because theconfiguration is not the default, this issue has been assessed as Lowseverity.FIPS impact: noNo FIPS modules are affected by this issue as the affected code is outsidethe OpenSSL FIPS module boundary. (CVE-2026-72897)Issue summary: OpenSSL QUIC stack does not enforce connectionlevel flow control for streams. Remote peers may send more bytesas long as they fit within the stream flow control limits.Impact summary: A malicious remote peer may exploit the lack of connectionflow control for streams to make the QUIC stack receive ~100MB of memoryinstead of 768 KiB (default flow control window size).CWE: CWE-770: Allocation of Resources Without Limits or ThrottlingDescription: The local QUIC stack advertises two flow control limitsto its remote peer: stream flow control limit and connection flowcontrol limit. The remote peer must follow both limits when transmittingstream data.Whenever the local QUIC stack receives a stream frame, it validatesthat the size of the received stream frame stays within flow control limits.If either limit is exceeded (stream level or connection level), thenthe QUIC stack must close the connection with a flow control error.The vulnerable OpenSSL QUIC stack enforces the stream-level but notthe connection-level limit. To exploit the issue, three conditions must be met:- the remote peer opens several streams- each stream must stay within the stream-level flow control limit- there must be no zero-offset byte sent on any of the streams(to prevent the vulnerable QUIC stack from consuming data).By meeting the conditions above, the remote peer may make the local stackallocate 2 x MAX_STREAMS x (stream flow control limit) bytesof memory. MAX_STREAMS defaults to 100, and the limit applies to bothbidirectional and unidirectional streams, making it 200 in total. The defaultflow control window for a stream is 512kB. The remote peer mayforce the vulnerable QUIC stack to allocate 100MB of heap per connection.FIPS impact: noThe FIPS module is not affected as the QUIC implementation is outside ofthe OpenSSL FIPS module boundary. (CVE-2026-75804)Issue summary: A CMP client that requests certificate revocation on the basisof a PKCS#10 CSR may dereference a NULL pointer and terminate abnormally whenprocessing a crafted revocation response.Impact summary: The NULL pointer dereference happens on a read whichleads to a crash and a Denial of Service for the affected client application.CWE: CWE-476: NULL-pointer dereferenceDescription: A CMP client revoking a certificate has to tell the server whichcertificate to revoke, and may do so by supplying a PKCS#10 CSR instead of thecertificate itself or its issuer name and serial number. This is'openssl cmp -cmd rr -csr <file>' on the command line, orOSSL_CMP_exec_RR_ses() with the certificate supplied viaOSSL_CMP_CTX_set1_p10CSR() through the API.A CSR does not contain the issuer name and serial number of the certificate,so the client does not send them. A server may optionally name thecertificate it revoked in its response, and the client then compares thatname against what it sent. Having sent neither an issuer name nor a serialnumber, it has nothing to compare against, and a server returning a speciallycrafted name causes the client to read from a NULL pointer and crash.The revocation response is checked for valid message protection beforethe affected code is reached, so an attacker must be a malicious orcompromised CMP server, or a man-in-the-middle in possession of thesecret used for message protection. Clients that identify the certificateto be revoked by a certificate or by issuer and serial number ratherthan by a PKCS#10 CSR are not affected.FIPS impact: noNo FIPS modules are affected by this issue, as the CMP protocolimplementation is outside the OpenSSL FIPS module boundary. (CVE-2026-75805)Issue summary: An established DTLS 1.2 association using an AEAD cipher suitecan be terminated by a single unauthenticated datagram whose encryptedfragment is shorter than the mandatory explicit IV and authentication tagoverhead.Impact summary: An attacker who can send a datagram that is routed to anexisting DTLS 1.2 association can tear that association down without knowingany key material. This is a Denial of Service limited to the targetedassociation. There is no memory safety or confidentiality impact.CWE: CWE-1284: Improper Validation of Specified Quantity in InputDescription: In TLS 1.2 and DTLS 1.2 every record protected by an AEAD ciphersuite carries an explicit IV followed by the ciphertext and an authenticationtag. When decrypting such a record the record layer passed the record length tothe cipher implementation before checking that the record was long enough tocontain the explicit IV and the tag. For a record shorter than that overhead thecipher implementation rejected the impossible length, and the record layertreated this as an internal failure and raised a fatal internal_error alertinstead of treating the record as one that failed authentication.In TLS 1.2 the same record causes a fatal internal_error alert instead of theexpected bad_record_mac alert. Since any undecryptable record alreadyterminates a TLS connection, this is a protocol conformance issue rather thana security issue in TLS.The fix validates the record length against the explicit IV and tag lengthbefore any AEAD processing, so that TLS reports bad_record_mac and DTLSsilently discards the record.FIPS impact: noThe affected code is outside the FIPS module boundary. (CVE-2026-75806)A flaw was found in OpenSSL. The Datagram Transport Layer Security (DTLS) retransmission mechanism fails to properly handle handshake message writes that are suspended before completion. A remote attacker could exploit this vulnerability during handshake message retransmission, causing OpenSSL to read past the message buffer or overwrite internal state required to resume writing. This issue can result in information disclosure through out-of-bounds memory reads or cause a Denial of Service (DoS) by crashing the process. (CVE-2026-84782)Issue summary: A malicious remote peer may flood the local QUICstack with NEW_CONNECTION_ID frames by avoiding a limit check onhow many connection IDs the remote QUIC stack can use.Impact summary: The local QUIC stack sends a RETIRE_CONN_ID framefor every NEW_CONNECTION_ID frame it receives. The RETIRE_CONN_IDframe is dispatched via the Control Frame Queue (CFQ). If the remotepeer also withholds ACKs, then it can force the local stackto allocate ~400MB (depending on ACK delay).CWE: CWE-770: Allocation of Resources Without Limits or ThrottlingDescription: RFC 9000 sections 5.1.1 and 5.1.2 [1] describe the mechanismby which a remote peer can notify the local QUIC stack to change thedestination connection ID (a.k.a. CID) the local stack uses toidentify the connection at the remote peer. Each CID is associatedwith a sequence number. The sequence number is transmittedin NEW_CONNECTION_ID and RETIRE_CONNECTION_ID frames to identify the CIDwhich is being either associated with a connection or retired.The remote peer sends a NEW_CONNECTION_ID frame to let the local stack knowa new CID is being associated with an existing connection. TheNEW_CONNECTION_ID frame carries the new CID, its sequence number, and theretire-prior-to number. The retire-prior-to identifies existingCIDs that are to be retired. The local QUIC stack must send aRETIRE_CONNECTION_ID for every destination CID whose sequence numberis less than retire-prior-to. The CID becomes retired after thelocal stack receives an ACK for its RETIRE_CONNECTION_ID frame.Although the OpenSSL QUIC stack supports at most one destination CIDfor every connection, it can be tricked into processing more thanone RETIRE_CONNECTION_ID frame per connection. The OpenSSL QUICstack currently retires the destination CID as soon as it receivesthe NEW_CONNECTION_ID, while in fact the destination CID mustbe retired after an ACK for the RETIRE_CONNECTION_ID frame is received.Correcting the flawed logic also fixes the backlog growth.[1] https://datatracker.ietf.org/doc/html/rfc9000#name-issuing-connection-idsFIPS impact: noThe FIPS module is not affected as the QUIC implementation is outside ofthe OpenSSL FIPS module boundary. (CVE-2026-84784)"},"relatedVulnerabilities":[{"id":"CVE-2026-35189","cvss":[{"type":"Secondary","source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","metrics":{"baseScore":5.3,"impactScore":1.5,"exploitabilityScore":3.9},"version":"3.1","vendorMetadata":{}}],"cwes":[{"cve":"CVE-2026-35189","cwe":"CWE-770","type":"Secondary","source":"openssl-security@openssl.org"}],"epss":[{"cve":"CVE-2026-35189","date":"2026-10-19","epss":0.00267,"percentile":0.17666}],"urls":["https://github.com/openssl/openssl/commit/2b93c73b2c70ddc4c61c5e4bfaaa6bd71379eb84","https://github.com/openssl/openssl/commit/3842516cc15e8b2cf55747011045e77547e71d89","https://github.com/openssl/openssl/commit/8e0efc7549b7ff8246d40e585e3fd604f728473f","https://github.com/openssl/openssl/commit/c72ae182cac17a82e4246c6ecd4e9c4ec3586ec9","https://openssl-library.org/news/secadv/20260929.txt"],"severity":"Medium","namespace":"nvd:cpe","dataSource":"https://nvd.nist.gov/vuln/detail/CVE-2026-35189","description":"Issue summary: A certificate with many nameRelativeToCRLIssuer CRL\ndistribution points causes disproportionate heap growth when OpenSSL caches\nX.509 extensions.\n\nImpact summary: Receiving a crafted certificate from a malicious peer can lead\nto significant memory pressure and possible Denial of Service in clients or\nin servers that solicit client certificates.\n\nCWE: CWE-770: Allocation of Resources Without Limits or Throttling\n\nDescription: A certificate or a set of certificates that fits under the limit for\nsize of certificates accepted from the peer (~100 KiB) can result in allocation\nof several hundred MiB of resident memory on the receiving side\nduring a normal TLS handshake.  This may be enough to crash the client or\nserver, if multiple concurrent connections lead to similarly large memory\nallocations.\n\nThe fix postpones processing of the CRL distribution points extensions in\ncertificates to the time when the processed value is required for CRL processing.\nThis avoids keeping large memory allocations for a long time when such\ncertificates are received.\n\nFIPS impact: no\nThe affected code is outside the FIPS module boundary."},{"id":"CVE-2026-35191","cvss":[{"type":"Secondary","source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L","metrics":{"baseScore":3.7,"impactScore":1.5,"exploitabilityScore":2.3},"version":"3.1","vendorMetadata":{}}],"cwes":[{"cve":"CVE-2026-35191","cwe":"CWE-440","type":"Secondary","source":"openssl-security@openssl.org"}],"epss":[{"cve":"CVE-2026-35191","date":"2026-10-19","epss":0.00357,"percentile":0.27986}],"urls":["https://github.com/openssl/openssl/commit/0fe4442d4f8ea3af8a174046dae176e0d4717239","https://github.com/openssl/openssl/commit/2de4c35fb13fc58f43fd8dc1d261700472ce72e5","https://github.com/openssl/openssl/commit/e44292e58b090014232ef75bd400393851b24d1a","https://openssl-library.org/news/secadv/20260929.txt"],"severity":"Low","namespace":"nvd:cpe","dataSource":"https://nvd.nist.gov/vuln/detail/CVE-2026-35191","description":"Issue summary: The OpenSSL QUIC server, when configured to not preform address\nvalidation, can be forced to count incoming packets multiple times in its\nunvalidated credit computation, leading to a violation of the RFC 9000\nunvalidated connection amplification limit of 3 times the amount of data\nreceived.\n\nImpact summary: A remote attacker able to spoof packets to a server using the\nOpenSSL QUIC implementation might use the server for an amplification of\na DDoS attack.\n\nCWE: CWE-440: Expected Behavior Violation \n\nDescription: OpenSSL's QUIC stack, when operating as a server, enforces client\naddress validation (RFC 9000, Section 8), to confirm the peer address is not\nused for a traffic amplification attack.  If this feature is disabled on the\nserver, the QUIC stack limits the amount of server data that can be sent to 3\ntimes the amount of data received from the peer address, until such time as the\nTLS handshake is completed.\n\nThe OpenSSL QUIC server, when operating in non-validation mode, adds the\nlength of the whole datagram received to the unvalidated credit limit when\nprocessing each QUIC packet in the datagram. A remote peer may,\nafter establishing a connection with an initial client hello frame, send a\nsubsequent datagram containing multiple QUIC packets, leading the server to\naccount the entire datagram length for each packet in the datagram, resulting\nin the server believing that the peer has sent more data than it actually has,\nthereby violating the 3x amplification limit mandated by the RFC.\n\nFIPS impact: no\nAs the QUIC stack lives outside the FIPS module boundary, no FIPS modules\nare affected by this CVE."},{"id":"CVE-2026-42772","cvss":[{"type":"Secondary","source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","metrics":{"baseScore":5.3,"impactScore":1.5,"exploitabilityScore":3.9},"version":"3.1","vendorMetadata":{}}],"cwes":[{"cve":"CVE-2026-42772","cwe":"CWE-407","type":"Secondary","source":"openssl-security@openssl.org"}],"epss":[{"cve":"CVE-2026-42772","date":"2026-10-19","epss":0.0033,"percentile":0.24601}],"urls":["https://github.com/openssl/openssl/commit/32d0ed8afe1b8c3e7ece725b44663da3d7087a09","https://github.com/openssl/openssl/commit/ca8402e273af4de5b3f04fa61a0f0c02ce3ae20e","https://github.com/openssl/openssl/commit/eb2becc0a4baea7f3050a247834d0e5c2ebe1773","https://github.com/openssl/openssl/commit/f42ae513bbda513b3c121d54834040ee4a0eae1a","https://openssl-library.org/news/secadv/20260929.txt"],"severity":"Medium","namespace":"nvd:cpe","dataSource":"https://nvd.nist.gov/vuln/detail/CVE-2026-42772","description":"Issue summary: The QUIC stream reassembly algorithm performance deteriorates\nprogressively as packets are arriving out of order. The worst case has\na quadratic complexity proportional to the number of stream frames kept in\nthe buffer for the received stream data.\n\nImpact summary: A remote QUIC peer that completes the handshake can create\na connection-scoped CPU pressure and potentially a Denial of Service using\ncompliant STREAM frames inside the advertised receive window, with low\nattacker bandwidth.\n\nCWE: CWE-407: Inefficient Algorithmic Complexity\n\nDescription: OpenSSL manages received QUIC stream fragments using a\ndoubly-linked list. While it optimizes for append operations (at the end of\nthe list), it falls back to a head-to-tail linear search for any fragment\nthat does not immediately follow the current `tail`.\n\nBy manipulating the sequence of offsets, an attacker can force the server\nto perform O(n^2) operations, consuming excessive CPU time for the\nQUIC process.\n\nFIPS impact: no\nThe FIPS module is not affected as the QUIC implementation is outside of\nthe OpenSSL FIPS module boundary."},{"id":"CVE-2026-54872","cvss":[{"type":"Secondary","source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N","metrics":{"baseScore":3.7,"impactScore":1.5,"exploitabilityScore":2.3},"version":"3.1","vendorMetadata":{}}],"cwes":[{"cve":"CVE-2026-54872","cwe":"CWE-208","type":"Secondary","source":"openssl-security@openssl.org"}],"epss":[{"cve":"CVE-2026-54872","date":"2026-10-19","epss":0.00263,"percentile":0.16964}],"urls":["https://github.com/openssl/openssl/commit/1a5bee8dc57430a2be69cd1ffe7fec6a62f4f179","https://github.com/openssl/openssl/commit/3f7e1363dccec6f7732bb9e9fa471bb6e4aa68cb","https://github.com/openssl/openssl/commit/7d83bc7764999dfd91b83b4f0815b45390422afd","https://github.com/openssl/openssl/commit/8166827a78aad164a07aa86dea2b425403ced471","https://openssl-library.org/news/secadv/20260929.txt"],"severity":"Low","namespace":"nvd:cpe","dataSource":"https://nvd.nist.gov/vuln/detail/CVE-2026-54872","description":"Issue summary: The generic elliptic-curve scalar multiplication used for\nECDSA and SM2 signature operations with curves that do not have a dedicated\nimplementation leaks information about the secret nonce through timing.\n\nImpact summary: An attacker able to measure signing times may learn\ninformation about the per-signature secret nonce, which over many signatures\ncan, via a lattice / Hidden Number Problem attack, lead to recovery of the\nprivate key.\n\nCWE: CWE-208: Observable Timing Discrepancy\n\nDescription: The generic elliptic-curve scalar multiplication used for\ncurves that do not have a dedicated constant-time implementation pads the\nsecret scalar with non-constant-time BIGNUM operations, so the time taken\ndepends on the value of the secret scalar derived from the ECDSA and SM2 nonce.\n\nThe leak is very small; observing it requires a large number of\nmeasurements. The effect is largest for curves whose group order lies\non a machine-word boundary, such as brainpoolP384r1.\n\nApplications using ECDSA signing over the Brainpool and other generic prime\ncurves, and SM2 signing on platforms that use the generic implementation,\nare vulnerable to this issue.\n\nThe NIST curves P-256, P-384 and P-521 use dedicated constant-time\nimplementations and are not affected.\n\nFIPS Impact: no\nThe FIPS modules are not affected: the approved NIST curves used in the FIPS\nprovider have dedicated constant-time implementations and do not use the\naffected code path."},{"id":"CVE-2026-54873","cvss":[{"type":"Secondary","source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","metrics":{"baseScore":7.5,"impactScore":3.6,"exploitabilityScore":3.9},"version":"3.1","vendorMetadata":{}}],"cwes":[{"cve":"CVE-2026-54873","cwe":"CWE-770","type":"Secondary","source":"openssl-security@openssl.org"}],"epss":[{"cve":"CVE-2026-54873","date":"2026-10-19","epss":0.00462,"percentile":0.38743}],"urls":["https://github.com/openssl/openssl/commit/1f643b8bc735487b500a1f68a7fb3a22d5e38e23","https://github.com/openssl/openssl/commit/279e7ee1392af98785746788168749491c74bd53","https://github.com/openssl/openssl/commit/3ea6213e050e938ecbbf8c4eff32bec2736780eb","https://github.com/openssl/openssl/commit/7127fb10888b49711c63128a09e524c0d2d5d0b2","https://openssl-library.org/news/secadv/20260929.txt"],"severity":"High","namespace":"nvd:cpe","dataSource":"https://nvd.nist.gov/vuln/detail/CVE-2026-54873","description":"Issue summary: QUIC process may keep memory for QUIC packet\nbuffer for much longer period than necessary.\n\nImpact summary: Remote peer can exploit this vulnerability\nby sending maliciously crafted packets, making the local\nQUIC stack to keep the memory for packet buffers allocated.\nThe time for which the memory remains allocated is entirely\nunder the control of the potentially malicious remote peer.\n\nCWE: CWE-770: Allocation of Resources Without Limits or Throttling\n\nDescription: To save copy operation from the packet buffer to the\nstream reassemble buffer the QUIC stack leaves the stream data\non the packet buffer waiting to be copied to a buffer provided\nby the local receiving application. The QUIC stack releases\na reference to the packet buffer only after the data are copied\nto the application buffer. This design is more efficient for\nlegitimate data transfers but enables an attacker to allocate a lot\nmore memory than actually required by the data kept in the receiving\nstream buffer.\n\nTo mitigate the vulnerability, the QUIC stack now calculates\nand monitors memory overhead for every stream. The memory overhead\nfor a single stream frame is calculated as a difference between the\nsize of the whole packet that carries the stream frame and the size\nof the stream frame itself. The memory overhead for a single stream\nframe is added to the total (cumulative) memory overhead QUIC stack\nkeeps for each stream. Once the cumulative memory overhead exceeds\n64kB, the QUIC stack moves the stream frame data from the packet\nbuffer to the stream buffer, starting with the next packet received.\n\nFIPS impact: no\nThe FIPS module is not affected as the QUIC implementation is outside of\nthe OpenSSL FIPS module boundary."},{"id":"CVE-2026-72897","cvss":[{"type":"Secondary","source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","metrics":{"baseScore":7.5,"impactScore":3.6,"exploitabilityScore":3.9},"version":"3.1","vendorMetadata":{}}],"cwes":[{"cve":"CVE-2026-72897","cwe":"CWE-787","type":"Secondary","source":"openssl-security@openssl.org"}],"epss":[{"cve":"CVE-2026-72897","date":"2026-10-19","epss":0.00266,"percentile":0.17333}],"urls":["https://github.com/openssl/openssl/commit/00646e5085a0d12d29e0d2f9b9bc5f7111a50922","https://github.com/openssl/openssl/commit/4135f553c9d3ba4a09fe752f5d30af2a6a092b2e","https://github.com/openssl/openssl/commit/9c54d209486f6b1ad79fe2179c40f13200fa4f61","https://github.com/openssl/openssl/commit/e87ed26b298a74d8ba61a53e9c7bcd1acac6b814","https://openssl-library.org/news/secadv/20260929.txt"],"severity":"High","namespace":"nvd:cpe","dataSource":"https://nvd.nist.gov/vuln/detail/CVE-2026-72897","description":"Issue summary: A TLS server that calls SSL_set_SSL_CTX() to switch a\nconnection to a different SSL_CTX part way through a handshake may access\nmemory beyond the end of an internal array if the replacement context knows\nabout more provider signature algorithms than the context the connection was\ncreated from. Applications which never call SSL_set_SSL_CTX() are not\naffected.\n\nImpact summary: A remote peer may be able to cause a small out-of-bounds\nread, and in some circumstances a fixed-value out-of-bounds write, on the\nserver heap. This may lead to a Denial of Service.\n\nCWE: CWE-787: Out-of-bounds Write\n\nDescription: A TLS connection records how many certificate slots it has\nwhen it is created, taken from the SSL_CTX that created it: the built-in\ncertificate types plus one slot for each provider TLS-SIGALG entry that\ncontext was aware of. That count sizes an internal array of per-slot\ncertificate validity flags.\n\nAn application may replace a connection's SSL_CTX part way through the\nhandshake by calling SSL_set_SSL_CTX(), most commonly from a servername\ncallback in order to serve a different virtual host. Doing so did not\nrefresh the recorded count. A provider signature algorithm's slot index is\nits position in the list of whichever context resolves it, so if the\nreplacement context is aware of more of them than the original, an\nalgorithm offered by the peer can resolve to an index beyond the end of the\narray. Processing the peer's signature algorithms then reads one four byte\nword past the end for each such algorithm and, where the word read is zero,\nwrites a fixed value over it. A peer offering many of them can corrupt heap\nmetadata and abort the process.\n\nOnly provider signature algorithms which occupy one of the excess slots,\nand which the server also has configured, have this effect. Codepoints the\nreplacement context does not recognise are discarded without being resolved\nto a slot, and provider signature algorithms are usable only from TLS 1.3.\n\nThe two contexts must therefore be aware of different numbers of provider\nsignature algorithms, which requires separate library contexts, a provider\nloaded between the two being created, or providers which differ in what\nthey advertise - in 4.0, for example, the default provider advertises SM2\nwhere the FIPS provider does not. A deployment meeting the condition is\nalso unable to negotiate the affected algorithms with legitimate clients,\nsince the same stale count hides the corresponding certificates, so the\nmisconfiguration is likely to be noticed. For that reason, and because the\nconfiguration is not the default, this issue has been assessed as Low\nseverity.\n\nFIPS impact: no\nNo FIPS modules are affected by this issue as the affected code is outside\nthe OpenSSL FIPS module boundary."},{"id":"CVE-2026-75804","cvss":[{"type":"Secondary","source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","metrics":{"baseScore":5.3,"impactScore":1.5,"exploitabilityScore":3.9},"version":"3.1","vendorMetadata":{}}],"cwes":[{"cve":"CVE-2026-75804","cwe":"CWE-770","type":"Secondary","source":"openssl-security@openssl.org"}],"epss":[{"cve":"CVE-2026-75804","date":"2026-10-19","epss":0.00352,"percentile":0.2736}],"urls":["https://github.com/openssl/openssl/commit/2e8f54666b3fb7b05ff5f58aa6cac9285163654e","https://github.com/openssl/openssl/commit/4533ee8a5686c953ed3b644738ac4bdf20806538","https://github.com/openssl/openssl/commit/64d3102fb5b54311e92517f26ba00169d719e74a","https://github.com/openssl/openssl/commit/f9eaecf5bdd6692da052bc65b0332af2a938ac03","https://openssl-library.org/news/secadv/20260929.txt"],"severity":"Medium","namespace":"nvd:cpe","dataSource":"https://nvd.nist.gov/vuln/detail/CVE-2026-75804","description":"Issue summary: OpenSSL QUIC stack does not enforce connection\nlevel flow control for streams. Remote peers may send more bytes\nas long as they fit within the stream flow control limits.\n\nImpact summary: A malicious remote peer may exploit the lack of connection\nflow control for streams to make the QUIC stack receive ~100MB of memory\ninstead of 768 KiB (default flow control window size).\n\nCWE: CWE-770: Allocation of Resources Without Limits or Throttling\n\nDescription: The local QUIC stack advertises two flow control limits\nto its remote peer: stream flow control limit and connection flow\ncontrol limit. The remote peer must follow both limits when transmitting\nstream data.\n\nWhenever the local QUIC stack receives a stream frame, it validates\nthat the size of the received stream frame stays within flow control limits.\nIf either limit is exceeded (stream level or connection level), then\nthe QUIC stack must close the connection with a flow control error.\n\nThe vulnerable OpenSSL QUIC stack enforces the stream-level but not\nthe connection-level limit. To exploit the issue, three conditions must be met:\n  - the remote peer opens several streams\n  - each stream must stay within the stream-level flow control limit\n  - there must be no zero-offset byte sent on any of the streams\n    (to prevent the vulnerable QUIC stack from consuming data).\nBy meeting the conditions above, the remote peer may make the local stack\nallocate 2 x MAX_STREAMS x (stream flow control limit) bytes\nof memory. MAX_STREAMS defaults to 100, and the limit applies to both\nbidirectional and unidirectional streams, making it 200 in total. The default\nflow control window for a stream is 512kB. The remote peer may\nforce the vulnerable QUIC stack to allocate 100MB of heap per connection.\n\nFIPS impact: no\nThe FIPS module is not affected as the QUIC implementation is outside of\nthe OpenSSL FIPS module boundary."},{"id":"CVE-2026-75805","cvss":[{"type":"Secondary","source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","metrics":{"baseScore":5.3,"impactScore":1.5,"exploitabilityScore":3.9},"version":"3.1","vendorMetadata":{}}],"cwes":[{"cve":"CVE-2026-75805","cwe":"CWE-476","type":"Secondary","source":"openssl-security@openssl.org"}],"epss":[{"cve":"CVE-2026-75805","date":"2026-10-19","epss":0.00222,"percentile":0.11962}],"urls":["https://github.com/openssl/openssl/commit/7588db7fef14209c3caa3a101d11a02006b19166","https://github.com/openssl/openssl/commit/7ca0ccb5172a577e9b87267d77bfe21e5481a5e7","https://github.com/openssl/openssl/commit/9eb2a8a9b86136cdb39d6d7d50644dd66941cdc3","https://github.com/openssl/openssl/commit/abf02872a4b71767ecc72293424420f5b009190f","https://openssl-library.org/news/secadv/20260929.txt"],"severity":"Medium","namespace":"nvd:cpe","dataSource":"https://nvd.nist.gov/vuln/detail/CVE-2026-75805","description":"Issue summary: A CMP client that requests certificate revocation on the basis\nof a PKCS#10 CSR may dereference a NULL pointer and terminate abnormally when\nprocessing a crafted revocation response. \n\nImpact summary: The NULL pointer dereference happens on a read which \nleads to a crash and a Denial of Service for the affected client application.\n\nCWE: CWE-476: NULL-pointer dereference\n\nDescription: A CMP client revoking a certificate has to tell the server which\ncertificate to revoke, and may do so by supplying a PKCS#10 CSR instead of the\ncertificate itself or its issuer name and serial number. This is\n'openssl cmp -cmd rr -csr <file>' on the command line, or\nOSSL_CMP_exec_RR_ses() with the certificate supplied via\nOSSL_CMP_CTX_set1_p10CSR() through the API.\n\nA CSR does not contain the issuer name and serial number of the certificate,\nso the client does not send them. A server may optionally name the\ncertificate it revoked in its response, and the client then compares that\nname against what it sent. Having sent neither an issuer name nor a serial\nnumber, it has nothing to compare against, and a server returning a specially\ncrafted name causes the client to read from a NULL pointer and crash.\n\nThe revocation response is checked for valid message protection before\nthe affected code is reached, so an attacker must be a malicious or\ncompromised CMP server, or a man-in-the-middle in possession of the\nsecret used for message protection. Clients that identify the certificate\nto be revoked by a certificate or by issuer and serial number rather\nthan by a PKCS#10 CSR are not affected.\n\nFIPS impact: no\nNo FIPS modules are affected by this issue, as the CMP protocol\nimplementation is outside the OpenSSL FIPS module boundary."},{"id":"CVE-2026-75806","cvss":[{"type":"Secondary","source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","metrics":{"baseScore":5.3,"impactScore":1.5,"exploitabilityScore":3.9},"version":"3.1","vendorMetadata":{}}],"cwes":[{"cve":"CVE-2026-75806","cwe":"CWE-1284","type":"Secondary","source":"openssl-security@openssl.org"}],"epss":[{"cve":"CVE-2026-75806","date":"2026-10-19","epss":0.00387,"percentile":0.3128}],"urls":["https://github.com/openssl/openssl/commit/04728a289a823e68137f88da016cb9ede307217d","https://github.com/openssl/openssl/commit/050b275cd671a6eed1d6457642d41a5a77aab972","https://github.com/openssl/openssl/commit/3a4589d015a9049d47b66f186cf50a8711343a1d","https://github.com/openssl/openssl/commit/5af82fefbaf2b5fec2fc0e1d87f112844902f01d","https://openssl-library.org/news/secadv/20260929.txt"],"severity":"Medium","namespace":"nvd:cpe","dataSource":"https://nvd.nist.gov/vuln/detail/CVE-2026-75806","description":"Issue summary: An established DTLS 1.2 association using an AEAD cipher suite\ncan be terminated by a single unauthenticated datagram whose encrypted\nfragment is shorter than the mandatory explicit IV and authentication tag\noverhead.\n\nImpact summary: An attacker who can send a datagram that is routed to an\nexisting DTLS 1.2 association can tear that association down without knowing\nany key material. This is a Denial of Service limited to the targeted\nassociation. There is no memory safety or confidentiality impact.\n\nCWE: CWE-1284: Improper Validation of Specified Quantity in Input\n\nDescription: In TLS 1.2 and DTLS 1.2 every record protected by an AEAD cipher\nsuite carries an explicit IV followed by the ciphertext and an authentication\ntag. When decrypting such a record the record layer passed the record length to\nthe cipher implementation before checking that the record was long enough to\ncontain the explicit IV and the tag. For a record shorter than that overhead the\ncipher implementation rejected the impossible length, and the record layer\ntreated this as an internal failure and raised a fatal internal_error alert\ninstead of treating the record as one that failed authentication.\n\nIn TLS 1.2 the same record causes a fatal internal_error alert instead of the\nexpected bad_record_mac alert. Since any undecryptable record already\nterminates a TLS connection, this is a protocol conformance issue rather than\na security issue in TLS.\n\nThe fix validates the record length against the explicit IV and tag length\nbefore any AEAD processing, so that TLS reports bad_record_mac and DTLS\nsilently discards the record.\n\nFIPS impact: no\nThe affected code is outside the FIPS module boundary."},{"id":"CVE-2026-84782","cvss":[{"type":"Secondary","source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H","metrics":{"baseScore":8.2,"impactScore":4.3,"exploitabilityScore":3.9},"version":"3.1","vendorMetadata":{}}],"cwes":[{"cve":"CVE-2026-84782","cwe":"CWE-125","type":"Secondary","source":"openssl-security@openssl.org"}],"epss":[{"cve":"CVE-2026-84782","date":"2026-10-19","epss":0.0039,"percentile":0.31687}],"urls":["https://github.com/openssl/openssl/commit/906cf0ef1c85ca40ce69163e9086d6d3fe292943","https://github.com/openssl/openssl/commit/9f6b34422af7eb5dac61322e33dac1ae989fa628","https://github.com/openssl/openssl/commit/a383dafdd754eb5b22bf45e37e1bff9d07277a58","https://github.com/openssl/openssl/commit/d951e02ede8f6a6ff8150546db44b34f0518192c","https://openssl-library.org/news/secadv/20260929.txt"],"severity":"High","namespace":"nvd:cpe","dataSource":"https://nvd.nist.gov/vuln/detail/CVE-2026-84782","description":"Issue summary: The DTLS retransmission logic does not correctly handle\na handshake message write that is suspended part-way through.\nThe retransmitted message can be read past the message buffer and\nthe retransmission overwrites the internal state the suspended write\nneeds to resume correctly.\n\nImpact summary: The retransmitted message can disclose a heap memory\nto the peer as plaintext handshake data or cause a crash and a Denial\nof Service when the read reaches an unmapped memory region.\n\nCWE: CWE-125: Out-of-bounds Read\n\nDescription: DTLS handshake messages can be written out in multiple\nfragments, and a write can suspend mid-message (returning WANT_WRITE)\nif the underlying transport temporarily cannot accept more data. While\nsuch a write is suspended, the DTLS retransmission timer may\nindependently fire and ask the retransmission logic to resend an\nearlier, already-acknowledged-as-sent message from its retransmit\nqueue.\n\nThe retransmission logic reused the same internal buffer and position\ntracking as the message that was still being written, without\nresetting the position back to the start of the message being\nretransmitted. As a result the retransmission was read starting from\nwherever the suspended write had left off, producing a mislabelled\nmessage whose body was leftover bytes from the other, larger message\nstill in flight - content that was never meant to be sent at that\npoint, and which could run past the end of the allocated buffer.\n\nSeparately, even when the retransmission is positioned correctly,\nallowing it to run to completion while another write is suspended\noverwrites the same shared bookkeeping that the suspended write\ndepends on to resume. When the application later resumes the\nsuspended write (via a subsequent SSL_read(), SSL_write(),\nSSL_accept(), or SSL_connect() call), it finds that bookkeeping in a\nstate inconsistent with the message and aborts the process in\na debugging build.\n\nThe fix resets the retransmission's read position to the start of the\nmessage before resending, and skips retransmission entirely whenever a\nhandshake write is still suspended, deferring to the next call that\nresumes it instead.\n\nFIPS impact: no\nThe affected code is outside the FIPS module boundary."},{"id":"CVE-2026-84784","cvss":[{"type":"Secondary","source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","metrics":{"baseScore":7.5,"impactScore":3.6,"exploitabilityScore":3.9},"version":"3.1","vendorMetadata":{}}],"cwes":[{"cve":"CVE-2026-84784","cwe":"CWE-770","type":"Secondary","source":"openssl-security@openssl.org"}],"epss":[{"cve":"CVE-2026-84784","date":"2026-10-19","epss":0.00403,"percentile":0.33142}],"urls":["https://github.com/openssl/openssl/commit/4685c914b0d410b1034f40b547c95bc95e7a380a","https://github.com/openssl/openssl/commit/9a30fe0fba195c14e5b87bf93c0d0fdb70373806","https://github.com/openssl/openssl/commit/dba3c48d653c64fcbc9070a17a0ee2b3e2f3af1f","https://github.com/openssl/openssl/commit/e9e5155833fa968bee50024bf9ca3a185ab599fe","https://openssl-library.org/news/secadv/20260929.txt"],"severity":"High","namespace":"nvd:cpe","dataSource":"https://nvd.nist.gov/vuln/detail/CVE-2026-84784","description":"Issue summary: A malicious remote peer may flood the local QUIC\nstack with NEW_CONNECTION_ID frames by avoiding a limit check on\nhow many connection IDs the remote QUIC stack can use.\n\nImpact summary: The local QUIC stack sends a RETIRE_CONN_ID frame\nfor every NEW_CONNECTION_ID frame it receives. The RETIRE_CONN_ID\nframe is dispatched via the Control Frame Queue (CFQ). If the remote\npeer also withholds ACKs, then it can force the local stack\nto allocate ~400MB (depending on ACK delay).\n\nCWE: CWE-770: Allocation of Resources Without Limits or Throttling\n\nDescription: RFC 9000 sections 5.1.1 and 5.1.2 [1] describe the mechanism\nby which a remote peer can notify the local QUIC stack to change the\ndestination connection ID (a.k.a. CID) the local stack uses to\nidentify the connection at the remote peer. Each CID is associated\nwith a sequence number. The sequence number is transmitted\nin NEW_CONNECTION_ID and RETIRE_CONNECTION_ID frames to identify the CID\nwhich is being either associated with a connection or retired.\n\nThe remote peer sends a NEW_CONNECTION_ID frame to let the local stack know\na new CID is being associated with an existing connection. The\nNEW_CONNECTION_ID frame carries the new CID, its sequence number, and the\nretire-prior-to number. The retire-prior-to identifies existing\nCIDs that are to be retired. The local QUIC stack must send a\nRETIRE_CONNECTION_ID for every destination CID whose sequence number\nis less than retire-prior-to. The CID becomes retired after the\nlocal stack receives an ACK for its RETIRE_CONNECTION_ID frame.\n\nAlthough the OpenSSL QUIC stack supports at most one destination CID\nfor every connection, it can be tricked into processing more than\none RETIRE_CONNECTION_ID frame per connection. The OpenSSL QUIC\nstack currently retires the destination CID as soon as it receives\nthe NEW_CONNECTION_ID, while in fact the destination CID must\nbe retired after an ACK for the RETIRE_CONNECTION_ID frame is received.\nCorrecting the flawed logic also fixes the backlog growth.\n\n[1] https://datatracker.ietf.org/doc/html/rfc9000#name-issuing-connection-ids\n\nFIPS impact: no\nThe FIPS module is not affected as the QUIC implementation is outside of\nthe OpenSSL FIPS module boundary."}]},{"artifact":{"id":"09a9e7a8c48db103","cpes":["cpe:2.3:a:amazonlinux:bind-libs:32\\:9.18.50-1.amzn2023.0.3:*:*:*:*:*:*:*","cpe:2.3:a:amazonlinux:bind_libs:32\\:9.18.50-1.amzn2023.0.3:*:*:*:*:*:*:*","cpe:2.3:a:bind-libs:bind-libs:32\\:9.18.50-1.amzn2023.0.3:*:*:*:*:*:*:*","cpe:2.3:a:bind-libs:bind_libs:32\\:9.18.50-1.amzn2023.0.3:*:*:*:*:*:*:*","cpe:2.3:a:bind_libs:bind-libs:32\\:9.18.50-1.amzn2023.0.3:*:*:*:*:*:*:*","cpe:2.3:a:bind_libs:bind_libs:32\\:9.18.50-1.amzn2023.0.3:*:*:*:*:*:*:*","cpe:2.3:a:bind:bind-libs:32\\:9.18.50-1.amzn2023.0.3:*:*:*:*:*:*:*","cpe:2.3:a:bind:bind_libs:32\\:9.18.50-1.amzn2023.0.3:*:*:*:*:*:*:*"],"name":"bind-libs","purl":"pkg:rpm/amzn/bind-libs@9.18.50-1.amzn2023.0.3?arch=x86_64&distro=amzn-2023&epoch=32&upstream=bind-9.18.50-1.amzn2023.0.3.src.rpm","type":"rpm","version":"32:9.18.50-1.amzn2023.0.3","language":"","licenses":["MPL-2.0 AND ISC AND MIT AND BSD-3-Clause AND BSD-2-Clause"],"metadata":{"epoch":32,"architecture":"x86_64","modularityLabel":""},"locations":[{"path":"/var/lib/rpm/rpmdb.sqlite","layerID":"sha256:36ecccff5cdfa790aa570cb6cbe04b052333d62b672dac330d047934181da1ac","accessPath":"/var/lib/rpm/rpmdb.sqlite","annotations":{"evidence":"primary"}}],"upstreams":[{"name":"bind","version":"9.18.50-1.amzn2023.0.3"}],"metadataType":"RpmMetadata"},"matchDetails":[{"fix":{"suggestedVersion":"9.18.50-1.amzn2023.0.4"},"type":"exact-direct-match","found":{"vulnerabilityID":"ALAS2023-2026-3221","versionConstraint":"< 9.18.50-1.amzn2023.0.4 (rpm)"},"matcher":"rpm-matcher","searchedBy":{"distro":{"type":"amazonlinux","version":"2023"},"package":{"name":"bind-libs","version":"32:9.18.50-1.amzn2023.0.3"},"namespace":"amazon:distro:amazonlinux:2023"}},{"fix":{"suggestedVersion":"9.18.50-1.amzn2023.0.4"},"type":"exact-indirect-match","found":{"vulnerabilityID":"ALAS2023-2026-3221","versionConstraint":"< 9.18.50-1.amzn2023.0.4 (rpm)"},"matcher":"rpm-matcher","searchedBy":{"distro":{"type":"amazonlinux","version":"2023"},"package":{"name":"bind","version":"9.18.50-1.amzn2023.0.3"},"namespace":"amazon:distro:amazonlinux:2023"}}],"vulnerability":{"id":"ALAS2023-2026-3221","fix":{"state":"fixed","versions":["9.18.50-1.amzn2023.0.4"],"available":[{"date":"2026-10-14","kind":"advisory","version":"9.18.50-1.amzn2023.0.4"}]},"cvss":[],"risk":0,"urls":[],"severity":"High","namespace":"amazon:distro:amazonlinux:2023","advisories":[],"dataSource":"https://alas.aws.amazon.com/AL2023/ALAS2023-2026-3221.html","description":"Amazon Linux–vended DNS resolvers shipped with an older DNSSEC root signing key. For hosts configured with DNSSEC validation enabled, this could result in DNS resolution failures, including for names in unsigned zones. This applies where the resolver is still using the trust anchor shipped in the package; resolvers that already picked up the new root key via RFC 5011 are unaffected.On 11 October 2026 at 14:00 UTC the DNS root zone began signing with KSK-2024 (key tag 38696), replacing KSK-2017 (key tag 20326). The packaged trust anchor files contained only KSK-2017, so an affected resolver cannot validate the root DNSKEY RRset and returns SERVFAIL.The updated packages include an updated root signing key."},"relatedVulnerabilities":[]},{"artifact":{"id":"2a445e32fbad077c","cpes":["cpe:2.3:a:bind-license:bind-license:32\\:9.18.50-1.amzn2023.0.3:*:*:*:*:*:*:*","cpe:2.3:a:bind-license:bind_license:32\\:9.18.50-1.amzn2023.0.3:*:*:*:*:*:*:*","cpe:2.3:a:bind_license:bind-license:32\\:9.18.50-1.amzn2023.0.3:*:*:*:*:*:*:*","cpe:2.3:a:bind_license:bind_license:32\\:9.18.50-1.amzn2023.0.3:*:*:*:*:*:*:*","cpe:2.3:a:amazonlinux:bind-license:32\\:9.18.50-1.amzn2023.0.3:*:*:*:*:*:*:*","cpe:2.3:a:amazonlinux:bind_license:32\\:9.18.50-1.amzn2023.0.3:*:*:*:*:*:*:*","cpe:2.3:a:bind:bind-license:32\\:9.18.50-1.amzn2023.0.3:*:*:*:*:*:*:*","cpe:2.3:a:bind:bind_license:32\\:9.18.50-1.amzn2023.0.3:*:*:*:*:*:*:*"],"name":"bind-license","purl":"pkg:rpm/amzn/bind-license@9.18.50-1.amzn2023.0.3?arch=noarch&distro=amzn-2023&epoch=32&upstream=bind-9.18.50-1.amzn2023.0.3.src.rpm","type":"rpm","version":"32:9.18.50-1.amzn2023.0.3","language":"","licenses":["MPL-2.0 AND ISC AND MIT AND BSD-3-Clause AND BSD-2-Clause"],"metadata":{"epoch":32,"architecture":"noarch","modularityLabel":""},"locations":[{"path":"/var/lib/rpm/rpmdb.sqlite","layerID":"sha256:36ecccff5cdfa790aa570cb6cbe04b052333d62b672dac330d047934181da1ac","accessPath":"/var/lib/rpm/rpmdb.sqlite","annotations":{"evidence":"primary"}}],"upstreams":[{"name":"bind","version":"9.18.50-1.amzn2023.0.3"}],"metadataType":"RpmMetadata"},"matchDetails":[{"fix":{"suggestedVersion":"9.18.50-1.amzn2023.0.4"},"type":"exact-direct-match","found":{"vulnerabilityID":"ALAS2023-2026-3221","versionConstraint":"< 9.18.50-1.amzn2023.0.4 (rpm)"},"matcher":"rpm-matcher","searchedBy":{"distro":{"type":"amazonlinux","version":"2023"},"package":{"name":"bind-license","version":"32:9.18.50-1.amzn2023.0.3"},"namespace":"amazon:distro:amazonlinux:2023"}},{"fix":{"suggestedVersion":"9.18.50-1.amzn2023.0.4"},"type":"exact-indirect-match","found":{"vulnerabilityID":"ALAS2023-2026-3221","versionConstraint":"< 9.18.50-1.amzn2023.0.4 (rpm)"},"matcher":"rpm-matcher","searchedBy":{"distro":{"type":"amazonlinux","version":"2023"},"package":{"name":"bind","version":"9.18.50-1.amzn2023.0.3"},"namespace":"amazon:distro:amazonlinux:2023"}}],"vulnerability":{"id":"ALAS2023-2026-3221","fix":{"state":"fixed","versions":["9.18.50-1.amzn2023.0.4"],"available":[{"date":"2026-10-14","kind":"advisory","version":"9.18.50-1.amzn2023.0.4"}]},"cvss":[],"risk":0,"urls":[],"severity":"High","namespace":"amazon:distro:amazonlinux:2023","advisories":[],"dataSource":"https://alas.aws.amazon.com/AL2023/ALAS2023-2026-3221.html","description":"Amazon Linux–vended DNS resolvers shipped with an older DNSSEC root signing key. For hosts configured with DNSSEC validation enabled, this could result in DNS resolution failures, including for names in unsigned zones. This applies where the resolver is still using the trust anchor shipped in the package; resolvers that already picked up the new root key via RFC 5011 are unaffected.On 11 October 2026 at 14:00 UTC the DNS root zone began signing with KSK-2024 (key tag 38696), replacing KSK-2017 (key tag 20326). The packaged trust anchor files contained only KSK-2017, so an affected resolver cannot validate the root DNSKEY RRset and returns SERVFAIL.The updated packages include an updated root signing key."},"relatedVulnerabilities":[]},{"artifact":{"id":"8b51a3343ea1d997","cpes":["cpe:2.3:a:amazonlinux:bind-utils:32\\:9.18.50-1.amzn2023.0.3:*:*:*:*:*:*:*","cpe:2.3:a:amazonlinux:bind_utils:32\\:9.18.50-1.amzn2023.0.3:*:*:*:*:*:*:*","cpe:2.3:a:bind-utils:bind-utils:32\\:9.18.50-1.amzn2023.0.3:*:*:*:*:*:*:*","cpe:2.3:a:bind-utils:bind_utils:32\\:9.18.50-1.amzn2023.0.3:*:*:*:*:*:*:*","cpe:2.3:a:bind_utils:bind-utils:32\\:9.18.50-1.amzn2023.0.3:*:*:*:*:*:*:*","cpe:2.3:a:bind_utils:bind_utils:32\\:9.18.50-1.amzn2023.0.3:*:*:*:*:*:*:*","cpe:2.3:a:bind:bind-utils:32\\:9.18.50-1.amzn2023.0.3:*:*:*:*:*:*:*","cpe:2.3:a:bind:bind_utils:32\\:9.18.50-1.amzn2023.0.3:*:*:*:*:*:*:*"],"name":"bind-utils","purl":"pkg:rpm/amzn/bind-utils@9.18.50-1.amzn2023.0.3?arch=x86_64&distro=amzn-2023&epoch=32&upstream=bind-9.18.50-1.amzn2023.0.3.src.rpm","type":"rpm","version":"32:9.18.50-1.amzn2023.0.3","language":"","licenses":["MPL-2.0 AND ISC AND MIT AND BSD-3-Clause AND BSD-2-Clause"],"metadata":{"epoch":32,"architecture":"x86_64","modularityLabel":""},"locations":[{"path":"/var/lib/rpm/rpmdb.sqlite","layerID":"sha256:36ecccff5cdfa790aa570cb6cbe04b052333d62b672dac330d047934181da1ac","accessPath":"/var/lib/rpm/rpmdb.sqlite","annotations":{"evidence":"primary"}}],"upstreams":[{"name":"bind","version":"9.18.50-1.amzn2023.0.3"}],"metadataType":"RpmMetadata"},"matchDetails":[{"fix":{"suggestedVersion":"9.18.50-1.amzn2023.0.4"},"type":"exact-direct-match","found":{"vulnerabilityID":"ALAS2023-2026-3221","versionConstraint":"< 9.18.50-1.amzn2023.0.4 (rpm)"},"matcher":"rpm-matcher","searchedBy":{"distro":{"type":"amazonlinux","version":"2023"},"package":{"name":"bind-utils","version":"32:9.18.50-1.amzn2023.0.3"},"namespace":"amazon:distro:amazonlinux:2023"}},{"fix":{"suggestedVersion":"9.18.50-1.amzn2023.0.4"},"type":"exact-indirect-match","found":{"vulnerabilityID":"ALAS2023-2026-3221","versionConstraint":"< 9.18.50-1.amzn2023.0.4 (rpm)"},"matcher":"rpm-matcher","searchedBy":{"distro":{"type":"amazonlinux","version":"2023"},"package":{"name":"bind","version":"9.18.50-1.amzn2023.0.3"},"namespace":"amazon:distro:amazonlinux:2023"}}],"vulnerability":{"id":"ALAS2023-2026-3221","fix":{"state":"fixed","versions":["9.18.50-1.amzn2023.0.4"],"available":[{"date":"2026-10-14","kind":"advisory","version":"9.18.50-1.amzn2023.0.4"}]},"cvss":[],"risk":0,"urls":[],"severity":"High","namespace":"amazon:distro:amazonlinux:2023","advisories":[],"dataSource":"https://alas.aws.amazon.com/AL2023/ALAS2023-2026-3221.html","description":"Amazon Linux–vended DNS resolvers shipped with an older DNSSEC root signing key. For hosts configured with DNSSEC validation enabled, this could result in DNS resolution failures, including for names in unsigned zones. This applies where the resolver is still using the trust anchor shipped in the package; resolvers that already picked up the new root key via RFC 5011 are unaffected.On 11 October 2026 at 14:00 UTC the DNS root zone began signing with KSK-2024 (key tag 38696), replacing KSK-2017 (key tag 20326). The packaged trust anchor files contained only KSK-2017, so an affected resolver cannot validate the root DNSKEY RRset and returns SERVFAIL.The updated packages include an updated root signing key."},"relatedVulnerabilities":[]},{"artifact":{"id":"6c3a9ab4a97bb4a7","cpes":["cpe:2.3:a:amazonlinux:systemd:252.23-14.amzn2023:*:*:*:*:*:*:*","cpe:2.3:a:systemd:systemd:252.23-14.amzn2023:*:*:*:*:*:*:*"],"name":"systemd","purl":"pkg:rpm/amzn/systemd@252.23-14.amzn2023?arch=x86_64&distro=amzn-2023&upstream=systemd-252.23-14.amzn2023.src.rpm","type":"rpm","version":"252.23-14.amzn2023","language":"","licenses":["LGPLv2+ and MIT and GPLv2+"],"metadata":{"epoch":null,"architecture":"x86_64","modularityLabel":""},"locations":[{"path":"/var/lib/rpm/rpmdb.sqlite","layerID":"sha256:36ecccff5cdfa790aa570cb6cbe04b052333d62b672dac330d047934181da1ac","accessPath":"/var/lib/rpm/rpmdb.sqlite","annotations":{"evidence":"primary"}}],"upstreams":[],"metadataType":"RpmMetadata"},"matchDetails":[{"fix":{"suggestedVersion":"252.23-15.amzn2023"},"type":"exact-direct-match","found":{"vulnerabilityID":"ALAS2023-2026-3224","versionConstraint":"< 252.23-15.amzn2023 (rpm)"},"matcher":"rpm-matcher","searchedBy":{"distro":{"type":"amazonlinux","version":"2023"},"package":{"name":"systemd","version":"0:252.23-14.amzn2023"},"namespace":"amazon:distro:amazonlinux:2023"}}],"vulnerability":{"id":"ALAS2023-2026-3224","fix":{"state":"fixed","versions":["252.23-15.amzn2023"],"available":[{"date":"2026-10-14","kind":"advisory","version":"252.23-15.amzn2023"}]},"cvss":[],"risk":0,"urls":[],"severity":"High","namespace":"amazon:distro:amazonlinux:2023","advisories":[],"dataSource":"https://alas.aws.amazon.com/AL2023/ALAS2023-2026-3224.html","description":"Amazon Linux–vended DNS resolvers shipped with an older DNSSEC root signing key. For hosts configured with DNSSEC validation enabled, this could result in DNS resolution failures, including for names in unsigned zones. This applies where the resolver is still using the trust anchor shipped in the package; resolvers that already picked up the new root key via RFC 5011 are unaffected.On 11 October 2026 at 14:00 UTC the DNS root zone began signing with KSK-2024 (key tag 38696), replacing KSK-2017 (key tag 20326). The packaged trust anchor files contained only KSK-2017, so an affected resolver cannot validate the root DNSKEY RRset and returns SERVFAIL.The updated packages include an updated root signing key."},"relatedVulnerabilities":[]},{"artifact":{"id":"84c83370d47efe20","cpes":["cpe:2.3:a:systemd-libs:systemd-libs:252.23-14.amzn2023:*:*:*:*:*:*:*","cpe:2.3:a:systemd-libs:systemd_libs:252.23-14.amzn2023:*:*:*:*:*:*:*","cpe:2.3:a:systemd_libs:systemd-libs:252.23-14.amzn2023:*:*:*:*:*:*:*","cpe:2.3:a:systemd_libs:systemd_libs:252.23-14.amzn2023:*:*:*:*:*:*:*","cpe:2.3:a:amazonlinux:systemd-libs:252.23-14.amzn2023:*:*:*:*:*:*:*","cpe:2.3:a:amazonlinux:systemd_libs:252.23-14.amzn2023:*:*:*:*:*:*:*","cpe:2.3:a:systemd:systemd-libs:252.23-14.amzn2023:*:*:*:*:*:*:*","cpe:2.3:a:systemd:systemd_libs:252.23-14.amzn2023:*:*:*:*:*:*:*"],"name":"systemd-libs","purl":"pkg:rpm/amzn/systemd-libs@252.23-14.amzn2023?arch=x86_64&distro=amzn-2023&upstream=systemd-252.23-14.amzn2023.src.rpm","type":"rpm","version":"252.23-14.amzn2023","language":"","licenses":["LGPLv2+ and MIT"],"metadata":{"epoch":null,"architecture":"x86_64","modularityLabel":""},"locations":[{"path":"/var/lib/rpm/rpmdb.sqlite","layerID":"sha256:36ecccff5cdfa790aa570cb6cbe04b052333d62b672dac330d047934181da1ac","accessPath":"/var/lib/rpm/rpmdb.sqlite","annotations":{"evidence":"primary"}}],"upstreams":[{"name":"systemd","version":"252.23-14.amzn2023"}],"metadataType":"RpmMetadata"},"matchDetails":[{"fix":{"suggestedVersion":"252.23-15.amzn2023"},"type":"exact-direct-match","found":{"vulnerabilityID":"ALAS2023-2026-3224","versionConstraint":"< 252.23-15.amzn2023 (rpm)"},"matcher":"rpm-matcher","searchedBy":{"distro":{"type":"amazonlinux","version":"2023"},"package":{"name":"systemd-libs","version":"0:252.23-14.amzn2023"},"namespace":"amazon:distro:amazonlinux:2023"}},{"fix":{"suggestedVersion":"252.23-15.amzn2023"},"type":"exact-indirect-match","found":{"vulnerabilityID":"ALAS2023-2026-3224","versionConstraint":"< 252.23-15.amzn2023 (rpm)"},"matcher":"rpm-matcher","searchedBy":{"distro":{"type":"amazonlinux","version":"2023"},"package":{"name":"systemd","version":"252.23-14.amzn2023"},"namespace":"amazon:distro:amazonlinux:2023"}}],"vulnerability":{"id":"ALAS2023-2026-3224","fix":{"state":"fixed","versions":["252.23-15.amzn2023"],"available":[{"date":"2026-10-14","kind":"advisory","version":"252.23-15.amzn2023"}]},"cvss":[],"risk":0,"urls":[],"severity":"High","namespace":"amazon:distro:amazonlinux:2023","advisories":[],"dataSource":"https://alas.aws.amazon.com/AL2023/ALAS2023-2026-3224.html","description":"Amazon Linux–vended DNS resolvers shipped with an older DNSSEC root signing key. For hosts configured with DNSSEC validation enabled, this could result in DNS resolution failures, including for names in unsigned zones. This applies where the resolver is still using the trust anchor shipped in the package; resolvers that already picked up the new root key via RFC 5011 are unaffected.On 11 October 2026 at 14:00 UTC the DNS root zone began signing with KSK-2024 (key tag 38696), replacing KSK-2017 (key tag 20326). The packaged trust anchor files contained only KSK-2017, so an affected resolver cannot validate the root DNSKEY RRset and returns SERVFAIL.The updated packages include an updated root signing key."},"relatedVulnerabilities":[]},{"artifact":{"id":"be097dc2f06b3ad3","cpes":["cpe:2.3:a:systemd-networkd:systemd-networkd:252.23-14.amzn2023:*:*:*:*:*:*:*","cpe:2.3:a:systemd-networkd:systemd_networkd:252.23-14.amzn2023:*:*:*:*:*:*:*","cpe:2.3:a:systemd_networkd:systemd-networkd:252.23-14.amzn2023:*:*:*:*:*:*:*","cpe:2.3:a:systemd_networkd:systemd_networkd:252.23-14.amzn2023:*:*:*:*:*:*:*","cpe:2.3:a:amazonlinux:systemd-networkd:252.23-14.amzn2023:*:*:*:*:*:*:*","cpe:2.3:a:amazonlinux:systemd_networkd:252.23-14.amzn2023:*:*:*:*:*:*:*","cpe:2.3:a:systemd:systemd-networkd:252.23-14.amzn2023:*:*:*:*:*:*:*","cpe:2.3:a:systemd:systemd_networkd:252.23-14.amzn2023:*:*:*:*:*:*:*"],"name":"systemd-networkd","purl":"pkg:rpm/amzn/systemd-networkd@252.23-14.amzn2023?arch=x86_64&distro=amzn-2023&upstream=systemd-252.23-14.amzn2023.src.rpm","type":"rpm","version":"252.23-14.amzn2023","language":"","licenses":["LGPLv2+"],"metadata":{"epoch":null,"architecture":"x86_64","modularityLabel":""},"locations":[{"path":"/var/lib/rpm/rpmdb.sqlite","layerID":"sha256:36ecccff5cdfa790aa570cb6cbe04b052333d62b672dac330d047934181da1ac","accessPath":"/var/lib/rpm/rpmdb.sqlite","annotations":{"evidence":"primary"}}],"upstreams":[{"name":"systemd","version":"252.23-14.amzn2023"}],"metadataType":"RpmMetadata"},"matchDetails":[{"fix":{"suggestedVersion":"252.23-15.amzn2023"},"type":"exact-direct-match","found":{"vulnerabilityID":"ALAS2023-2026-3224","versionConstraint":"< 252.23-15.amzn2023 (rpm)"},"matcher":"rpm-matcher","searchedBy":{"distro":{"type":"amazonlinux","version":"2023"},"package":{"name":"systemd-networkd","version":"0:252.23-14.amzn2023"},"namespace":"amazon:distro:amazonlinux:2023"}},{"fix":{"suggestedVersion":"252.23-15.amzn2023"},"type":"exact-indirect-match","found":{"vulnerabilityID":"ALAS2023-2026-3224","versionConstraint":"< 252.23-15.amzn2023 (rpm)"},"matcher":"rpm-matcher","searchedBy":{"distro":{"type":"amazonlinux","version":"2023"},"package":{"name":"systemd","version":"252.23-14.amzn2023"},"namespace":"amazon:distro:amazonlinux:2023"}}],"vulnerability":{"id":"ALAS2023-2026-3224","fix":{"state":"fixed","versions":["252.23-15.amzn2023"],"available":[{"date":"2026-10-14","kind":"advisory","version":"252.23-15.amzn2023"}]},"cvss":[],"risk":0,"urls":[],"severity":"High","namespace":"amazon:distro:amazonlinux:2023","advisories":[],"dataSource":"https://alas.aws.amazon.com/AL2023/ALAS2023-2026-3224.html","description":"Amazon Linux–vended DNS resolvers shipped with an older DNSSEC root signing key. For hosts configured with DNSSEC validation enabled, this could result in DNS resolution failures, including for names in unsigned zones. This applies where the resolver is still using the trust anchor shipped in the package; resolvers that already picked up the new root key via RFC 5011 are unaffected.On 11 October 2026 at 14:00 UTC the DNS root zone began signing with KSK-2024 (key tag 38696), replacing KSK-2017 (key tag 20326). The packaged trust anchor files contained only KSK-2017, so an affected resolver cannot validate the root DNSKEY RRset and returns SERVFAIL.The updated packages include an updated root signing key."},"relatedVulnerabilities":[]},{"artifact":{"id":"2cf1ba3ae6b62552","cpes":["cpe:2.3:a:amazonlinux:systemd-pam:252.23-14.amzn2023:*:*:*:*:*:*:*","cpe:2.3:a:amazonlinux:systemd_pam:252.23-14.amzn2023:*:*:*:*:*:*:*","cpe:2.3:a:systemd-pam:systemd-pam:252.23-14.amzn2023:*:*:*:*:*:*:*","cpe:2.3:a:systemd-pam:systemd_pam:252.23-14.amzn2023:*:*:*:*:*:*:*","cpe:2.3:a:systemd_pam:systemd-pam:252.23-14.amzn2023:*:*:*:*:*:*:*","cpe:2.3:a:systemd_pam:systemd_pam:252.23-14.amzn2023:*:*:*:*:*:*:*","cpe:2.3:a:systemd:systemd-pam:252.23-14.amzn2023:*:*:*:*:*:*:*","cpe:2.3:a:systemd:systemd_pam:252.23-14.amzn2023:*:*:*:*:*:*:*"],"name":"systemd-pam","purl":"pkg:rpm/amzn/systemd-pam@252.23-14.amzn2023?arch=x86_64&distro=amzn-2023&upstream=systemd-252.23-14.amzn2023.src.rpm","type":"rpm","version":"252.23-14.amzn2023","language":"","licenses":["LGPLv2+ and MIT and GPLv2+"],"metadata":{"epoch":null,"architecture":"x86_64","modularityLabel":""},"locations":[{"path":"/var/lib/rpm/rpmdb.sqlite","layerID":"sha256:36ecccff5cdfa790aa570cb6cbe04b052333d62b672dac330d047934181da1ac","accessPath":"/var/lib/rpm/rpmdb.sqlite","annotations":{"evidence":"primary"}}],"upstreams":[{"name":"systemd","version":"252.23-14.amzn2023"}],"metadataType":"RpmMetadata"},"matchDetails":[{"fix":{"suggestedVersion":"252.23-15.amzn2023"},"type":"exact-direct-match","found":{"vulnerabilityID":"ALAS2023-2026-3224","versionConstraint":"< 252.23-15.amzn2023 (rpm)"},"matcher":"rpm-matcher","searchedBy":{"distro":{"type":"amazonlinux","version":"2023"},"package":{"name":"systemd-pam","version":"0:252.23-14.amzn2023"},"namespace":"amazon:distro:amazonlinux:2023"}},{"fix":{"suggestedVersion":"252.23-15.amzn2023"},"type":"exact-indirect-match","found":{"vulnerabilityID":"ALAS2023-2026-3224","versionConstraint":"< 252.23-15.amzn2023 (rpm)"},"matcher":"rpm-matcher","searchedBy":{"distro":{"type":"amazonlinux","version":"2023"},"package":{"name":"systemd","version":"252.23-14.amzn2023"},"namespace":"amazon:distro:amazonlinux:2023"}}],"vulnerability":{"id":"ALAS2023-2026-3224","fix":{"state":"fixed","versions":["252.23-15.amzn2023"],"available":[{"date":"2026-10-14","kind":"advisory","version":"252.23-15.amzn2023"}]},"cvss":[],"risk":0,"urls":[],"severity":"High","namespace":"amazon:distro:amazonlinux:2023","advisories":[],"dataSource":"https://alas.aws.amazon.com/AL2023/ALAS2023-2026-3224.html","description":"Amazon Linux–vended DNS resolvers shipped with an older DNSSEC root signing key. For hosts configured with DNSSEC validation enabled, this could result in DNS resolution failures, including for names in unsigned zones. This applies where the resolver is still using the trust anchor shipped in the package; resolvers that already picked up the new root key via RFC 5011 are unaffected.On 11 October 2026 at 14:00 UTC the DNS root zone began signing with KSK-2024 (key tag 38696), replacing KSK-2017 (key tag 20326). The packaged trust anchor files contained only KSK-2017, so an affected resolver cannot validate the root DNSKEY RRset and returns SERVFAIL.The updated packages include an updated root signing key."},"relatedVulnerabilities":[]},{"artifact":{"id":"d4fdb123781c513a","cpes":["cpe:2.3:a:systemd-resolved:systemd-resolved:252.23-14.amzn2023:*:*:*:*:*:*:*","cpe:2.3:a:systemd-resolved:systemd_resolved:252.23-14.amzn2023:*:*:*:*:*:*:*","cpe:2.3:a:systemd_resolved:systemd-resolved:252.23-14.amzn2023:*:*:*:*:*:*:*","cpe:2.3:a:systemd_resolved:systemd_resolved:252.23-14.amzn2023:*:*:*:*:*:*:*","cpe:2.3:a:amazonlinux:systemd-resolved:252.23-14.amzn2023:*:*:*:*:*:*:*","cpe:2.3:a:amazonlinux:systemd_resolved:252.23-14.amzn2023:*:*:*:*:*:*:*","cpe:2.3:a:systemd:systemd-resolved:252.23-14.amzn2023:*:*:*:*:*:*:*","cpe:2.3:a:systemd:systemd_resolved:252.23-14.amzn2023:*:*:*:*:*:*:*"],"name":"systemd-resolved","purl":"pkg:rpm/amzn/systemd-resolved@252.23-14.amzn2023?arch=x86_64&distro=amzn-2023&upstream=systemd-252.23-14.amzn2023.src.rpm","type":"rpm","version":"252.23-14.amzn2023","language":"","licenses":["LGPLv2+ and MIT and GPLv2+"],"metadata":{"epoch":null,"architecture":"x86_64","modularityLabel":""},"locations":[{"path":"/var/lib/rpm/rpmdb.sqlite","layerID":"sha256:36ecccff5cdfa790aa570cb6cbe04b052333d62b672dac330d047934181da1ac","accessPath":"/var/lib/rpm/rpmdb.sqlite","annotations":{"evidence":"primary"}}],"upstreams":[{"name":"systemd","version":"252.23-14.amzn2023"}],"metadataType":"RpmMetadata"},"matchDetails":[{"fix":{"suggestedVersion":"252.23-15.amzn2023"},"type":"exact-direct-match","found":{"vulnerabilityID":"ALAS2023-2026-3224","versionConstraint":"< 252.23-15.amzn2023 (rpm)"},"matcher":"rpm-matcher","searchedBy":{"distro":{"type":"amazonlinux","version":"2023"},"package":{"name":"systemd-resolved","version":"0:252.23-14.amzn2023"},"namespace":"amazon:distro:amazonlinux:2023"}},{"fix":{"suggestedVersion":"252.23-15.amzn2023"},"type":"exact-indirect-match","found":{"vulnerabilityID":"ALAS2023-2026-3224","versionConstraint":"< 252.23-15.amzn2023 (rpm)"},"matcher":"rpm-matcher","searchedBy":{"distro":{"type":"amazonlinux","version":"2023"},"package":{"name":"systemd","version":"252.23-14.amzn2023"},"namespace":"amazon:distro:amazonlinux:2023"}}],"vulnerability":{"id":"ALAS2023-2026-3224","fix":{"state":"fixed","versions":["252.23-15.amzn2023"],"available":[{"date":"2026-10-14","kind":"advisory","version":"252.23-15.amzn2023"}]},"cvss":[],"risk":0,"urls":[],"severity":"High","namespace":"amazon:distro:amazonlinux:2023","advisories":[],"dataSource":"https://alas.aws.amazon.com/AL2023/ALAS2023-2026-3224.html","description":"Amazon Linux–vended DNS resolvers shipped with an older DNSSEC root signing key. For hosts configured with DNSSEC validation enabled, this could result in DNS resolution failures, including for names in unsigned zones. This applies where the resolver is still using the trust anchor shipped in the package; resolvers that already picked up the new root key via RFC 5011 are unaffected.On 11 October 2026 at 14:00 UTC the DNS root zone began signing with KSK-2024 (key tag 38696), replacing KSK-2017 (key tag 20326). The packaged trust anchor files contained only KSK-2017, so an affected resolver cannot validate the root DNSKEY RRset and returns SERVFAIL.The updated packages include an updated root signing key."},"relatedVulnerabilities":[]}],"grade":"F","score":"17.00","as_of":"2026-10-20T08:02:14.529Z","grype_db_version":"2026-10-20T06:29:49.000Z"}