CVE-2026-84782
DTLS Retransmits Handshake Messages From a Stale Buffer Offset
Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly.
Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region.
CWE: CWE-125: Out-of-bounds Read
Description: DTLS handshake messages can be written out in multiple fragments, and a write can suspend mid-message (returning WANT_WRITE) if the underlying transport temporarily cannot accept more data. While such a write is suspended, the DTLS retransmission timer may independently fire and ask the retransmission logic to resend an earlier, already-acknowledged-as-sent message from its retransmit queue.
The retransmission logic reused the same internal buffer and position tracking as the message that was still being written, without resetting the position back to the start of the message being retransmitted. As a result the retransmission was read starting from wherever the suspended write had left off, producing a mislabelled message whose body was leftover bytes from the other, larger message still in flight - content that was never meant to be sent at that point, and which could run past the end of the allocated buffer.
Separately, even when the retransmission is positioned correctly, allowing it to run to completion while another write is suspended overwrites the same shared bookkeeping that the suspended write depends on to resume. When the application later resumes the suspended write (via a subsequent SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() call), it finds that bookkeeping in a state inconsistent with the message and aborts the process in a debugging build.
The fix resets the retransmission's read position to the start of the message before resending, and skips retransmission entirely whenever a handshake write is still suspended, deferring to the next call that resumes it instead.
FIPS impact: no The affected code is outside the FIPS module boundary.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- Low
- Integrity
- None
- Availability
- High
Exploit likelihood
What each source reports
CVE List Score used
DTLS Retransmits Handshake Messages From a Stale Buffer Offset
Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly.
Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region.
CWE: CWE-125: Out-of-bounds Read
Description: DTLS handshake messages can be written out in multiple fragments, and a write can suspend mid-message (returning WANT_WRITE) if the underlying transport temporarily cannot accept more data. While such a write is suspended, the DTLS retransmission timer may independently fire and ask the retransmission logic to resend an earlier, already-acknowledged-as-sent message from its retransmit queue.
The retransmission logic reused the same internal buffer and position tracking as the message that was still being written, without resetting the position back to the start of the message being retransmitted. As a result the retransmission was read starting from wherever the suspended write had left off, producing a mislabelled message whose body was leftover bytes from the other, larger message still in flight - content that was never meant to be sent at that point, and which could run past the end of the allocated buffer.
Separately, even when the retransmission is positioned correctly, allowing it to run to completion while another write is suspended overwrites the same shared bookkeeping that the suspended write depends on to resume. When the application later resumes the suspended write (via a subsequent SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() call), it finds that bookkeeping in a state inconsistent with the message and aborts the process in a debugging build.
The fix resets the retransmission's read position to the start of the message before resending, and skips retransmission entirely whenever a handshake write is still suspended, deferring to the next call that resumes it instead.
FIPS impact: no The affected code is outside the FIPS module boundary.
- Record
CVE-2026-84782- CVSS 3.1
- 8.2 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H - Weakness
- CWE-125
- Updated
- 2026-11-02
EUVDEUVD-2026-89013
Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly.
Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region.
CWE: CWE-125: Out-of-bounds Read
Description: DTLS handshake messages can be written out in multiple fragments, and a write can suspend mid-message (returning WANT_WRITE) if the underlying transport temporarily cannot accept more data. While such a write is suspended, the DTLS retransmission timer may independently fire and ask the retransmission logic to resend an earlier, already-acknowledged-as-sent message from its retransmit queue.
The retransmission logic reused the same internal buffer and position tracking as the message that was still being written, without resetting the position back to the start of the message being retransmitted. As a result the retransmission was read starting from wherever the suspended write had left off, producing a mislabelled message whose body was leftover bytes from the other, larger message still in flight - content that was never meant to be sent at that point, and which could run past the end of the allocated buffer.
Separately, even when the retransmission is positioned correctly, allowing it to run to completion while another write is suspended overwrites the same shared bookkeeping that the suspended write depends on to resume. When the application later resumes the suspended write (via a subsequent SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() call), it finds that bookkeeping in a state inconsistent with the message and aborts the process in a debugging build.
The fix resets the retransmission's read position to the start of the message before resending, and skips retransmission entirely whenever a handshake write is still suspended, deferring to the next call that resumes it instead.
FIPS impact: no The affected code is outside the FIPS module boundary.
- Record
EUVD-2026-89013- CVSS 3.1
- 8.2 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-6w84-hw79-7wgf
Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write...
Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly.
Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region.
CWE: CWE-125: Out-of-bounds Read
Description: DTLS handshake messages can be written out in multiple fragments, and a write can suspend mid-message (returning WANT_WRITE) if the underlying transport temporarily cannot accept more data. While such a write is suspended, the DTLS retransmission timer may independently fire and ask the retransmission logic to resend an earlier, already-acknowledged-as-sent message from its retransmit queue.
The retransmission logic reused the same internal buffer and position tracking as the message that was still being written, without resetting the position back to the start of the message being retransmitted. As a result the retransmission was read starting from wherever the suspended write had left off, producing a mislabelled message whose body was leftover bytes from the other, larger message still in flight - content that was never meant to be sent at that point, and which could run past the end of the allocated buffer.
Separately, even when the retransmission is positioned correctly, allowing it to run to completion while another write is suspended overwrites the same shared bookkeeping that the suspended write depends on to resume. When the application later resumes the suspended write (via a subsequent SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() call), it finds that bookkeeping in a state inconsistent with the message and aborts the process in a debugging build.
The fix resets the retransmission's read position to the start of the message before resending, and skips retransmission entirely whenever a handshake write is still suspended, deferring to the next call that resumes it instead.
FIPS impact: no The affected code is outside the FIPS module boundary.
- Record
GHSA-6w84-hw79-7wgf- CVSS 3.1
- 8.2 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H - Weakness
- CWE-125
- Updated
- 2026-11-02
NVD
Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly.
Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region.
CWE: CWE-125: Out-of-bounds Read
Description: DTLS handshake messages can be written out in multiple fragments, and a write can suspend mid-message (returning WANT_WRITE) if the underlying transport temporarily cannot accept more data. While such a write is suspended, the DTLS retransmission timer may independently fire and ask the retransmission logic to resend an earlier, already-acknowledged-as-sent message from its retransmit queue.
The retransmission logic reused the same internal buffer and position tracking as the message that was still being written, without resetting the position back to the start of the message being retransmitted. As a result the retransmission was read starting from wherever the suspended write had left off, producing a mislabelled message whose body was leftover bytes from the other, larger message still in flight - content that was never meant to be sent at that point, and which could run past the end of the allocated buffer.
Separately, even when the retransmission is positioned correctly, allowing it to run to completion while another write is suspended overwrites the same shared bookkeeping that the suspended write depends on to resume. When the application later resumes the suspended write (via a subsequent SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() call), it finds that bookkeeping in a state inconsistent with the message and aborts the process in a debugging build.
The fix resets the retransmission's read position to the start of the message before resending, and skips retransmission entirely whenever a handshake write is still suspended, deferring to the next call that resumes it instead.
FIPS impact: no The affected code is outside the FIPS module boundary.
- Record
CVE-2026-84782- CVSS 3.1
- 8.2 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H - Weakness
- CWE-125
- Updated
- 2026-11-02
OSVALPINE-CVE-2026-84782
Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly.
Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region.
CWE: CWE-125: Out-of-bounds Read
Description: DTLS handshake messages can be written out in multiple fragments, and a write can suspend mid-message (returning WANT_WRITE) if the underlying transport temporarily cannot accept more data. While such a write is suspended, the DTLS retransmission timer may independently fire and ask the retransmission logic to resend an earlier, already-acknowledged-as-sent message from its retransmit queue.
The retransmission logic reused the same internal buffer and position tracking as the message that was still being written, without resetting the position back to the start of the message being retransmitted. As a result the retransmission was read starting from wherever the suspended write had left off, producing a mislabelled message whose body was leftover bytes from the other, larger message still in flight - content that was never meant to be sent at that point, and which could run past the end of the allocated buffer.
Separately, even when the retransmission is positioned correctly, allowing it to run to completion while another write is suspended overwrites the same shared bookkeeping that the suspended write depends on to resume. When the application later resumes the suspended write (via a subsequent SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() call), it finds that bookkeeping in a state inconsistent with the message and aborts the process in a debugging build.
The fix resets the retransmission's read position to the start of the message before resending, and skips retransmission entirely whenever a handshake write is still suspended, deferring to the next call that resumes it instead.
FIPS impact: no The affected code is outside the FIPS module boundary.
- Record
ALPINE-CVE-2026-84782- CVSS 3.1
- 8.2 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H - Updated
- 2026-11-02
OSVBELL-CVE-2026-84782
- Record
BELL-CVE-2026-84782- CVSS 3.1
- 8.2 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H - Updated
- 2026-11-02
Show 48 moreShow less
OSV
DTLS Retransmits Handshake Messages From a Stale Buffer Offset
Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly.
Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region.
CWE: CWE-125: Out-of-bounds Read
Description: DTLS handshake messages can be written out in multiple fragments, and a write can suspend mid-message (returning WANT_WRITE) if the underlying transport temporarily cannot accept more data. While such a write is suspended, the DTLS retransmission timer may independently fire and ask the retransmission logic to resend an earlier, already-acknowledged-as-sent message from its retransmit queue.
The retransmission logic reused the same internal buffer and position tracking as the message that was still being written, without resetting the position back to the start of the message being retransmitted. As a result the retransmission was read starting from wherever the suspended write had left off, producing a mislabelled message whose body was leftover bytes from the other, larger message still in flight - content that was never meant to be sent at that point, and which could run past the end of the allocated buffer.
Separately, even when the retransmission is positioned correctly, allowing it to run to completion while another write is suspended overwrites the same shared bookkeeping that the suspended write depends on to resume. When the application later resumes the suspended write (via a subsequent SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() call), it finds that bookkeeping in a state inconsistent with the message and aborts the process in a debugging build.
The fix resets the retransmission's read position to the start of the message before resending, and skips retransmission entirely whenever a handshake write is still suspended, deferring to the next call that resumes it instead.
FIPS impact: no The affected code is outside the FIPS module boundary.
- Record
CVE-2026-84782- CVSS 3.1
- 8.2 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H - Weakness
- CWE-125
- Updated
- 2026-11-07
OSVDEBIAN-CVE-2026-84782
Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly. Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region. CWE: CWE-125: Out-of-bounds Read Description: DTLS handshake messages can be written out in multiple fragments, and a write can suspend mid-message (returning WANT_WRITE) if the underlying transport temporarily cannot accept more data. While such a write is suspended, the DTLS retransmission timer may independently fire and ask the retransmission logic to resend an earlier, already-acknowledged-as-sent message from its retransmit queue. The retransmission logic reused the same internal buffer and position tracking as the message that was still being written, without resetting the position back to the start of the message being retransmitted. As a result the retransmission was read starting from wherever the suspended write had left off, producing a mislabelled message whose body was leftover bytes from the other, larger message still in flight - content that was never meant to be sent at that point, and which could run past the end of the allocated buffer. Separately, even when the retransmission is positioned correctly, allowing it to run to completion while another write is suspended overwrites the same shared bookkeeping that the suspended write depends on to resume. When the application later resumes the suspended write (via a subsequent SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() call), it finds that bookkeeping in a state inconsistent with the message and aborts the process in a debugging build. The fix resets the retransmission's read position to the start of the message before resending, and skips retransmission entirely whenever a handshake write is still suspended, deferring to the next call that resumes it instead. FIPS impact: no The affected code is outside the FIPS module boundary.
- Record
DEBIAN-CVE-2026-84782- CVSS 3.1
- 8.2 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H - Updated
- 2026-11-02
OSVOESA-2026-4416
openssl security update
OpenSSL is a robust, commercial-grade, and full-featured toolkit for the Transport Layer Security (TLS) and Secure Sockets Layer (SSL) protocols.
Security Fix(es):
Issue summary: A certificate with many nameRelativeToCRLIssuer CRL distribution points causes disproportionate heap growth when OpenSSL caches X.509 extensions.
Impact summary: Receiving a crafted certificate from a malicious peer can lead to significant memory pressure and possible Denial of Service in clients or in servers that solicit client certificates.
CWE: CWE-770: Allocation of Resources Without Limits or Throttling
Description: A certificate or a set of certificates that fits under the limit for size of certificates accepted from the peer (~100 KiB) can result in allocation of several hundred MiB of resident memory on the receiving side during a normal TLS handshake. This may be enough to crash the client or server, if multiple concurrent connections lead to similarly large memory allocations.
The fix postpones processing of the CRL distribution points extensions in certificates to the time when the processed value is required for CRL processing. This avoids keeping large memory allocations for a long time when such certificates are received.
FIPS impact: no The affected code is outside the FIPS module boundary.(CVE-2026-35189)
Issue summary: The generic elliptic-curve scalar multiplication used for ECDSA and SM2 signature operations with curves that do not have a dedicated implementation leaks information about the secret nonce through timing.
Impact summary: An attacker able to measure signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key.
CWE: CWE-208: Observable Timing Discrepancy
Description: The generic elliptic-curve scalar multiplication used for curves that do not have a dedicated constant-time implementation pads the secret scalar with non-constant-time BIGNUM operations, so the time taken depends 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 of measurements. The effect is largest for curves whose group order lies on a machine-word boundary, such as brainpoolP384r1.
Applications using ECDSA signing over the Brainpool and other generic prime curves, 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-time implementations and are not affected.
FIPS Impact: no The FIPS modules are not affected: the approved NIST curves used in the FIPS provider have dedicated constant-time implementations and do not use the affected code path.(CVE-2026-54872)
Issue summary: An established DTLS 1.2 association using an AEAD cipher suite can be terminated by a single unauthenticated datagram whose encrypted fragment is shorter than the mandatory explicit IV and authentication tag overhead.
Impact summary: An attacker who can send a datagram that is routed to an existing DTLS 1.2 association can tear that association down without knowing any key material. This is a Denial of Service limited to the targeted association. There is no memory safety or confidentiality impact.
CWE: CWE-1284: Improper Validation of Specified Quantity in Input
Description: In TLS 1.2 and DTLS 1.2 every record protected by an AEAD cipher suite carries an explicit IV followed by the ciphertext and an authentication tag. When decrypting such a record the record layer passed the record length to the cipher implementation before checking that the record was long enough to contain the explicit IV and the tag. For a record shorter than that overhead the cipher implementation rejected the impossible length, and the record layer treated this as an internal failure and raised a fatal internal_error alert instead of treating the record as one that failed…
- Record
OESA-2026-4416- CVSS 3.1
- 8.2 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H - Updated
- 2026-11-02
OSVOESA-2026-4417
openssl security update
OpenSSL is a robust, commercial-grade, and full-featured toolkit for the Transport Layer Security (TLS) and Secure Sockets Layer (SSL) protocols.
Security Fix(es):
Issue summary: A certificate with many nameRelativeToCRLIssuer CRL distribution points causes disproportionate heap growth when OpenSSL caches X.509 extensions.
Impact summary: Receiving a crafted certificate from a malicious peer can lead to significant memory pressure and possible Denial of Service in clients or in servers that solicit client certificates.
CWE: CWE-770: Allocation of Resources Without Limits or Throttling
Description: A certificate or a set of certificates that fits under the limit for size of certificates accepted from the peer (~100 KiB) can result in allocation of several hundred MiB of resident memory on the receiving side during a normal TLS handshake. This may be enough to crash the client or server, if multiple concurrent connections lead to similarly large memory allocations.
The fix postpones processing of the CRL distribution points extensions in certificates to the time when the processed value is required for CRL processing. This avoids keeping large memory allocations for a long time when such certificates are received.
FIPS impact: no The affected code is outside the FIPS module boundary.(CVE-2026-35189)
Issue summary: The generic elliptic-curve scalar multiplication used for ECDSA and SM2 signature operations with curves that do not have a dedicated implementation leaks information about the secret nonce through timing.
Impact summary: An attacker able to measure signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key.
CWE: CWE-208: Observable Timing Discrepancy
Description: The generic elliptic-curve scalar multiplication used for curves that do not have a dedicated constant-time implementation pads the secret scalar with non-constant-time BIGNUM operations, so the time taken depends 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 of measurements. The effect is largest for curves whose group order lies on a machine-word boundary, such as brainpoolP384r1.
Applications using ECDSA signing over the Brainpool and other generic prime curves, 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-time implementations and are not affected.
FIPS Impact: no The FIPS modules are not affected: the approved NIST curves used in the FIPS provider have dedicated constant-time implementations and do not use the affected code path.(CVE-2026-54872)
Issue summary: A CMP client that requests certificate revocation on the basis of a PKCS#10 CSR may dereference a NULL pointer and terminate abnormally when processing a crafted revocation response.
Impact summary: The NULL pointer dereference happens on a read which leads to a crash and a Denial of Service for the affected client application.
CWE: CWE-476: NULL-pointer dereference
Description: A CMP client revoking a certificate has to tell the server which certificate to revoke, and may do so by supplying a PKCS#10 CSR instead of the certificate itself or its issuer name and serial number. This is 'openssl cmp -cmd rr -csr <file>' on the command line, or OSSL_CMP_exec_RR_ses() with the certificate supplied via OSSL_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 the certificate it revoked in its response, and the client then compares that name against what it sent. Having sent neither an issuer name nor a serial number, it has nothing to compare against, and a server returning a specially crafted name causes the client…
- Record
OESA-2026-4417- CVSS 3.1
- 8.2 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H - Updated
- 2026-11-02
OSVOESA-2026-4418
openssl security update
OpenSSL is a robust, commercial-grade, and full-featured toolkit for the Transport Layer Security (TLS) and Secure Sockets Layer (SSL) protocols.
Security Fix(es):
Issue summary: A certificate with many nameRelativeToCRLIssuer CRL distribution points causes disproportionate heap growth when OpenSSL caches X.509 extensions.
Impact summary: Receiving a crafted certificate from a malicious peer can lead to significant memory pressure and possible Denial of Service in clients or in servers that solicit client certificates.
CWE: CWE-770: Allocation of Resources Without Limits or Throttling
Description: A certificate or a set of certificates that fits under the limit for size of certificates accepted from the peer (~100 KiB) can result in allocation of several hundred MiB of resident memory on the receiving side during a normal TLS handshake. This may be enough to crash the client or server, if multiple concurrent connections lead to similarly large memory allocations.
The fix postpones processing of the CRL distribution points extensions in certificates to the time when the processed value is required for CRL processing. This avoids keeping large memory allocations for a long time when such certificates are received.
FIPS impact: no The affected code is outside the FIPS module boundary.(CVE-2026-35189)
Issue summary: The generic elliptic-curve scalar multiplication used for ECDSA and SM2 signature operations with curves that do not have a dedicated implementation leaks information about the secret nonce through timing.
Impact summary: An attacker able to measure signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key.
CWE: CWE-208: Observable Timing Discrepancy
Description: The generic elliptic-curve scalar multiplication used for curves that do not have a dedicated constant-time implementation pads the secret scalar with non-constant-time BIGNUM operations, so the time taken depends 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 of measurements. The effect is largest for curves whose group order lies on a machine-word boundary, such as brainpoolP384r1.
Applications using ECDSA signing over the Brainpool and other generic prime curves, 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-time implementations and are not affected.
FIPS Impact: no The FIPS modules are not affected: the approved NIST curves used in the FIPS provider have dedicated constant-time implementations and do not use the affected code path.(CVE-2026-54872)
Issue summary: A CMP client that requests certificate revocation on the basis of a PKCS#10 CSR may dereference a NULL pointer and terminate abnormally when processing a crafted revocation response.
Impact summary: The NULL pointer dereference happens on a read which leads to a crash and a Denial of Service for the affected client application.
CWE: CWE-476: NULL-pointer dereference
Description: A CMP client revoking a certificate has to tell the server which certificate to revoke, and may do so by supplying a PKCS#10 CSR instead of the certificate itself or its issuer name and serial number. This is 'openssl cmp -cmd rr -csr <file>' on the command line, or OSSL_CMP_exec_RR_ses() with the certificate supplied via OSSL_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 the certificate it revoked in its response, and the client then compares that name against what it sent. Having sent neither an issuer name nor a serial number, it has nothing to compare against, and a server returning a specially crafted name causes the client…
- Record
OESA-2026-4418- CVSS 3.1
- 8.2 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H - Updated
- 2026-11-02
OSVOESA-2026-4419
openssl security update
OpenSSL is a robust, commercial-grade, and full-featured toolkit for the Transport Layer Security (TLS) and Secure Sockets Layer (SSL) protocols.
Security Fix(es):
Issue summary: A certificate with many nameRelativeToCRLIssuer CRL distribution points causes disproportionate heap growth when OpenSSL caches X.509 extensions.
Impact summary: Receiving a crafted certificate from a malicious peer can lead to significant memory pressure and possible Denial of Service in clients or in servers that solicit client certificates.
CWE: CWE-770: Allocation of Resources Without Limits or Throttling
Description: A certificate or a set of certificates that fits under the limit for size of certificates accepted from the peer (~100 KiB) can result in allocation of several hundred MiB of resident memory on the receiving side during a normal TLS handshake. This may be enough to crash the client or server, if multiple concurrent connections lead to similarly large memory allocations.
The fix postpones processing of the CRL distribution points extensions in certificates to the time when the processed value is required for CRL processing. This avoids keeping large memory allocations for a long time when such certificates are received.
FIPS impact: no The affected code is outside the FIPS module boundary.(CVE-2026-35189)
Issue summary: The OpenSSL QUIC server, when configured to not preform address validation, can be forced to count incoming packets multiple times in its unvalidated credit computation, leading to a violation of the RFC 9000 unvalidated connection amplification limit of 3 times the amount of data received.
Impact summary: A remote attacker able to spoof packets to a server using the OpenSSL QUIC implementation might use the server for an amplification of a DDoS attack.
CWE: CWE-440: Expected Behavior Violation
Description: OpenSSL's QUIC stack, when operating as a server, enforces client address validation (RFC 9000, Section 8), to confirm the peer address is not used for a traffic amplification attack. If this feature is disabled on the server, the QUIC stack limits the amount of server data that can be sent to 3 times the amount of data received from the peer address, until such time as the TLS handshake is completed.
The OpenSSL QUIC server, when operating in non-validation mode, adds the length of the whole datagram received to the unvalidated credit limit when processing each QUIC packet in the datagram. A remote peer may, after establishing a connection with an initial client hello frame, send a subsequent datagram containing multiple QUIC packets, leading the server to account the entire datagram length for each packet in the datagram, resulting in 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: no As the QUIC stack lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.(CVE-2026-35191)
Issue summary: The QUIC stream reassembly algorithm performance deteriorates progressively as packets are arriving out of order. The worst case has a quadratic complexity proportional to the number of stream frames kept in the buffer for the received stream data.
Impact summary: A remote QUIC peer that completes the handshake can create a connection-scoped CPU pressure and potentially a Denial of Service using compliant STREAM frames inside the advertised receive window, with low attacker bandwidth.
CWE: CWE-407: Inefficient Algorithmic Complexity
Description: OpenSSL manages received QUIC stream fragments using a
doubly-linked list. While it optimizes for append operations (at the end of
the list), it falls back to a head-to-tail linear search for any fragment
that does not immediately follow the current tail.
By manipulating the sequence of offsets, an attacker can force the server to perform O(n^2) operations, consuming excessive CPU time for the QUIC process.
FIPS impact: no The…
- Record
OESA-2026-4419- CVSS 3.1
- 8.2 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H - Updated
- 2026-11-02
OSVRHSA-2026:55543
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
- Record
RHSA-2026:55543- CVSS 3.1
- 9.1 Critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N - Updated
- 2026-11-02
OSVRHSA-2026:62562
Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update
- Record
RHSA-2026:62562- CVSS 3.1
- 9.1 Critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N - Updated
- 2026-11-02
OSVRHSA-2026:62790
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
- Record
RHSA-2026:62790- CVSS 3.1
- 9.1 Critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N - Updated
- 2026-11-02
OSVRHSA-2026:67551
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
- Record
RHSA-2026:67551- CVSS 3.1
- 9.1 Critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N - Updated
- 2026-11-02
OSVRHSA-2026:73496
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
- Record
RHSA-2026:73496- CVSS 3.1
- 7.4 High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H - Updated
- 2026-11-02
OSVRHSA-2026:74162
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
- Record
RHSA-2026:74162- CVSS 3.1
- 7.4 High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H - Updated
- 2026-11-02
OSVRHSA-2026:74166
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
- Record
RHSA-2026:74166- CVSS 3.1
- 7.4 High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H - Updated
- 2026-11-02
OSVRHSA-2026:76918
Red Hat Security Advisory: openssl security update
- Record
RHSA-2026:76918- CVSS 3.1
- 7.4 High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H - Updated
- 2026-11-02
OSVRHSA-2026:77396
Red Hat Security Advisory: openssl security update
- Record
RHSA-2026:77396- CVSS 3.1
- 7.4 High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H - Updated
- 2026-11-02
OSVRHSA-2026:80510
Red Hat Security Advisory: compat-openssl10 security update
- Record
RHSA-2026:80510- CVSS 3.1
- 7.4 High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H - Updated
- 2026-11-02
OSVRHSA-2026:80514
Red Hat Security Advisory: compat-openssl11 security update
- Record
RHSA-2026:80514- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSVRLSA-2026:76918
Important: openssl security update
OpenSSL is a toolkit that implements the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols, as well as a full-strength general-purpose cryptography library.
Security Fix(es):
- openssl: compat-openssl: DTLS Retransmits Handshake Messages From a Stale Buffer Offset (CVE-2026-84782)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
- Record
RLSA-2026:76918- CVSS 3.1
- 7.4 High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H - Updated
- 2026-11-02
OSVRLSA-2026:77396
Important: openssl security update
OpenSSL is a toolkit that implements the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols, as well as a full-strength general-purpose cryptography library.
Security Fix(es):
- openssl: compat-openssl: DTLS Retransmits Handshake Messages From a Stale Buffer Offset (CVE-2026-84782)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
- Record
RLSA-2026:77396- CVSS 3.1
- 7.4 High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H - Updated
- 2026-11-02
OSVRLSA-2026:80510
Important: compat-openssl10 security update
The OpenSSL toolkit provides support for secure communications between machines. This version of OpenSSL package contains only the libraries and is provided for compatibility with previous releases and software that does not support compilation with OpenSSL-1.1.
Security Fix(es):
- openssl: compat-openssl: DTLS Retransmits Handshake Messages From a Stale Buffer Offset (CVE-2026-84782)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
- Record
RLSA-2026:80510- CVSS 3.1
- 7.4 High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H - Updated
- 2026-11-02
OSVRLSA-2026:80514
Moderate: compat-openssl11 security update
The OpenSSL toolkit provides support for secure communications between machines. This version of OpenSSL package contains only the libraries from the 1.1.1 version and is provided for compatibility with previous releases.
Security Fix(es):
-
openssl: heap buffer overflow in CMS key unwrapping (CVE-2026-63072)
-
openssl: compat-openssl: DTLS Retransmits Handshake Messages From a Stale Buffer Offset (CVE-2026-84782)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
- Record
RLSA-2026:80514- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSVUBUNTU-CVE-2026-84782
Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly. Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region. CWE: CWE-125: Out-of-bounds Read Description: DTLS handshake messages can be written out in multiple fragments, and a write can suspend mid-message (returning WANT_WRITE) if the underlying transport temporarily cannot accept more data. While such a write is suspended, the DTLS retransmission timer may independently fire and ask the retransmission logic to resend an earlier, already-acknowledged-as-sent message from its retransmit queue. The retransmission logic reused the same internal buffer and position tracking as the message that was still being written, without resetting the position back to the start of the message being retransmitted. As a result the retransmission was read starting from wherever the suspended write had left off, producing a mislabelled message whose body was leftover bytes from the other, larger message still in flight - content that was never meant to be sent at that point, and which could run past the end of the allocated buffer. Separately, even when the retransmission is positioned correctly, allowing it to run to completion while another write is suspended overwrites the same shared bookkeeping that the suspended write depends on to resume. When the application later resumes the suspended write (via a subsequent SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() call), it finds that bookkeeping in a state inconsistent with the message and aborts the process in a debugging build. The fix resets the retransmission's read position to the start of the message before resending, and skips retransmission entirely whenever a handshake write is still suspended, deferring to the next call that resumes it instead. FIPS impact: no The affected code is outside the FIPS module boundary.
- Record
UBUNTU-CVE-2026-84782- CVSS 3.1
- 8.2 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H - Updated
- 2026-11-02
OSVALSA-2026:76918 No score
Important: openssl security update
OpenSSL is a toolkit that implements the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols, as well as a full-strength general-purpose cryptography library.
Security Fix(es):
- openssl: compat-openssl: DTLS Retransmits Handshake Messages From a Stale Buffer Offset (CVE-2026-84782)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
- Record
ALSA-2026:76918- Updated
- 2026-11-02
OSVALSA-2026:77396 No score
Important: openssl security update
OpenSSL is a toolkit that implements the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols, as well as a full-strength general-purpose cryptography library.
Security Fix(es):
- openssl: compat-openssl: DTLS Retransmits Handshake Messages From a Stale Buffer Offset (CVE-2026-84782)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
- Record
ALSA-2026:77396- Updated
- 2026-11-02
OSVALSA-2026:80510 No score
Important: compat-openssl10 security update
The OpenSSL toolkit provides support for secure communications between machines. This version of OpenSSL package contains only the libraries and is provided for compatibility with previous releases and software that does not support compilation with OpenSSL-1.1.
Security Fix(es):
- openssl: compat-openssl: DTLS Retransmits Handshake Messages From a Stale Buffer Offset (CVE-2026-84782)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
- Record
ALSA-2026:80510- Updated
- 2026-11-02
OSVALSA-2026:80514 No score
Moderate: compat-openssl11 security update
The OpenSSL toolkit provides support for secure communications between machines. This version of OpenSSL package contains only the libraries from the 1.1.1 version and is provided for compatibility with previous releases.
Security Fix(es):
- openssl: heap buffer overflow in CMS key unwrapping (CVE-2026-63072)
- openssl: compat-openssl: DTLS Retransmits Handshake Messages From a Stale Buffer Offset (CVE-2026-84782)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
- Record
ALSA-2026:80514- Updated
- 2026-11-02
OSVALSA-2026:85968 No score
Important: openssl security update
OpenSSL is a toolkit that implements the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols, as well as a full-strength general-purpose cryptography library.
Security Fix(es):
- openssl: heap buffer overflow in CMS key unwrapping (CVE-2026-63072)
- openssl: compat-openssl: DTLS Retransmits Handshake Messages From a Stale Buffer Offset (CVE-2026-84782)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
- Record
ALSA-2026:85968- Updated
- 2026-11-02
OSVAZL-105363 No score
CVE-2026-84782 affecting package openssl-fips-provider 3.1.2-2
Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly.
Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region.
CWE: CWE-125: Out-of-bounds Read
Description: DTLS handshake messages can be written out in multiple fragments, and a write can suspend mid-message (returning WANT_WRITE) if the underlying transport temporarily cannot accept more data. While such a write is suspended, the DTLS retransmission timer may independently fire and ask the retransmission logic to resend an earlier, already-acknowledged-as-sent message from its retransmit queue.
The retransmission logic reused the same internal buffer and position tracking as the message that was still being written, without resetting the position back to the start of the message being retransmitted. As a result the retransmission was read starting from wherever the suspended write had left off, producing a mislabelled message whose body was leftover bytes from the other, larger message still in flight - content that was never meant to be sent at that point, and which could run past the end of the allocated buffer.
Separately, even when the retransmission is positioned correctly, allowing it to run to completion while another write is suspended overwrites the same shared bookkeeping that the suspended write depends on to resume. When the application later resumes the suspended write (via a subsequent SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() call), it finds that bookkeeping in a state inconsistent with the message and aborts the process in a debugging build.
The fix resets the retransmission's read position to the start of the message before resending, and skips retransmission entirely whenever a handshake write is still suspended, deferring to the next call that resumes it instead.
FIPS impact: no The affected code is outside the FIPS module boundary.
- Record
AZL-105363- Updated
- 2026-11-05
OSVAZL-105444 No score
CVE-2026-84782 affecting package cloud-hypervisor 52.0.152-1
Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly.
Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region.
CWE: CWE-125: Out-of-bounds Read
Description: DTLS handshake messages can be written out in multiple fragments, and a write can suspend mid-message (returning WANT_WRITE) if the underlying transport temporarily cannot accept more data. While such a write is suspended, the DTLS retransmission timer may independently fire and ask the retransmission logic to resend an earlier, already-acknowledged-as-sent message from its retransmit queue.
The retransmission logic reused the same internal buffer and position tracking as the message that was still being written, without resetting the position back to the start of the message being retransmitted. As a result the retransmission was read starting from wherever the suspended write had left off, producing a mislabelled message whose body was leftover bytes from the other, larger message still in flight - content that was never meant to be sent at that point, and which could run past the end of the allocated buffer.
Separately, even when the retransmission is positioned correctly, allowing it to run to completion while another write is suspended overwrites the same shared bookkeeping that the suspended write depends on to resume. When the application later resumes the suspended write (via a subsequent SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() call), it finds that bookkeeping in a state inconsistent with the message and aborts the process in a debugging build.
The fix resets the retransmission's read position to the start of the message before resending, and skips retransmission entirely whenever a handshake write is still suspended, deferring to the next call that resumes it instead.
FIPS impact: no The affected code is outside the FIPS module boundary.
- Record
AZL-105444- Updated
- 2026-11-02
OSVAZL-105483 No score
CVE-2026-84782 affecting package edk2 for versions less than 20240524git3e722403cd16-21
Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly.
Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region.
CWE: CWE-125: Out-of-bounds Read
Description: DTLS handshake messages can be written out in multiple fragments, and a write can suspend mid-message (returning WANT_WRITE) if the underlying transport temporarily cannot accept more data. While such a write is suspended, the DTLS retransmission timer may independently fire and ask the retransmission logic to resend an earlier, already-acknowledged-as-sent message from its retransmit queue.
The retransmission logic reused the same internal buffer and position tracking as the message that was still being written, without resetting the position back to the start of the message being retransmitted. As a result the retransmission was read starting from wherever the suspended write had left off, producing a mislabelled message whose body was leftover bytes from the other, larger message still in flight - content that was never meant to be sent at that point, and which could run past the end of the allocated buffer.
Separately, even when the retransmission is positioned correctly, allowing it to run to completion while another write is suspended overwrites the same shared bookkeeping that the suspended write depends on to resume. When the application later resumes the suspended write (via a subsequent SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() call), it finds that bookkeeping in a state inconsistent with the message and aborts the process in a debugging build.
The fix resets the retransmission's read position to the start of the message before resending, and skips retransmission entirely whenever a handshake write is still suspended, deferring to the next call that resumes it instead.
FIPS impact: no The affected code is outside the FIPS module boundary.
- Record
AZL-105483- Updated
- 2026-11-05
OSVAZL-105501 No score
CVE-2026-84782 affecting package kata-containers 4.1.0.kata0-1
Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly.
Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region.
CWE: CWE-125: Out-of-bounds Read
Description: DTLS handshake messages can be written out in multiple fragments, and a write can suspend mid-message (returning WANT_WRITE) if the underlying transport temporarily cannot accept more data. While such a write is suspended, the DTLS retransmission timer may independently fire and ask the retransmission logic to resend an earlier, already-acknowledged-as-sent message from its retransmit queue.
The retransmission logic reused the same internal buffer and position tracking as the message that was still being written, without resetting the position back to the start of the message being retransmitted. As a result the retransmission was read starting from wherever the suspended write had left off, producing a mislabelled message whose body was leftover bytes from the other, larger message still in flight - content that was never meant to be sent at that point, and which could run past the end of the allocated buffer.
Separately, even when the retransmission is positioned correctly, allowing it to run to completion while another write is suspended overwrites the same shared bookkeeping that the suspended write depends on to resume. When the application later resumes the suspended write (via a subsequent SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() call), it finds that bookkeeping in a state inconsistent with the message and aborts the process in a debugging build.
The fix resets the retransmission's read position to the start of the message before resending, and skips retransmission entirely whenever a handshake write is still suspended, deferring to the next call that resumes it instead.
FIPS impact: no The affected code is outside the FIPS module boundary.
- Record
AZL-105501- Updated
- 2026-11-02
OSVAZL-105567 No score
CVE-2026-84782 affecting package openssl for versions less than 3.3.7-7
Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly.
Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region.
CWE: CWE-125: Out-of-bounds Read
Description: DTLS handshake messages can be written out in multiple fragments, and a write can suspend mid-message (returning WANT_WRITE) if the underlying transport temporarily cannot accept more data. While such a write is suspended, the DTLS retransmission timer may independently fire and ask the retransmission logic to resend an earlier, already-acknowledged-as-sent message from its retransmit queue.
The retransmission logic reused the same internal buffer and position tracking as the message that was still being written, without resetting the position back to the start of the message being retransmitted. As a result the retransmission was read starting from wherever the suspended write had left off, producing a mislabelled message whose body was leftover bytes from the other, larger message still in flight - content that was never meant to be sent at that point, and which could run past the end of the allocated buffer.
Separately, even when the retransmission is positioned correctly, allowing it to run to completion while another write is suspended overwrites the same shared bookkeeping that the suspended write depends on to resume. When the application later resumes the suspended write (via a subsequent SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() call), it finds that bookkeeping in a state inconsistent with the message and aborts the process in a debugging build.
The fix resets the retransmission's read position to the start of the message before resending, and skips retransmission entirely whenever a handshake write is still suspended, deferring to the next call that resumes it instead.
FIPS impact: no The affected code is outside the FIPS module boundary.
- Record
AZL-105567- Updated
- 2026-11-05
OSVAZL-105615 No score
CVE-2026-84782 affecting package openvmm 0.1.0-1
Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly.
Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region.
CWE: CWE-125: Out-of-bounds Read
Description: DTLS handshake messages can be written out in multiple fragments, and a write can suspend mid-message (returning WANT_WRITE) if the underlying transport temporarily cannot accept more data. While such a write is suspended, the DTLS retransmission timer may independently fire and ask the retransmission logic to resend an earlier, already-acknowledged-as-sent message from its retransmit queue.
The retransmission logic reused the same internal buffer and position tracking as the message that was still being written, without resetting the position back to the start of the message being retransmitted. As a result the retransmission was read starting from wherever the suspended write had left off, producing a mislabelled message whose body was leftover bytes from the other, larger message still in flight - content that was never meant to be sent at that point, and which could run past the end of the allocated buffer.
Separately, even when the retransmission is positioned correctly, allowing it to run to completion while another write is suspended overwrites the same shared bookkeeping that the suspended write depends on to resume. When the application later resumes the suspended write (via a subsequent SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() call), it finds that bookkeeping in a state inconsistent with the message and aborts the process in a debugging build.
The fix resets the retransmission's read position to the start of the message before resending, and skips retransmission entirely whenever a handshake write is still suspended, deferring to the next call that resumes it instead.
FIPS impact: no The affected code is outside the FIPS module boundary.
- Record
AZL-105615- Updated
- 2026-11-02
OSVAZL-105696 No score
CVE-2026-84782 affecting package qemu 10.1.0-1
Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly.
Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region.
CWE: CWE-125: Out-of-bounds Read
Description: DTLS handshake messages can be written out in multiple fragments, and a write can suspend mid-message (returning WANT_WRITE) if the underlying transport temporarily cannot accept more data. While such a write is suspended, the DTLS retransmission timer may independently fire and ask the retransmission logic to resend an earlier, already-acknowledged-as-sent message from its retransmit queue.
The retransmission logic reused the same internal buffer and position tracking as the message that was still being written, without resetting the position back to the start of the message being retransmitted. As a result the retransmission was read starting from wherever the suspended write had left off, producing a mislabelled message whose body was leftover bytes from the other, larger message still in flight - content that was never meant to be sent at that point, and which could run past the end of the allocated buffer.
Separately, even when the retransmission is positioned correctly, allowing it to run to completion while another write is suspended overwrites the same shared bookkeeping that the suspended write depends on to resume. When the application later resumes the suspended write (via a subsequent SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() call), it finds that bookkeeping in a state inconsistent with the message and aborts the process in a debugging build.
The fix resets the retransmission's read position to the start of the message before resending, and skips retransmission entirely whenever a handshake write is still suspended, deferring to the next call that resumes it instead.
FIPS impact: no The affected code is outside the FIPS module boundary.
- Record
AZL-105696- Updated
- 2026-11-02
OSVAZL-105822 No score
CVE-2026-84782 affecting package rust 1.75.0-31
Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly.
Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region.
CWE: CWE-125: Out-of-bounds Read
Description: DTLS handshake messages can be written out in multiple fragments, and a write can suspend mid-message (returning WANT_WRITE) if the underlying transport temporarily cannot accept more data. While such a write is suspended, the DTLS retransmission timer may independently fire and ask the retransmission logic to resend an earlier, already-acknowledged-as-sent message from its retransmit queue.
The retransmission logic reused the same internal buffer and position tracking as the message that was still being written, without resetting the position back to the start of the message being retransmitted. As a result the retransmission was read starting from wherever the suspended write had left off, producing a mislabelled message whose body was leftover bytes from the other, larger message still in flight - content that was never meant to be sent at that point, and which could run past the end of the allocated buffer.
Separately, even when the retransmission is positioned correctly, allowing it to run to completion while another write is suspended overwrites the same shared bookkeeping that the suspended write depends on to resume. When the application later resumes the suspended write (via a subsequent SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() call), it finds that bookkeeping in a state inconsistent with the message and aborts the process in a debugging build.
The fix resets the retransmission's read position to the start of the message before resending, and skips retransmission entirely whenever a handshake write is still suspended, deferring to the next call that resumes it instead.
FIPS impact: no The affected code is outside the FIPS module boundary.
- Record
AZL-105822- Updated
- 2026-11-02
OSVAZL-105864 No score
CVE-2026-84782 affecting package rust 1.96.1-2
Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly.
Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region.
CWE: CWE-125: Out-of-bounds Read
Description: DTLS handshake messages can be written out in multiple fragments, and a write can suspend mid-message (returning WANT_WRITE) if the underlying transport temporarily cannot accept more data. While such a write is suspended, the DTLS retransmission timer may independently fire and ask the retransmission logic to resend an earlier, already-acknowledged-as-sent message from its retransmit queue.
The retransmission logic reused the same internal buffer and position tracking as the message that was still being written, without resetting the position back to the start of the message being retransmitted. As a result the retransmission was read starting from wherever the suspended write had left off, producing a mislabelled message whose body was leftover bytes from the other, larger message still in flight - content that was never meant to be sent at that point, and which could run past the end of the allocated buffer.
Separately, even when the retransmission is positioned correctly, allowing it to run to completion while another write is suspended overwrites the same shared bookkeeping that the suspended write depends on to resume. When the application later resumes the suspended write (via a subsequent SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() call), it finds that bookkeeping in a state inconsistent with the message and aborts the process in a debugging build.
The fix resets the retransmission's read position to the start of the message before resending, and skips retransmission entirely whenever a handshake write is still suspended, deferring to the next call that resumes it instead.
FIPS impact: no The affected code is outside the FIPS module boundary.
- Record
AZL-105864- Updated
- 2026-11-02
OSVCLSA-2026-1790933161 No score
openssl: Fix of 2 CVEs
- CVE-2026-84782: reset s->init_off to 0 in dtls1_retransmit_message() and skip retransmission in dtls1_handle_timeout() while a handshake write is suspended, preventing a DTLS retransmit from being sent from a stale buffer offset
- CVE-2026-35189: defer building the full nameRelativeToCRLIssuer distribution point name out of certificate parsing into CRL matching, so a certificate with many relative CRL distribution points no longer duplicates the issuer name per entry at parse time
- Record
CLSA-2026-1790933161- Updated
- 2026-11-02
OSVCLSA-2026-1790933443 No score
openssl: Fix of 2 CVEs
- CVE-2026-84782: dtls: reset init_off before retransmitting a message, and skip retransmission while a handshake write is still suspended
- CVE-2026-35189: defer computation of relative CRL distribution point names until CRL processing actually needs them
- Record
CLSA-2026-1790933443- Updated
- 2026-11-02
OSVCLSA-2026-1790933563 No score
openssl: Fix of 2 CVEs
- CVE-2026-84782: reset s->init_off to 0 in dtls1_retransmit_message() and skip retransmission in dtls1_handle_timeout() while a handshake write is still parked mid-flight, so a DTLS retransmit is no longer sent from the stale offset left behind by an unrelated suspended write
- CVE-2026-35189: defer building the full nameRelativeToCRLIssuer distribution point name out of setup_dp() at certificate parse time into the CRL matching code, so a certificate carrying many relative CRL distribution points no longer duplicates the issuer name once per entry on every parse
- Record
CLSA-2026-1790933563- Updated
- 2026-11-02
OSVCLSA-2026-1791192990 No score
openssl11: Fix of 2 CVEs
- CVE-2026-84782: reset init_off before a DTLS retransmission and skip it while a handshake write is suspended, avoiding a heap over-read
- CVE-2026-35189: build relative CRL distribution point names only during CRL matching, avoiding unbounded heap growth when caching extensions
- Record
CLSA-2026-1791192990- Updated
- 2026-11-02
OSVCLSA-2026-1791193015 No score
openssl11: Fix of 2 CVEs
- CVE-2026-84782: reset init_off before a DTLS retransmission and skip it while a handshake write is suspended, avoiding a heap over-read
- CVE-2026-35189: build relative CRL distribution point names only during CRL matching, avoiding unbounded heap growth when caching extensions
- Record
CLSA-2026-1791193015- Updated
- 2026-11-02
OSVCLSA-2026-1791193238 No score
openssl11: Fix of 2 CVEs
- CVE-2026-84782: reset init_off before a DTLS retransmission and skip it while a handshake write is suspended, avoiding a heap over-read
- CVE-2026-35189: build relative CRL distribution point names only during CRL matching, avoiding unbounded heap growth when caching extensions
- Record
CLSA-2026-1791193238- Updated
- 2026-11-02
OSVCLSA-2026-1791199071 No score
openssl: Fix of 2 CVEs
- CVE-2026-84782: reset s->init_off to 0 in dtls1_retransmit_message() so a DTLS retransmission is read from the start of the queued message instead of the offset left by a write suspended on WANT_WRITE, and skip retransmission in dtls1_handle_timeout() while such a write is still parked
- CVE-2026-35189: defer building the full name of a nameRelativeToCRLIssuer CRL distribution point out of setup_dp() and into crl_crldp_check(), so a certificate with many relative distribution points no longer caches one copy of the issuer name per entry
- Record
CLSA-2026-1791199071- Updated
- 2026-11-02
OSVCLSA-2026-1791200035 No score
openssl: Fix of 2 CVEs
- CVE-2026-84782: reset s->init_off to 0 in dtls1_retransmit_message() so a DTLS retransmission is read from the start of the queued message instead of the offset left by a write suspended on WANT_WRITE, and skip retransmission in dtls1_handle_timeout() while such a write is still parked
- CVE-2026-35189: defer building the full name of a nameRelativeToCRLIssuer CRL distribution point out of setup_dp() and into crl_crldp_check(), so a certificate with many relative distribution points no longer caches one copy of the issuer name per entry
- Record
CLSA-2026-1791200035- Updated
- 2026-11-02
OSVCLSA-2026-1791200195 No score
openssl: Fix of 2 CVEs
- CVE-2026-84782: reset s->init_off to 0 in dtls1_retransmit_message() so a DTLS retransmission is read from the start of the queued message instead of the offset left by a write suspended on WANT_WRITE, and skip retransmission in dtls1_handle_timeout() while such a write is still parked
- CVE-2026-35189: defer building the full name of a nameRelativeToCRLIssuer CRL distribution point out of setup_dp() and into crl_crldp_check(), so a certificate with many relative distribution points no longer caches one copy of the issuer name per entry
- Record
CLSA-2026-1791200195- Updated
- 2026-11-02
OSVCLSA-2026-1791229632 No score
Fix CVE(s): CVE-2026-35189, CVE-2026-84782
- SECURITY UPDATE: excessive memory use with relative CRL distribution
point names
- debian/patches/CVE-2026-35189.patch: build the full name of a nameRelativeToCRLIssuer distribution point only while matching a CRL instead of for every parsed certificate in crypto/x509v3/v3_crld.c, crypto/x509v3/v3_purp.c and crypto/x509/x509_vfy.c
- CVE-2026-35189
- SECURITY UPDATE: DTLS retransmission corrupts a suspended write
- debian/patches/CVE-2026-84782.patch: reset init_off before retransmitting a message in ssl/statem/statem_dtls.c and skip the retransmission while a write is still parked in ssl/d1_lib.c
- CVE-2026-84782
- Record
CLSA-2026-1791229632- Updated
- 2026-11-02
OSVCLSA-2026-1791229846 No score
Fix CVE(s): CVE-2026-35189, CVE-2026-84782
- SECURITY UPDATE: excessive memory use with relative CRL distribution
point names
- debian/patches/CVE-2026-35189.patch: build the full name of a nameRelativeToCRLIssuer distribution point only while matching a CRL instead of for every parsed certificate in crypto/x509v3/v3_purp.c and crypto/x509/x509_vfy.c
- CVE-2026-35189
- SECURITY UPDATE: DTLS retransmission corrupts a suspended write
- debian/patches/CVE-2026-84782.patch: reset init_off before retransmitting a message in ssl/d1_both.c and skip the retransmission while a handshake write is unfinished in ssl/d1_lib.c
- CVE-2026-84782
- Record
CLSA-2026-1791229846- Updated
- 2026-11-02
OSVCLSA-2026-1791490295 No score
Fix CVE(s): CVE-2026-35189, CVE-2026-84782
- SECURITY UPDATE: excessive memory use with relative CRL distribution
point names
- debian/patches/CVE-2026-35189.patch: build the full name of a nameRelativeToCRLIssuer distribution point only while matching a CRL instead of for every parsed certificate in crypto/x509v3/v3_crld.c, crypto/x509v3/v3_purp.c and crypto/x509/x509_vfy.c
- CVE-2026-35189
- SECURITY UPDATE: DTLS retransmission corrupts a suspended write
- debian/patches/CVE-2026-84782.patch: reset init_off before retransmitting a message in ssl/statem/statem_dtls.c and skip the retransmission while a write is still parked in ssl/d1_lib.c
- CVE-2026-84782
- Record
CLSA-2026-1791490295- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
opensslAlpine:v3.21 |
1.0.2 up to 3.3.7-r2 | 3.3.7-r2 |
opensslAlmaLinux:10 |
before 1:3.5.8-2.el10_2.alma.1 | 1:3.5.8-2.el10_2.alma.1 |
openssl-develAlmaLinux:10 |
before 1:3.5.8-2.el10_2.alma.1 | 1:3.5.8-2.el10_2.alma.1 |
openssl-libsAlmaLinux:10 |
before 1:3.5.8-2.el10_2.alma.1 | 1:3.5.8-2.el10_2.alma.1 |
openssl-perlAlmaLinux:10 |
before 1:3.5.8-2.el10_2.alma.1 | 1:3.5.8-2.el10_2.alma.1 |
opensslAlmaLinux:9 |
before 1:3.5.8-2.el9_8 | 1:3.5.8-2.el9_8 |
openssl-develAlmaLinux:9 |
before 1:3.5.8-2.el9_8 | 1:3.5.8-2.el9_8 |
openssl-libsAlmaLinux:9 |
before 1:3.5.8-2.el9_8 | 1:3.5.8-2.el9_8 |
openssl-perlAlmaLinux:9 |
before 1:3.5.8-2.el9_8 | 1:3.5.8-2.el9_8 |
compat-openssl10AlmaLinux:8 |
before 1:1.0.2o-4.el8_10.4 | 1:1.0.2o-4.el8_10.4 |
Show 233 moreShow less
| Package | Affected | Fixed |
|---|---|---|
compat-openssl11AlmaLinux:9 From an advisory covering 2 CVEs |
before 1:1.1.1k-5.el9_8.6 | 1:1.1.1k-5.el9_8.6 |
opensslAlmaLinux:8 From an advisory covering 2 CVEs |
before 1:1.1.1k-18.el8_6 | 1:1.1.1k-18.el8_6 |
openssl-develAlmaLinux:8 From an advisory covering 2 CVEs |
before 1:1.1.1k-18.el8_6 | 1:1.1.1k-18.el8_6 |
openssl-libsAlmaLinux:8 From an advisory covering 2 CVEs |
before 1:1.1.1k-18.el8_6 | 1:1.1.1k-18.el8_6 |
openssl-perlAlmaLinux:8 From an advisory covering 2 CVEs |
before 1:1.1.1k-18.el8_6 | 1:1.1.1k-18.el8_6 |
openssl-fips-providerAzure Linux:3 |
through 3.1.2-2 | None known |
cloud-hypervisorAzure Linux:3 |
through 52.0.152-1 | None known |
edk2Azure Linux:3 |
before 20240524git3e722403cd16-21 | 20240524git3e722403cd16-21 |
kata-containersAzure Linux:3 |
through 4.1.0.kata0-1 | None known |
opensslAzure Linux:3 |
before 3.3.7-7 | 3.3.7-7 |
openvmmAzure Linux:3 |
through 0.1.0-1 | None known |
qemuAzure Linux:3 |
through 10.1.0-1 | None known |
rustAzure Linux:3 |
through 1.75.0-31 | None known |
rustAzure Linux:3 |
1.85.0 to 1.96.1-2 | None known |
opensslAlpaquita:23 |
3.0.8-r4 up to 3.0.22-r1 | 3.0.22-r1 |
opensslAlpaquita:25 |
3.5.0-r0 up to 3.5.9-r0 | 3.5.9-r0 |
opensslAlpaquita:stream |
3.5.0-r0 up to 3.5.9-r0 | 3.5.9-r0 |
opensslBellSoft Hardened Containers:23 |
3.0.8-r4 up to 3.0.22-r1 | 3.0.22-r1 |
opensslBellSoft Hardened Containers:25 |
3.5.0-r0 up to 3.5.9-r0 | 3.5.9-r0 |
opensslBellSoft Hardened Containers:stream |
3.5.0-r0 up to 3.5.9-r0 | 3.5.9-r0 |
opensslTuxCare:CentOS:8.5 From an advisory covering 2 CVEs |
before 1:1.1.1k-5.el8_5.tuxcare.els22 | 1:1.1.1k-5.el8_5.tuxcare.els22 |
openssl-develTuxCare:CentOS:8.5 From an advisory covering 2 CVEs |
before 1:1.1.1k-5.el8_5.tuxcare.els22 | 1:1.1.1k-5.el8_5.tuxcare.els22 |
openssl-libsTuxCare:CentOS:8.5 From an advisory covering 2 CVEs |
before 1:1.1.1k-5.el8_5.tuxcare.els22 | 1:1.1.1k-5.el8_5.tuxcare.els22 |
openssl-perlTuxCare:CentOS:8.5 From an advisory covering 2 CVEs |
before 1:1.1.1k-5.el8_5.tuxcare.els22 | 1:1.1.1k-5.el8_5.tuxcare.els22 |
openssl-staticTuxCare:CentOS:8.5 From an advisory covering 2 CVEs |
before 1:1.1.1k-5.el8_5.tuxcare.els22 | 1:1.1.1k-5.el8_5.tuxcare.els22 |
opensslTuxCare:CentOS:8.4 From an advisory covering 2 CVEs |
before 1:1.1.1g-15.el8_4.tuxcare.els23 | 1:1.1.1g-15.el8_4.tuxcare.els23 |
openssl-develTuxCare:CentOS:8.4 From an advisory covering 2 CVEs |
before 1:1.1.1g-15.el8_4.tuxcare.els23 | 1:1.1.1g-15.el8_4.tuxcare.els23 |
openssl-libsTuxCare:CentOS:8.4 From an advisory covering 2 CVEs |
before 1:1.1.1g-15.el8_4.tuxcare.els23 | 1:1.1.1g-15.el8_4.tuxcare.els23 |
openssl-perlTuxCare:CentOS:8.4 From an advisory covering 2 CVEs |
before 1:1.1.1g-15.el8_4.tuxcare.els23 | 1:1.1.1g-15.el8_4.tuxcare.els23 |
openssl-staticTuxCare:CentOS:8.4 From an advisory covering 2 CVEs |
before 1:1.1.1g-15.el8_4.tuxcare.els23 | 1:1.1.1g-15.el8_4.tuxcare.els23 |
opensslTuxCare:CentOS-Stream:8 From an advisory covering 2 CVEs |
before 1:1.1.1k-12.el8.tuxcare.els12 | 1:1.1.1k-12.el8.tuxcare.els12 |
openssl-develTuxCare:CentOS-Stream:8 From an advisory covering 2 CVEs |
before 1:1.1.1k-12.el8.tuxcare.els12 | 1:1.1.1k-12.el8.tuxcare.els12 |
openssl-libsTuxCare:CentOS-Stream:8 From an advisory covering 2 CVEs |
before 1:1.1.1k-12.el8.tuxcare.els12 | 1:1.1.1k-12.el8.tuxcare.els12 |
openssl-perlTuxCare:CentOS-Stream:8 From an advisory covering 2 CVEs |
before 1:1.1.1k-12.el8.tuxcare.els12 | 1:1.1.1k-12.el8.tuxcare.els12 |
openssl-staticTuxCare:CentOS-Stream:8 From an advisory covering 2 CVEs |
before 1:1.1.1k-12.el8.tuxcare.els12 | 1:1.1.1k-12.el8.tuxcare.els12 |
openssl11TuxCare:RHEL:7 From an advisory covering 2 CVEs |
before 1:1.1.1k-7.el7.tuxcare.els6 | 1:1.1.1k-7.el7.tuxcare.els6 |
openssl11-develTuxCare:RHEL:7 From an advisory covering 2 CVEs |
before 1:1.1.1k-7.el7.tuxcare.els6 | 1:1.1.1k-7.el7.tuxcare.els6 |
openssl11-libsTuxCare:RHEL:7 From an advisory covering 2 CVEs |
before 1:1.1.1k-7.el7.tuxcare.els6 | 1:1.1.1k-7.el7.tuxcare.els6 |
openssl11-staticTuxCare:RHEL:7 From an advisory covering 2 CVEs |
before 1:1.1.1k-7.el7.tuxcare.els6 | 1:1.1.1k-7.el7.tuxcare.els6 |
openssl11TuxCare:CentOS:7 From an advisory covering 2 CVEs |
before 1:1.1.1k-7.el7.tuxcare.els6 | 1:1.1.1k-7.el7.tuxcare.els6 |
openssl11-develTuxCare:CentOS:7 From an advisory covering 2 CVEs |
before 1:1.1.1k-7.el7.tuxcare.els6 | 1:1.1.1k-7.el7.tuxcare.els6 |
openssl11-libsTuxCare:CentOS:7 From an advisory covering 2 CVEs |
before 1:1.1.1k-7.el7.tuxcare.els6 | 1:1.1.1k-7.el7.tuxcare.els6 |
openssl11-staticTuxCare:CentOS:7 From an advisory covering 2 CVEs |
before 1:1.1.1k-7.el7.tuxcare.els6 | 1:1.1.1k-7.el7.tuxcare.els6 |
openssl11TuxCare:OracleLinux:7 From an advisory covering 2 CVEs |
before 1:1.1.1k-7.el7.tuxcare.els6 | 1:1.1.1k-7.el7.tuxcare.els6 |
openssl11-develTuxCare:OracleLinux:7 From an advisory covering 2 CVEs |
before 1:1.1.1k-7.el7.tuxcare.els6 | 1:1.1.1k-7.el7.tuxcare.els6 |
openssl11-libsTuxCare:OracleLinux:7 From an advisory covering 2 CVEs |
before 1:1.1.1k-7.el7.tuxcare.els6 | 1:1.1.1k-7.el7.tuxcare.els6 |
openssl11-staticTuxCare:OracleLinux:7 From an advisory covering 2 CVEs |
before 1:1.1.1k-7.el7.tuxcare.els6 | 1:1.1.1k-7.el7.tuxcare.els6 |
opensslTuxCare:CentOS:7 From an advisory covering 2 CVEs |
before 1:1.0.2k-26.0.1.el7_9.tuxcare.els5 | 1:1.0.2k-26.0.1.el7_9.tuxcare.els5 |
openssl-develTuxCare:CentOS:7 From an advisory covering 2 CVEs |
before 1:1.0.2k-26.0.1.el7_9.tuxcare.els5 | 1:1.0.2k-26.0.1.el7_9.tuxcare.els5 |
openssl-libsTuxCare:CentOS:7 From an advisory covering 2 CVEs |
before 1:1.0.2k-26.0.1.el7_9.tuxcare.els5 | 1:1.0.2k-26.0.1.el7_9.tuxcare.els5 |
openssl-perlTuxCare:CentOS:7 From an advisory covering 2 CVEs |
before 1:1.0.2k-26.0.1.el7_9.tuxcare.els5 | 1:1.0.2k-26.0.1.el7_9.tuxcare.els5 |
openssl-staticTuxCare:CentOS:7 From an advisory covering 2 CVEs |
before 1:1.0.2k-26.0.1.el7_9.tuxcare.els5 | 1:1.0.2k-26.0.1.el7_9.tuxcare.els5 |
opensslTuxCare:OracleLinux:7 From an advisory covering 2 CVEs |
before 1:1.0.2k-26.0.1.el7_9.tuxcare.els5 | 1:1.0.2k-26.0.1.el7_9.tuxcare.els5 |
openssl-develTuxCare:OracleLinux:7 From an advisory covering 2 CVEs |
before 1:1.0.2k-26.0.1.el7_9.tuxcare.els5 | 1:1.0.2k-26.0.1.el7_9.tuxcare.els5 |
openssl-libsTuxCare:OracleLinux:7 From an advisory covering 2 CVEs |
before 1:1.0.2k-26.0.1.el7_9.tuxcare.els5 | 1:1.0.2k-26.0.1.el7_9.tuxcare.els5 |
openssl-perlTuxCare:OracleLinux:7 From an advisory covering 2 CVEs |
before 1:1.0.2k-26.0.1.el7_9.tuxcare.els5 | 1:1.0.2k-26.0.1.el7_9.tuxcare.els5 |
openssl-staticTuxCare:OracleLinux:7 From an advisory covering 2 CVEs |
before 1:1.0.2k-26.0.1.el7_9.tuxcare.els5 | 1:1.0.2k-26.0.1.el7_9.tuxcare.els5 |
opensslTuxCare:RHEL:7 From an advisory covering 2 CVEs |
before 1:1.0.2k-26.0.1.el7_9.tuxcare.els5 | 1:1.0.2k-26.0.1.el7_9.tuxcare.els5 |
openssl-develTuxCare:RHEL:7 From an advisory covering 2 CVEs |
before 1:1.0.2k-26.0.1.el7_9.tuxcare.els5 | 1:1.0.2k-26.0.1.el7_9.tuxcare.els5 |
openssl-libsTuxCare:RHEL:7 From an advisory covering 2 CVEs |
before 1:1.0.2k-26.0.1.el7_9.tuxcare.els5 | 1:1.0.2k-26.0.1.el7_9.tuxcare.els5 |
openssl-perlTuxCare:RHEL:7 From an advisory covering 2 CVEs |
before 1:1.0.2k-26.0.1.el7_9.tuxcare.els5 | 1:1.0.2k-26.0.1.el7_9.tuxcare.els5 |
openssl-staticTuxCare:RHEL:7 From an advisory covering 2 CVEs |
before 1:1.0.2k-26.0.1.el7_9.tuxcare.els5 | 1:1.0.2k-26.0.1.el7_9.tuxcare.els5 |
libssl-devTuxCare:Ubuntu:18.04 From an advisory covering 2 CVEs |
before 1.1.1-1ubuntu2.1~18.04.23+tuxcare.els12 | 1.1.1-1ubuntu2.1~18.04.23+tuxcare.els12 |
libssl-docTuxCare:Ubuntu:18.04 From an advisory covering 2 CVEs |
before 1.1.1-1ubuntu2.1~18.04.23+tuxcare.els12 | 1.1.1-1ubuntu2.1~18.04.23+tuxcare.els12 |
libssl1.1TuxCare:Ubuntu:18.04 From an advisory covering 2 CVEs |
before 1.1.1-1ubuntu2.1~18.04.23+tuxcare.els12 | 1.1.1-1ubuntu2.1~18.04.23+tuxcare.els12 |
opensslTuxCare:Ubuntu:18.04 From an advisory covering 2 CVEs |
before 1.1.1-1ubuntu2.1~18.04.23+tuxcare.els12 | 1.1.1-1ubuntu2.1~18.04.23+tuxcare.els12 |
libssl-devTuxCare:Ubuntu:16.04 From an advisory covering 2 CVEs |
before 1.0.2g-1ubuntu4.21+tuxcare.els18 | 1.0.2g-1ubuntu4.21+tuxcare.els18 |
libssl-docTuxCare:Ubuntu:16.04 From an advisory covering 2 CVEs |
before 1.0.2g-1ubuntu4.21+tuxcare.els18 | 1.0.2g-1ubuntu4.21+tuxcare.els18 |
libssl1.0.0TuxCare:Ubuntu:16.04 From an advisory covering 2 CVEs |
before 1.0.2g-1ubuntu4.21+tuxcare.els18 | 1.0.2g-1ubuntu4.21+tuxcare.els18 |
opensslTuxCare:Ubuntu:16.04 From an advisory covering 2 CVEs |
before 1.0.2g-1ubuntu4.21+tuxcare.els18 | 1.0.2g-1ubuntu4.21+tuxcare.els18 |
libssl-devTuxCare:Ubuntu:20.04 From an advisory covering 2 CVEs |
before 1.1.1f-1ubuntu2.24+tuxcare.els9 | 1.1.1f-1ubuntu2.24+tuxcare.els9 |
libssl-docTuxCare:Ubuntu:20.04 From an advisory covering 2 CVEs |
before 1.1.1f-1ubuntu2.24+tuxcare.els9 | 1.1.1f-1ubuntu2.24+tuxcare.els9 |
libssl1.1TuxCare:Ubuntu:20.04 From an advisory covering 2 CVEs |
before 1.1.1f-1ubuntu2.24+tuxcare.els9 | 1.1.1f-1ubuntu2.24+tuxcare.els9 |
opensslTuxCare:Ubuntu:20.04 From an advisory covering 2 CVEs |
before 1.1.1f-1ubuntu2.24+tuxcare.els9 | 1.1.1f-1ubuntu2.24+tuxcare.els9 |
opensslTuxCare:AlmaLinux:9.2 From an advisory covering 2 CVEs |
before 1:3.0.7-20.el9_2.tuxcare.1.els25 | 1:3.0.7-20.el9_2.tuxcare.1.els25 |
openssl-develTuxCare:AlmaLinux:9.2 From an advisory covering 2 CVEs |
before 1:3.0.7-20.el9_2.tuxcare.1.els25 | 1:3.0.7-20.el9_2.tuxcare.1.els25 |
openssl-libsTuxCare:AlmaLinux:9.2 From an advisory covering 2 CVEs |
before 1:3.0.7-20.el9_2.tuxcare.1.els25 | 1:3.0.7-20.el9_2.tuxcare.1.els25 |
openssl-perlTuxCare:AlmaLinux:9.2 From an advisory covering 2 CVEs |
before 1:3.0.7-20.el9_2.tuxcare.1.els25 | 1:3.0.7-20.el9_2.tuxcare.1.els25 |
opensslTuxCare:CentOS:6 |
before 1.0.1e-63.el6.tuxcare.els17 | 1.0.1e-63.el6.tuxcare.els17 |
openssl-develTuxCare:CentOS:6 |
before 1.0.1e-63.el6.tuxcare.els17 | 1.0.1e-63.el6.tuxcare.els17 |
openssl-perlTuxCare:CentOS:6 |
before 1.0.1e-63.el6.tuxcare.els17 | 1.0.1e-63.el6.tuxcare.els17 |
openssl-staticTuxCare:CentOS:6 |
before 1.0.1e-63.el6.tuxcare.els17 | 1.0.1e-63.el6.tuxcare.els17 |
compat-openssl11TuxCare:AlmaLinux:9.6 |
before 1:1.1.1k-5.el9_6.1.tuxcare.els5 | 1:1.1.1k-5.el9_6.1.tuxcare.els5 |
opensslTuxCare:OracleLinux:6 |
before 1.0.1e-63.el6.tuxcare.els17 | 1.0.1e-63.el6.tuxcare.els17 |
openssl-develTuxCare:OracleLinux:6 |
before 1.0.1e-63.el6.tuxcare.els17 | 1.0.1e-63.el6.tuxcare.els17 |
openssl-perlTuxCare:OracleLinux:6 |
before 1.0.1e-63.el6.tuxcare.els17 | 1.0.1e-63.el6.tuxcare.els17 |
openssl-staticTuxCare:OracleLinux:6 |
before 1.0.1e-63.el6.tuxcare.els17 | 1.0.1e-63.el6.tuxcare.els17 |
opensslDebian:12 |
before 3.0.22-1~deb12u2, plus listed versions 3.0.10-13.0.10-1~deb12u13.0.11-13.0.11-1~deb12u13.0.11-1~deb12u2 Show 19 moreShow less3.0.12-13.0.12-23.0.13-1~deb12u13.0.13-1~deb12u23.0.14-1~deb12u13.0.14-1~deb12u23.0.15-1~deb12u13.0.16-1~deb12u13.0.17-1~deb12u13.0.17-1~deb12u23.0.17-1~deb12u33.0.18-1~deb12u13.0.18-1~deb12u23.0.19-1~deb12u13.0.19-1~deb12u23.0.20-1~deb12u13.0.20-1~deb12u23.0.22-1~deb12u13.0.9-1 |
3.0.22-1~deb12u2 |
opensslDebian:13 |
before 3.5.7-1~deb13u3, plus listed versions 3.5.1-13.5.1-1+deb13u13.5.2-13.5.3-13.5.4-1 Show 9 moreShow less3.5.4-1~deb13u13.5.4-1~deb13u23.5.5-13.5.5-1~deb13u13.5.5-1~deb13u23.5.6-1~deb13u13.5.6-1~deb13u23.5.7-1~deb13u13.5.7-1~deb13u2 |
3.5.7-1~deb13u3 |
opensslDebian:14 |
before 3.6.5-1, plus listed versions 3.5.1-13.5.2-13.5.3-13.5.4-13.5.4-1~deb13u1 Show 19 moreShow less3.5.4-1~deb13u23.5.5-13.5.5-1~deb13u13.5.5-1~deb13u23.5.6-1~deb13u13.5.6-1~deb13u23.5.7-1~deb13u13.5.7-1~deb13u23.5.7-1~deb13u33.6.0-13.6.0-23.6.0~~alpha1-13.6.0~~beta1-13.6.1-13.6.1-23.6.1-33.6.2-13.6.3-13.6.4-1 |
3.6.5-1 |
opensslMageia:10 From an advisory covering 13 CVEs |
before 3.5.9-1.mga10 | 3.5.9-1.mga10 |
opensslopenEuler:22.03-LTS-SP4 From an advisory covering 5 CVEs |
before 1.1.1wa-19.oe2203sp4 | 1.1.1wa-19.oe2203sp4 |
opensslopenEuler:24.03-LTS-SP1 From an advisory covering 6 CVEs |
before 3.0.12-54.oe2403sp1 | 3.0.12-54.oe2403sp1 |
opensslopenEuler:24.03-LTS-SP3 From an advisory covering 6 CVEs |
before 3.0.12-54.oe2403sp3 | 3.0.12-54.oe2403sp3 |
opensslopenEuler:24.03-LTS-SP4 From an advisory covering 13 CVEs |
before 3.5.6-8.oe2403sp4 | 3.5.6-8.oe2403sp4 |
python-cryptographyRed Hat:hummingbird:1 From an advisory covering 24 CVEs |
before 0:50.0.0-1.hum1 | 0:50.0.0-1.hum1 |
python3-cryptographyRed Hat:hummingbird:1 From an advisory covering 24 CVEs |
before 0:50.0.0-1.hum1 | 0:50.0.0-1.hum1 |
ruby3.3Red Hat:hummingbird:1 From an advisory covering 22 CVEs |
before 0:3.3.10-23.6.hum1 | 0:3.3.10-23.6.hum1 |
ruby3.3-bundled-gemsRed Hat:hummingbird:1 From an advisory covering 22 CVEs |
before 0:3.3.10-23.6.hum1 | 0:3.3.10-23.6.hum1 |
ruby3.3-default-gemsRed Hat:hummingbird:1 From an advisory covering 22 CVEs |
before 0:3.3.10-23.6.hum1 | 0:3.3.10-23.6.hum1 |
ruby3.3-develRed Hat:hummingbird:1 From an advisory covering 22 CVEs |
before 0:3.3.10-23.6.hum1 | 0:3.3.10-23.6.hum1 |
ruby3.3-docRed Hat:hummingbird:1 From an advisory covering 22 CVEs |
before 0:3.3.10-23.6.hum1 | 0:3.3.10-23.6.hum1 |
ruby3.3-libsRed Hat:hummingbird:1 From an advisory covering 22 CVEs |
before 0:3.3.10-23.6.hum1 | 0:3.3.10-23.6.hum1 |
rubygem3.3-bigdecimalRed Hat:hummingbird:1 From an advisory covering 22 CVEs |
before 0:3.1.5-23.6.hum1 | 0:3.1.5-23.6.hum1 |
rubygem3.3-bundlerRed Hat:hummingbird:1 From an advisory covering 22 CVEs |
before 0:2.5.22-23.6.hum1 | 0:2.5.22-23.6.hum1 |
rubygem3.3-develRed Hat:hummingbird:1 From an advisory covering 22 CVEs |
before 0:3.5.22-23.6.hum1 | 0:3.5.22-23.6.hum1 |
rubygem3.3-io-consoleRed Hat:hummingbird:1 From an advisory covering 22 CVEs |
before 0:0.7.1-23.6.hum1 | 0:0.7.1-23.6.hum1 |
rubygem3.3-irbRed Hat:hummingbird:1 From an advisory covering 22 CVEs |
before 0:1.13.1-23.6.hum1 | 0:1.13.1-23.6.hum1 |
rubygem3.3-jsonRed Hat:hummingbird:1 From an advisory covering 22 CVEs |
before 0:2.7.2-23.6.hum1 | 0:2.7.2-23.6.hum1 |
rubygem3.3-minitestRed Hat:hummingbird:1 From an advisory covering 22 CVEs |
before 0:5.20.0-23.6.hum1 | 0:5.20.0-23.6.hum1 |
rubygem3.3-power_assertRed Hat:hummingbird:1 From an advisory covering 22 CVEs |
before 0:2.0.3-23.6.hum1 | 0:2.0.3-23.6.hum1 |
rubygem3.3-psychRed Hat:hummingbird:1 From an advisory covering 22 CVEs |
before 0:5.1.2-23.6.hum1 | 0:5.1.2-23.6.hum1 |
rubygem3.3-raccRed Hat:hummingbird:1 From an advisory covering 22 CVEs |
before 0:1.7.3-23.6.hum1 | 0:1.7.3-23.6.hum1 |
rubygem3.3-rakeRed Hat:hummingbird:1 From an advisory covering 22 CVEs |
before 0:13.1.0-23.6.hum1 | 0:13.1.0-23.6.hum1 |
rubygem3.3-rbsRed Hat:hummingbird:1 From an advisory covering 22 CVEs |
before 0:3.4.0-23.6.hum1 | 0:3.4.0-23.6.hum1 |
rubygem3.3-rdocRed Hat:hummingbird:1 From an advisory covering 22 CVEs |
before 0:6.6.3.1-23.6.hum1 | 0:6.6.3.1-23.6.hum1 |
rubygem3.3-rexmlRed Hat:hummingbird:1 From an advisory covering 22 CVEs |
before 0:3.4.4-23.6.hum1 | 0:3.4.4-23.6.hum1 |
rubygem3.3-rssRed Hat:hummingbird:1 From an advisory covering 22 CVEs |
before 0:0.3.1-23.6.hum1 | 0:0.3.1-23.6.hum1 |
rubygem3.3-rubygemsRed Hat:hummingbird:1 From an advisory covering 22 CVEs |
before 0:3.5.22-23.6.hum1 | 0:3.5.22-23.6.hum1 |
rubygem3.3-test-unitRed Hat:hummingbird:1 From an advisory covering 22 CVEs |
before 0:3.6.1-23.6.hum1 | 0:3.6.1-23.6.hum1 |
rubygem3.3-typeprofRed Hat:hummingbird:1 From an advisory covering 22 CVEs |
before 0:0.21.9-23.6.hum1 | 0:0.21.9-23.6.hum1 |
ruby3.4Red Hat:hummingbird:1 From an advisory covering 19 CVEs |
before 0:3.4.10-31.7.hum1 | 0:3.4.10-31.7.hum1 |
ruby3.4-bundled-gemsRed Hat:hummingbird:1 From an advisory covering 19 CVEs |
before 0:3.4.10-31.7.hum1 | 0:3.4.10-31.7.hum1 |
ruby3.4-default-gemsRed Hat:hummingbird:1 From an advisory covering 19 CVEs |
before 0:3.4.10-31.7.hum1 | 0:3.4.10-31.7.hum1 |
ruby3.4-develRed Hat:hummingbird:1 From an advisory covering 19 CVEs |
before 0:3.4.10-31.7.hum1 | 0:3.4.10-31.7.hum1 |
ruby3.4-docRed Hat:hummingbird:1 From an advisory covering 19 CVEs |
before 0:3.4.10-31.7.hum1 | 0:3.4.10-31.7.hum1 |
ruby3.4-libsRed Hat:hummingbird:1 From an advisory covering 19 CVEs |
before 0:3.4.10-31.7.hum1 | 0:3.4.10-31.7.hum1 |
bootupdRed Hat:hummingbird:1 From an advisory covering 19 CVEs |
before 0:0.3.2-1.hum1 | 0:0.3.2-1.hum1 |
rust-bootupdRed Hat:hummingbird:1 From an advisory covering 19 CVEs |
before 0:0.3.2-1.hum1 | 0:0.3.2-1.hum1 |
chunkahRed Hat:hummingbird:1 |
before 0:0.7.0-1.1.hum1 | 0:0.7.0-1.1.hum1 |
opensslRed Hat:hummingbird:1 From an advisory covering 13 CVEs |
before 0:3.5.9-0.1.hum1 | 0:3.5.9-0.1.hum1 |
openssl-config-fipsRed Hat:hummingbird:1 From an advisory covering 13 CVEs |
before 0:3.5.9-0.1.hum1 | 0:3.5.9-0.1.hum1 |
openssl-develRed Hat:hummingbird:1 From an advisory covering 13 CVEs |
before 0:3.5.9-0.1.hum1 | 0:3.5.9-0.1.hum1 |
openssl-devel-engineRed Hat:hummingbird:1 From an advisory covering 13 CVEs |
before 0:3.5.9-0.1.hum1 | 0:3.5.9-0.1.hum1 |
openssl-fips-provider-upstreamRed Hat:hummingbird:1 From an advisory covering 13 CVEs |
before 0:3.5.9-0.1.hum1 | 0:3.5.9-0.1.hum1 |
openssl-libsRed Hat:hummingbird:1 From an advisory covering 13 CVEs |
before 0:3.5.9-0.1.hum1 | 0:3.5.9-0.1.hum1 |
openssl-perlRed Hat:hummingbird:1 From an advisory covering 13 CVEs |
before 0:3.5.9-0.1.hum1 | 0:3.5.9-0.1.hum1 |
openssl3Red Hat:hummingbird:1 From an advisory covering 13 CVEs |
before 0:3.5.9-0.1.hum1 | 0:3.5.9-0.1.hum1 |
openssl3-develRed Hat:hummingbird:1 From an advisory covering 13 CVEs |
before 0:3.5.9-0.1.hum1 | 0:3.5.9-0.1.hum1 |
openssl3-devel-engineRed Hat:hummingbird:1 From an advisory covering 13 CVEs |
before 0:3.5.9-0.1.hum1 | 0:3.5.9-0.1.hum1 |
openssl3-libsRed Hat:hummingbird:1 From an advisory covering 13 CVEs |
before 0:3.5.9-0.1.hum1 | 0:3.5.9-0.1.hum1 |
openssl-debuginfoRed Hat:enterprise_linux:10.2 |
before 1:3.5.8-2.el10_2 | 1:3.5.8-2.el10_2 |
openssl-debugsourceRed Hat:enterprise_linux:10.2 |
before 1:3.5.8-2.el10_2 | 1:3.5.8-2.el10_2 |
openssl-develRed Hat:enterprise_linux:10.2 |
before 1:3.5.8-2.el10_2 | 1:3.5.8-2.el10_2 |
openssl-libs-debuginfoRed Hat:enterprise_linux:10.2 |
before 1:3.5.8-2.el10_2 | 1:3.5.8-2.el10_2 |
openssl-perlRed Hat:enterprise_linux:10.2 |
before 1:3.5.8-2.el10_2 | 1:3.5.8-2.el10_2 |
opensslRed Hat:enterprise_linux:10.2 |
before 1:3.5.8-2.el10_2 | 1:3.5.8-2.el10_2 |
openssl-libsRed Hat:enterprise_linux:10.2 |
before 1:3.5.8-2.el10_2 | 1:3.5.8-2.el10_2 |
openssl-debuginfoRed Hat:enterprise_linux:9::appstream |
before 1:3.5.8-2.el9_8 | 1:3.5.8-2.el9_8 |
openssl-debugsourceRed Hat:enterprise_linux:9::appstream |
before 1:3.5.8-2.el9_8 | 1:3.5.8-2.el9_8 |
openssl-develRed Hat:enterprise_linux:9::appstream |
before 1:3.5.8-2.el9_8 | 1:3.5.8-2.el9_8 |
openssl-libs-debuginfoRed Hat:enterprise_linux:9::appstream |
before 1:3.5.8-2.el9_8 | 1:3.5.8-2.el9_8 |
openssl-perlRed Hat:enterprise_linux:9::appstream |
before 1:3.5.8-2.el9_8 | 1:3.5.8-2.el9_8 |
opensslRed Hat:enterprise_linux:9::baseos |
before 1:3.5.8-2.el9_8 | 1:3.5.8-2.el9_8 |
openssl-debuginfoRed Hat:enterprise_linux:9::baseos |
before 1:3.5.8-2.el9_8 | 1:3.5.8-2.el9_8 |
openssl-debugsourceRed Hat:enterprise_linux:9::baseos |
before 1:3.5.8-2.el9_8 | 1:3.5.8-2.el9_8 |
openssl-libsRed Hat:enterprise_linux:9::baseos |
before 1:3.5.8-2.el9_8 | 1:3.5.8-2.el9_8 |
openssl-libs-debuginfoRed Hat:enterprise_linux:9::baseos |
before 1:3.5.8-2.el9_8 | 1:3.5.8-2.el9_8 |
compat-openssl10Red Hat:enterprise_linux:8::appstream |
before 1:1.0.2o-4.el8_10.4 | 1:1.0.2o-4.el8_10.4 |
compat-openssl10-debuginfoRed Hat:enterprise_linux:8::appstream |
before 1:1.0.2o-4.el8_10.4 | 1:1.0.2o-4.el8_10.4 |
compat-openssl10-debugsourceRed Hat:enterprise_linux:8::appstream |
before 1:1.0.2o-4.el8_10.4 | 1:1.0.2o-4.el8_10.4 |
compat-openssl11Red Hat:enterprise_linux:9::appstream From an advisory covering 2 CVEs |
before 1:1.1.1k-5.el9_8.6 | 1:1.1.1k-5.el9_8.6 |
compat-openssl11-debuginfoRed Hat:enterprise_linux:9::appstream From an advisory covering 2 CVEs |
before 1:1.1.1k-5.el9_8.6 | 1:1.1.1k-5.el9_8.6 |
compat-openssl11-debugsourceRed Hat:enterprise_linux:9::appstream From an advisory covering 2 CVEs |
before 1:1.1.1k-5.el9_8.6 | 1:1.1.1k-5.el9_8.6 |
opensslRocky Linux:10 |
before 1:3.5.8-2.el10_2 | 1:3.5.8-2.el10_2 |
opensslRocky Linux:9 |
before 1:3.5.8-2.el9_8 | 1:3.5.8-2.el9_8 |
compat-openssl10Rocky Linux:8 |
before 1:1.0.2o-4.el8_10.4 | 1:1.0.2o-4.el8_10.4 |
compat-openssl11Rocky Linux:9 From an advisory covering 2 CVEs |
before 1:1.1.1k-5.el9_8.6 | 1:1.1.1k-5.el9_8.6 |
opensslRoot:Alpine:3.15 |
before 1.1.1w-r10076 | 1.1.1w-r10076 |
rootio-opensslRoot:Alpine:3.15 |
before 1.1.1w-r10076 | 1.1.1w-r10076 |
opensslRoot:Alpine:3.17 |
before 3.0.19-r00079 | 3.0.19-r00079 |
rootio-opensslRoot:Alpine:3.17 |
before 3.0.19-r00079 | 3.0.19-r00079 |
openssl-3SUSE:Linux Micro 6.0 From an advisory covering 6 CVEs |
before 3.1.4-159998.1.1 | 3.1.4-159998.1.1 |
openssl-3SUSE:Linux Micro 6.2 From an advisory covering 11 CVEs |
before 3.5.0-160000.11.1 | 3.5.0-160000.11.1 |
openssl-3SUSE:Linux Enterprise Server 16.0 From an advisory covering 11 CVEs |
before 3.5.0-160000.11.1 | 3.5.0-160000.11.1 |
openssl-3SUSE:Linux Enterprise Server for SAP applications 16.0 From an advisory covering 11 CVEs |
before 3.5.0-160000.11.1 | 3.5.0-160000.11.1 |
openssl-3SUSE:Linux Micro 6.1 From an advisory covering 6 CVEs |
before 3.1.4-slfo.1.1_14.1 | 3.1.4-slfo.1.1_14.1 |
openssl-3-livepatchesSUSE:Linux Micro 6.1 |
before 0.7-slfo.1.1_1.1 | 0.7-slfo.1.1_1.1 |
openssl-3SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS From an advisory covering 6 CVEs |
before 3.0.8-150500.5.80.1 | 3.0.8-150500.5.80.1 |
openssl-3SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS From an advisory covering 6 CVEs |
before 3.0.8-150500.5.80.1 | 3.0.8-150500.5.80.1 |
openssl-3SUSE:Linux Enterprise Server 15 SP5-LTSS From an advisory covering 6 CVEs |
before 3.0.8-150500.5.80.1 | 3.0.8-150500.5.80.1 |
openssl-3SUSE:Linux Enterprise Server for SAP Applications 15 SP5 From an advisory covering 6 CVEs |
before 3.0.8-150500.5.80.1 | 3.0.8-150500.5.80.1 |
openssl-3SUSE:Linux Enterprise Micro 5.3 From an advisory covering 6 CVEs |
before 3.0.8-150400.4.101.1 | 3.0.8-150400.4.101.1 |
openssl-3SUSE:Linux Enterprise Micro 5.4 From an advisory covering 6 CVEs |
before 3.0.8-150400.4.101.1 | 3.0.8-150400.4.101.1 |
openssl-3SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS From an advisory covering 6 CVEs |
before 3.0.8-150400.4.101.1 | 3.0.8-150400.4.101.1 |
openssl-3SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS From an advisory covering 6 CVEs |
before 3.0.8-150400.4.101.1 | 3.0.8-150400.4.101.1 |
openssl-3SUSE:Linux Enterprise Server 15 SP4-LTSS From an advisory covering 6 CVEs |
before 3.0.8-150400.4.101.1 | 3.0.8-150400.4.101.1 |
openssl-3SUSE:Linux Enterprise Server for SAP Applications 15 SP4 From an advisory covering 6 CVEs |
before 3.0.8-150400.4.101.1 | 3.0.8-150400.4.101.1 |
openssl-3SUSE:Linux Enterprise Module for Basesystem 15 SP7 From an advisory covering 11 CVEs |
before 3.5.0-150700.5.53.2 | 3.5.0-150700.5.53.2 |
openssl-3-livepatchesSUSE:Linux Enterprise Live Patching 15 SP6 |
before 0.7-150600.13.22.1 | 0.7-150600.13.22.1 |
openssl-3SUSE:Linux Enterprise Server 15 SP6-LTSS From an advisory covering 6 CVEs |
before 3.1.4-150600.5.67.1 | 3.1.4-150600.5.67.1 |
openssl-3SUSE:Linux Enterprise Server for SAP Applications 15 SP6 From an advisory covering 6 CVEs |
before 3.1.4-150600.5.67.1 | 3.1.4-150600.5.67.1 |
openssl-3-livepatchesSUSE:Linux Enterprise Live Patching 15 SP7 |
before 0.7-150700.16.15.1 | 0.7-150700.16.15.1 |
opensslUbuntu:Pro:14.04:LTS |
before 1.0.1f-1ubuntu2.27+esm17, plus listed versions 1.0.1e-3ubuntu11.0.1e-4ubuntu11.0.1e-4ubuntu21.0.1e-4ubuntu31.0.1e-4ubuntu4 Show 38 moreShow less1.0.1f-1ubuntu11.0.1f-1ubuntu21.0.1f-1ubuntu2.11.0.1f-1ubuntu2.21.0.1f-1ubuntu2.31.0.1f-1ubuntu2.41.0.1f-1ubuntu2.51.0.1f-1ubuntu2.71.0.1f-1ubuntu2.81.0.1f-1ubuntu2.111.0.1f-1ubuntu2.121.0.1f-1ubuntu2.151.0.1f-1ubuntu2.161.0.1f-1ubuntu2.171.0.1f-1ubuntu2.181.0.1f-1ubuntu2.191.0.1f-1ubuntu2.201.0.1f-1ubuntu2.211.0.1f-1ubuntu2.221.0.1f-1ubuntu2.231.0.1f-1ubuntu2.241.0.1f-1ubuntu2.251.0.1f-1ubuntu2.261.0.1f-1ubuntu2.271.0.1f-1ubuntu2.27+esm11.0.1f-1ubuntu2.27+esm21.0.1f-1ubuntu2.27+esm31.0.1f-1ubuntu2.27+esm41.0.1f-1ubuntu2.27+esm51.0.1f-1ubuntu2.27+esm61.0.1f-1ubuntu2.27+esm71.0.1f-1ubuntu2.27+esm91.0.1f-1ubuntu2.27+esm101.0.1f-1ubuntu2.27+esm111.0.1f-1ubuntu2.27+esm121.0.1f-1ubuntu2.27+esm131.0.1f-1ubuntu2.27+esm141.0.1f-1ubuntu2.27+esm16 |
1.0.1f-1ubuntu2.27+esm17 |
opensslUbuntu:Pro:16.04:LTS |
before 1.0.2g-1ubuntu4.20+esm19, plus listed versions 1.0.2d-0ubuntu11.0.2d-0ubuntu21.0.2e-1ubuntu11.0.2f-2ubuntu11.0.2g-1ubuntu2 Show 36 moreShow less1.0.2g-1ubuntu31.0.2g-1ubuntu41.0.2g-1ubuntu4.11.0.2g-1ubuntu4.21.0.2g-1ubuntu4.41.0.2g-1ubuntu4.51.0.2g-1ubuntu4.61.0.2g-1ubuntu4.81.0.2g-1ubuntu4.91.0.2g-1ubuntu4.101.0.2g-1ubuntu4.111.0.2g-1ubuntu4.121.0.2g-1ubuntu4.131.0.2g-1ubuntu4.141.0.2g-1ubuntu4.151.0.2g-1ubuntu4.161.0.2g-1ubuntu4.171.0.2g-1ubuntu4.181.0.2g-1ubuntu4.191.0.2g-1ubuntu4.201.0.2g-1ubuntu4.20+esm11.0.2g-1ubuntu4.20+esm21.0.2g-1ubuntu4.20+esm31.0.2g-1ubuntu4.20+esm41.0.2g-1ubuntu4.20+esm51.0.2g-1ubuntu4.20+esm61.0.2g-1ubuntu4.20+esm71.0.2g-1ubuntu4.20+esm91.0.2g-1ubuntu4.20+esm101.0.2g-1ubuntu4.20+esm111.0.2g-1ubuntu4.20+esm121.0.2g-1ubuntu4.20+esm131.0.2g-1ubuntu4.20+esm141.0.2g-1ubuntu4.20+esm151.0.2g-1ubuntu4.20+esm161.0.2g-1ubuntu4.20+esm18 |
1.0.2g-1ubuntu4.20+esm19 |
edk2Ubuntu:Pro:16.04:LTS |
All versions, plus listed versions 0~20150106.5c2d456b-20~20160104.c2a892d7-10~20160408.ffea0a2c-20~20160408.ffea0a2c-2ubuntu0.10~20160408.ffea0a2c-2ubuntu0.20~20160408.ffea0a2c-2ubuntu0.2+esm10~20160408.ffea0a2c-2ubuntu0.2+esm30~20160408.ffea0a2c-2ubuntu0.2+esm4 |
None known |
nodejsUbuntu:Pro:16.04:LTS |
All versions, plus listed versions 0.10.25~dfsg2-2ubuntu14.2.2~dfsg-14.2.3~dfsg-14.2.4~dfsg-1ubuntu14.2.4~dfsg-2 Show 7 moreShow less4.2.6~dfsg-1ubuntu14.2.6~dfsg-1ubuntu44.2.6~dfsg-1ubuntu4.14.2.6~dfsg-1ubuntu4.24.2.6~dfsg-1ubuntu4.2+esm14.2.6~dfsg-1ubuntu4.2+esm24.2.6~dfsg-1ubuntu4.2+esm3 |
None known |
opensslUbuntu:Pro:FIPS-updates:16.04:LTS |
All versions, plus listed versions 1.0.2g-1ubuntu4.fips.4.9.11.0.2g-1ubuntu4.fips.4.13.11.0.2g-1ubuntu4.fips.4.15.11.0.2g-1ubuntu4.fips.4.16.11.0.2g-1ubuntu4.fips.4.17.1 Show 14 moreShow less1.0.2g-1ubuntu4.fips.4.18.11.0.2g-1ubuntu4.fips.4.19.31.0.2g-1ubuntu4.fips.4.20.11.0.2g-1ubuntu4.fips.4.20.21.0.2g-1ubuntu4.fips.4.20.31.0.2g-1ubuntu4.fips.4.20.61.0.2g-1ubuntu4.fips.4.20.71.0.2g-1ubuntu4.fips.4.20.91.0.2g-1ubuntu4.fips.4.20.101.0.2g-1ubuntu4.fips.4.20.111.0.2g-1ubuntu4.fips.4.20.121.0.2g-1ubuntu4.fips.4.20.131.0.2g-1ubuntu4.fips.4.20.141.0.2g-1ubuntu4.fips.4.20.15 |
None known |
opensslUbuntu:Pro:FIPS:16.04:LTS |
All versions, plus listed versions 1.0.2g-1ubuntu4.fips.4.6~ppa11.0.2g-1ubuntu4.fips.4.6~ppa21.0.2g-1ubuntu4.fips.4.6~ppa31.0.2g-1ubuntu4.fips.4.61.0.2g-1ubuntu4.fips.4.6.11.0.2g-1ubuntu4.fips.4.6.21.0.2g-1ubuntu4.fips.4.6.3 |
None known |
opensslUbuntu:Pro:18.04:LTS |
before 1.1.1-1ubuntu2.1~18.04.23+esm11, plus listed versions 1.0.2g-1ubuntu131.0.2g-1ubuntu141.0.2n-1ubuntu11.1.0g-2ubuntu11.1.0g-2ubuntu2 Show 32 moreShow less1.1.0g-2ubuntu31.1.0g-2ubuntu41.1.0g-2ubuntu4.11.1.0g-2ubuntu4.31.1.1-1ubuntu2.1~18.04.11.1.1-1ubuntu2.1~18.04.21.1.1-1ubuntu2.1~18.04.31.1.1-1ubuntu2.1~18.04.41.1.1-1ubuntu2.1~18.04.51.1.1-1ubuntu2.1~18.04.61.1.1-1ubuntu2.1~18.04.71.1.1-1ubuntu2.1~18.04.81.1.1-1ubuntu2.1~18.04.91.1.1-1ubuntu2.1~18.04.101.1.1-1ubuntu2.1~18.04.131.1.1-1ubuntu2.1~18.04.141.1.1-1ubuntu2.1~18.04.151.1.1-1ubuntu2.1~18.04.171.1.1-1ubuntu2.1~18.04.191.1.1-1ubuntu2.1~18.04.201.1.1-1ubuntu2.1~18.04.211.1.1-1ubuntu2.1~18.04.221.1.1-1ubuntu2.1~18.04.231.1.1-1ubuntu2.1~18.04.23+esm11.1.1-1ubuntu2.1~18.04.23+esm31.1.1-1ubuntu2.1~18.04.23+esm41.1.1-1ubuntu2.1~18.04.23+esm51.1.1-1ubuntu2.1~18.04.23+esm61.1.1-1ubuntu2.1~18.04.23+esm71.1.1-1ubuntu2.1~18.04.23+esm81.1.1-1ubuntu2.1~18.04.23+esm91.1.1-1ubuntu2.1~18.04.23+esm10 |
1.1.1-1ubuntu2.1~18.04.23+esm11 |
openssl1.0Ubuntu:Pro:18.04:LTS |
before 1.0.2n-1ubuntu5.13+esm7, plus listed versions 1.0.2n-1ubuntu21.0.2n-1ubuntu31.0.2n-1ubuntu41.0.2n-1ubuntu51.0.2n-1ubuntu5.1 Show 18 moreShow less1.0.2n-1ubuntu5.21.0.2n-1ubuntu5.31.0.2n-1ubuntu5.41.0.2n-1ubuntu5.51.0.2n-1ubuntu5.61.0.2n-1ubuntu5.71.0.2n-1ubuntu5.81.0.2n-1ubuntu5.91.0.2n-1ubuntu5.101.0.2n-1ubuntu5.111.0.2n-1ubuntu5.121.0.2n-1ubuntu5.131.0.2n-1ubuntu5.13+esm11.0.2n-1ubuntu5.13+esm21.0.2n-1ubuntu5.13+esm31.0.2n-1ubuntu5.13+esm41.0.2n-1ubuntu5.13+esm51.0.2n-1ubuntu5.13+esm6 |
1.0.2n-1ubuntu5.13+esm7 |
edk2Ubuntu:Pro:18.04:LTS |
All versions, plus listed versions 0~20170911.5dfba97c-10~20171010.234dbcef-10~20171027.76fd5a66-10~20171205.a9212288-10~20180105.0bc94c74-1 Show 8 moreShow less0~20180205.c0d9813c-10~20180205.c0d9813c-20~20180205.c0d9813c-2ubuntu0.10~20180205.c0d9813c-2ubuntu0.20~20180205.c0d9813c-2ubuntu0.30~20180205.c0d9813c-2ubuntu0.3+esm10~20180205.c0d9813c-2ubuntu0.3+esm20~20180205.c0d9813c-2ubuntu0.3+esm3 |
None known |
nodejsUbuntu:Pro:18.04:LTS |
All versions, plus listed versions 6.11.4~dfsg-1ubuntu16.11.4~dfsg-1ubuntu26.12.0~dfsg-1ubuntu16.12.0~dfsg-2ubuntu16.12.0~dfsg-2ubuntu2 Show 10 moreShow less8.10.0~dfsg-28.10.0~dfsg-2ubuntu0.28.10.0~dfsg-2ubuntu0.38.10.0~dfsg-2ubuntu0.48.10.0~dfsg-2ubuntu0.4+esm18.10.0~dfsg-2ubuntu0.4+esm28.10.0~dfsg-2ubuntu0.4+esm38.10.0~dfsg-2ubuntu0.4+esm48.10.0~dfsg-2ubuntu0.4+esm58.10.0~dfsg-2ubuntu0.4+esm6 |
None known |
opensslUbuntu:Pro:FIPS-updates:18.04:LTS |
All versions, plus listed versions 1.1.1-1ubuntu2.fips.2.1~18.04.5.11.1.1-1ubuntu2.fips.2.1~18.04.6.11.1.1-1ubuntu2.fips.2.1~18.04.7.11.1.1-1ubuntu2.fips.2.1~18.04.9.11.1.1-1ubuntu2.fips.2.1~18.04.9.2 Show 17 moreShow less1.1.1-1ubuntu2.fips.2.1~18.04.9.31.1.1-1ubuntu2.fips.2.1~18.04.13.21.1.1-1ubuntu2.fips.2.1~18.04.151.1.1-1ubuntu2.fips.2.1~18.04.15.11.1.1-1ubuntu2.fips.2.1~18.04.15.21.1.1-1ubuntu2.fips.2.1~18.04.171.1.1-1ubuntu2.fips.2.1~18.04.201.1.1-1ubuntu2.fips.2.1~18.04.211.1.1-1ubuntu2.fips.2.1~18.04.221.1.1-1ubuntu2.fips.2.1~18.04.231.1.1-1ubuntu2.fips.2.1~18.04.23.31.1.1-1ubuntu2.fips.2.1~18.04.23.41.1.1-1ubuntu2.fips.2.1~18.04.23.51.1.1-1ubuntu2.fips.2.1~18.04.23.61.1.1-1ubuntu2.fips.2.1~18.04.23.71.1.1-1ubuntu2.fips.2.1~18.04.23.81.1.1-1ubuntu2.fips.2.1~18.04.23.9 |
None known |
opensslUbuntu:Pro:FIPS:18.04:LTS |
All versions, plus listed versions 1.1.1-1ubuntu2.fips.2.1~18.04.3.11.1.1-1ubuntu2.fips.2.1~18.04.15.2 |
None known |
edk2Ubuntu:Pro:20.04:LTS |
All versions, plus listed versions 0~20190606.20d2e5a1-2ubuntu10~20190828.37eef910-30~20190828.37eef910-40~20191122.bd85bf54-10~20191122.bd85bf54-1ubuntu1 Show 11 moreShow less0~20191122.bd85bf54-20~20191122.bd85bf54-2ubuntu10~20191122.bd85bf54-2ubuntu20~20191122.bd85bf54-2ubuntu30~20191122.bd85bf54-2ubuntu3.10~20191122.bd85bf54-2ubuntu3.20~20191122.bd85bf54-2ubuntu3.30~20191122.bd85bf54-2ubuntu3.40~20191122.bd85bf54-2ubuntu3.50~20191122.bd85bf54-2ubuntu3.60~20191122.bd85bf54-2ubuntu3.6+esm1 |
None known |
opensslUbuntu:Pro:20.04:LTS |
before 1.1.1f-1ubuntu2.24+esm6, plus listed versions 1.1.1c-1ubuntu41.1.1d-2ubuntu31.1.1d-2ubuntu61.1.1f-1ubuntu11.1.1f-1ubuntu2 Show 26 moreShow less1.1.1f-1ubuntu2.11.1.1f-1ubuntu2.21.1.1f-1ubuntu2.31.1.1f-1ubuntu2.41.1.1f-1ubuntu2.51.1.1f-1ubuntu2.81.1.1f-1ubuntu2.91.1.1f-1ubuntu2.101.1.1f-1ubuntu2.111.1.1f-1ubuntu2.121.1.1f-1ubuntu2.131.1.1f-1ubuntu2.151.1.1f-1ubuntu2.161.1.1f-1ubuntu2.171.1.1f-1ubuntu2.181.1.1f-1ubuntu2.191.1.1f-1ubuntu2.201.1.1f-1ubuntu2.211.1.1f-1ubuntu2.221.1.1f-1ubuntu2.231.1.1f-1ubuntu2.241.1.1f-1ubuntu2.24+esm11.1.1f-1ubuntu2.24+esm21.1.1f-1ubuntu2.24+esm31.1.1f-1ubuntu2.24+esm41.1.1f-1ubuntu2.24+esm5 |
1.1.1f-1ubuntu2.24+esm6 |
opensslUbuntu:Pro:FIPS-updates:20.04:LTS |
All versions, plus listed versions 1.1.1f-1ubuntu2.fips.71.1.1f-1ubuntu2.fips.7.21.1.1f-1ubuntu2.fips.121.1.1f-1ubuntu2.fips.131.1.1f-1ubuntu2.fips.13.1 Show 13 moreShow less1.1.1f-1ubuntu2.fips.161.1.1f-1ubuntu2.fips.171.1.1f-1ubuntu2.fips.181.1.1f-1ubuntu2.fips.191.1.1f-1ubuntu2.fips.201.1.1f-1ubuntu2.fips.211.1.1f-1ubuntu2.fips.221.1.1f-1ubuntu2.fips.241.1.1f-1ubuntu2.fips.24.11.1.1f-1ubuntu2.fips.24.21.1.1f-1ubuntu2.fips.24.31.1.1f-1ubuntu2.fips.24.41.1.1f-1ubuntu2.fips.24.6 |
None known |
opensslUbuntu:Pro:FIPS:20.04:LTS |
All versions, plus listed versions 1.1.1f-1ubuntu2.fips.2.81.1.1f-1ubuntu2.fips.7.1 |
None known |
edk2Ubuntu:22.04:LTS |
All versions, plus listed versions 2021.08~rc0-22021.08-32021.11~rc1-12021.11-12021.11-2 Show 12 moreShow less2022.02~rc1-12022.02~rc1-1ubuntu12022.02-12022.02-22022.02-32022.02-3ubuntu0.22.04.12022.02-3ubuntu0.22.04.22022.02-3ubuntu0.22.04.32022.02-3ubuntu0.22.04.42022.02-3ubuntu0.22.04.52022.02-3ubuntu0.22.04.62022.02-3ubuntu0.22.04.7 |
None known |
opensslUbuntu:22.04:LTS |
before 3.0.2-0ubuntu1.30, plus listed versions 1.1.1l-1ubuntu13.0.0-1ubuntu13.0.1-0ubuntu13.0.2-0ubuntu13.0.2-0ubuntu1.1 Show 22 moreShow less3.0.2-0ubuntu1.23.0.2-0ubuntu1.43.0.2-0ubuntu1.53.0.2-0ubuntu1.63.0.2-0ubuntu1.73.0.2-0ubuntu1.83.0.2-0ubuntu1.93.0.2-0ubuntu1.103.0.2-0ubuntu1.123.0.2-0ubuntu1.133.0.2-0ubuntu1.143.0.2-0ubuntu1.153.0.2-0ubuntu1.163.0.2-0ubuntu1.173.0.2-0ubuntu1.183.0.2-0ubuntu1.193.0.2-0ubuntu1.203.0.2-0ubuntu1.213.0.2-0ubuntu1.233.0.2-0ubuntu1.253.0.2-0ubuntu1.263.0.2-0ubuntu1.29 |
3.0.2-0ubuntu1.30 |
nodejsUbuntu:Pro:22.04:LTS |
All versions, plus listed versions 12.22.5~dfsg-5ubuntu112.22.7~dfsg-2ubuntu112.22.7~dfsg-2ubuntu312.22.9~dfsg-1ubuntu212.22.9~dfsg-1ubuntu3 Show 7 moreShow less12.22.9~dfsg-1ubuntu3.112.22.9~dfsg-1ubuntu3.212.22.9~dfsg-1ubuntu3.312.22.9~dfsg-1ubuntu3.412.22.9~dfsg-1ubuntu3.512.22.9~dfsg-1ubuntu3.612.22.9~dfsg-1ubuntu3.6+esm2 |
None known |
opensslUbuntu:Pro:FIPS-preview:22.04:LTS |
All versions, plus listed versions 3.0.2-0ubuntu1.10+Fips13.0.2-0ubuntu1.12+Fips1 |
None known |
openssl-fipsUbuntu:Pro:FIPS-preview:22.04:LTS |
All versions, plus listed versions 3.0.5-0ubuntu0.1+Fips2.1 |
None known |
opensslUbuntu:Pro:FIPS-updates:22.04:LTS |
All versions, plus listed versions 3.0.2-0ubuntu1.10+Fips13.0.2-0ubuntu1.12+Fips13.0.2-0ubuntu1.14+Fips13.0.2-0ubuntu1.15+Fips13.0.2-0ubuntu1.16+Fips1 Show 10 moreShow less3.0.2-0ubuntu1.17+Fips13.0.2-0ubuntu1.18+Fips13.0.2-0ubuntu1.19+Fips13.0.2-0ubuntu1.20+Fips13.0.2-0ubuntu1.21+Fips13.0.2-0ubuntu1.23+Fips13.0.2-0ubuntu1.25+Fips13.0.2-0ubuntu1.26+Fips13.0.2-0ubuntu1.29+Fips13.0.2-0ubuntu1.30+Fips1 |
None known |
openssl-fipsUbuntu:Pro:FIPS-updates:22.04:LTS |
All versions, plus listed versions 3.0.5-0ubuntu0.1+Fips2.13.0.5-0ubuntu0.2+Fips1 |
None known |
edk2Ubuntu:24.04:LTS |
All versions, plus listed versions 2023.05-22023.11-22023.11-32023.11-42023.11-5 Show 13 moreShow less2023.11-62023.11-82024.02-12024.02-22024.02-2ubuntu0.12024.02-2ubuntu0.32024.02-2ubuntu0.42024.02-2ubuntu0.52024.02-2ubuntu0.62024.02-2ubuntu0.72024.02-2ubuntu0.82024.02-2ubuntu0.92024.02-2ubuntu0.10 |
None known |
opensslUbuntu:24.04:LTS |
before 3.0.13-0ubuntu3.16, plus listed versions 3.0.10-1ubuntu23.0.10-1ubuntu2.13.0.10-1ubuntu33.0.10-1ubuntu43.0.13-0ubuntu2 Show 12 moreShow less3.0.13-0ubuntu33.0.13-0ubuntu3.13.0.13-0ubuntu3.23.0.13-0ubuntu3.33.0.13-0ubuntu3.43.0.13-0ubuntu3.53.0.13-0ubuntu3.63.0.13-0ubuntu3.73.0.13-0ubuntu3.93.0.13-0ubuntu3.113.0.13-0ubuntu3.123.0.13-0ubuntu3.15 |
3.0.13-0ubuntu3.16 |
openssl-fipsUbuntu:Pro:FIPS-updates:24.04:LTS |
All versions, plus listed versions 3.0.13-0ubuntu3+Fips13.0.13-0ubuntu3.6+Fips13.0.13-0ubuntu3.12+Fips13.0.13-0ubuntu3.15+Fips13.0.13-0ubuntu3.15+Fips2 |
None known |
edk2Ubuntu:26.10 |
All versions, plus listed versions 2025.11-3ubuntu72025.11-3ubuntu82026.05-2ubuntu12026.05-2ubuntu22026.05-2ubuntu3 |
None known |
edk2-hweUbuntu:26.10 |
All versions, plus listed versions 2025.11-3ubuntu82025.11-3ubuntu92026.05-2ubuntu12026.05-2ubuntu22026.05-2ubuntu3 |
None known |
edk2Ubuntu:26.04:LTS |
All versions, plus listed versions 2025.02-8ubuntu32025.11-3ubuntu62025.11-3ubuntu72025.11-3ubuntu7.22025.11-3ubuntu7.3 |
None known |
edk2-hweUbuntu:26.04:LTS |
All versions, plus listed versions 2025.11-3ubuntu62025.11-3ubuntu82025.11-3ubuntu8.2 |
None known |
opensslUbuntu:26.04:LTS |
before 3.5.5-1ubuntu3.6, plus listed versions 3.5.3-1ubuntu23.5.5-1ubuntu13.5.5-1ubuntu33.5.5-1ubuntu3.23.5.5-1ubuntu3.33.5.5-1ubuntu3.43.5.5-1ubuntu3.5 |
3.5.5-1ubuntu3.6 |
opensslUbuntu:22.04:LTS From an advisory covering 11 CVEs |
before 3.0.2-0ubuntu1.30, plus listed versions 1.1.1l-1ubuntu13.0.0-1ubuntu13.0.1-0ubuntu13.0.2-0ubuntu13.0.2-0ubuntu1.1 Show 22 moreShow less3.0.2-0ubuntu1.23.0.2-0ubuntu1.43.0.2-0ubuntu1.53.0.2-0ubuntu1.63.0.2-0ubuntu1.73.0.2-0ubuntu1.83.0.2-0ubuntu1.93.0.2-0ubuntu1.103.0.2-0ubuntu1.123.0.2-0ubuntu1.133.0.2-0ubuntu1.143.0.2-0ubuntu1.153.0.2-0ubuntu1.163.0.2-0ubuntu1.173.0.2-0ubuntu1.183.0.2-0ubuntu1.193.0.2-0ubuntu1.203.0.2-0ubuntu1.213.0.2-0ubuntu1.233.0.2-0ubuntu1.253.0.2-0ubuntu1.263.0.2-0ubuntu1.29 |
3.0.2-0ubuntu1.30 |
opensslUbuntu:24.04:LTS From an advisory covering 11 CVEs |
before 3.0.13-0ubuntu3.16, plus listed versions 3.0.10-1ubuntu23.0.10-1ubuntu2.13.0.10-1ubuntu33.0.10-1ubuntu43.0.13-0ubuntu2 Show 12 moreShow less3.0.13-0ubuntu33.0.13-0ubuntu3.13.0.13-0ubuntu3.23.0.13-0ubuntu3.33.0.13-0ubuntu3.43.0.13-0ubuntu3.53.0.13-0ubuntu3.63.0.13-0ubuntu3.73.0.13-0ubuntu3.93.0.13-0ubuntu3.113.0.13-0ubuntu3.123.0.13-0ubuntu3.15 |
3.0.13-0ubuntu3.16 |
opensslUbuntu:26.04:LTS From an advisory covering 11 CVEs |
before 3.5.5-1ubuntu3.6, plus listed versions 3.5.3-1ubuntu23.5.5-1ubuntu13.5.5-1ubuntu33.5.5-1ubuntu3.23.5.5-1ubuntu3.33.5.5-1ubuntu3.43.5.5-1ubuntu3.5 |
3.5.5-1ubuntu3.6 |
opensslUbuntu:Pro:14.04:LTS From an advisory covering 4 CVEs |
before 1.0.1f-1ubuntu2.27+esm17, plus listed versions 1.0.1e-3ubuntu11.0.1e-4ubuntu11.0.1e-4ubuntu21.0.1e-4ubuntu31.0.1e-4ubuntu4 Show 38 moreShow less1.0.1f-1ubuntu11.0.1f-1ubuntu21.0.1f-1ubuntu2.11.0.1f-1ubuntu2.21.0.1f-1ubuntu2.31.0.1f-1ubuntu2.41.0.1f-1ubuntu2.51.0.1f-1ubuntu2.71.0.1f-1ubuntu2.81.0.1f-1ubuntu2.111.0.1f-1ubuntu2.121.0.1f-1ubuntu2.151.0.1f-1ubuntu2.161.0.1f-1ubuntu2.171.0.1f-1ubuntu2.181.0.1f-1ubuntu2.191.0.1f-1ubuntu2.201.0.1f-1ubuntu2.211.0.1f-1ubuntu2.221.0.1f-1ubuntu2.231.0.1f-1ubuntu2.241.0.1f-1ubuntu2.251.0.1f-1ubuntu2.261.0.1f-1ubuntu2.271.0.1f-1ubuntu2.27+esm11.0.1f-1ubuntu2.27+esm21.0.1f-1ubuntu2.27+esm31.0.1f-1ubuntu2.27+esm41.0.1f-1ubuntu2.27+esm51.0.1f-1ubuntu2.27+esm61.0.1f-1ubuntu2.27+esm71.0.1f-1ubuntu2.27+esm91.0.1f-1ubuntu2.27+esm101.0.1f-1ubuntu2.27+esm111.0.1f-1ubuntu2.27+esm121.0.1f-1ubuntu2.27+esm131.0.1f-1ubuntu2.27+esm141.0.1f-1ubuntu2.27+esm16 |
1.0.1f-1ubuntu2.27+esm17 |
opensslUbuntu:Pro:16.04:LTS From an advisory covering 4 CVEs |
before 1.0.2g-1ubuntu4.20+esm19, plus listed versions 1.0.2d-0ubuntu11.0.2d-0ubuntu21.0.2e-1ubuntu11.0.2f-2ubuntu11.0.2g-1ubuntu2 Show 36 moreShow less1.0.2g-1ubuntu31.0.2g-1ubuntu41.0.2g-1ubuntu4.11.0.2g-1ubuntu4.21.0.2g-1ubuntu4.41.0.2g-1ubuntu4.51.0.2g-1ubuntu4.61.0.2g-1ubuntu4.81.0.2g-1ubuntu4.91.0.2g-1ubuntu4.101.0.2g-1ubuntu4.111.0.2g-1ubuntu4.121.0.2g-1ubuntu4.131.0.2g-1ubuntu4.141.0.2g-1ubuntu4.151.0.2g-1ubuntu4.161.0.2g-1ubuntu4.171.0.2g-1ubuntu4.181.0.2g-1ubuntu4.191.0.2g-1ubuntu4.201.0.2g-1ubuntu4.20+esm11.0.2g-1ubuntu4.20+esm21.0.2g-1ubuntu4.20+esm31.0.2g-1ubuntu4.20+esm41.0.2g-1ubuntu4.20+esm51.0.2g-1ubuntu4.20+esm61.0.2g-1ubuntu4.20+esm71.0.2g-1ubuntu4.20+esm91.0.2g-1ubuntu4.20+esm101.0.2g-1ubuntu4.20+esm111.0.2g-1ubuntu4.20+esm121.0.2g-1ubuntu4.20+esm131.0.2g-1ubuntu4.20+esm141.0.2g-1ubuntu4.20+esm151.0.2g-1ubuntu4.20+esm161.0.2g-1ubuntu4.20+esm18 |
1.0.2g-1ubuntu4.20+esm19 |
opensslUbuntu:Pro:18.04:LTS From an advisory covering 4 CVEs |
before 1.1.1-1ubuntu2.1~18.04.23+esm11, plus listed versions 1.0.2g-1ubuntu131.0.2g-1ubuntu141.0.2n-1ubuntu11.1.0g-2ubuntu11.1.0g-2ubuntu2 Show 32 moreShow less1.1.0g-2ubuntu31.1.0g-2ubuntu41.1.0g-2ubuntu4.11.1.0g-2ubuntu4.31.1.1-1ubuntu2.1~18.04.11.1.1-1ubuntu2.1~18.04.21.1.1-1ubuntu2.1~18.04.31.1.1-1ubuntu2.1~18.04.41.1.1-1ubuntu2.1~18.04.51.1.1-1ubuntu2.1~18.04.61.1.1-1ubuntu2.1~18.04.71.1.1-1ubuntu2.1~18.04.81.1.1-1ubuntu2.1~18.04.91.1.1-1ubuntu2.1~18.04.101.1.1-1ubuntu2.1~18.04.131.1.1-1ubuntu2.1~18.04.141.1.1-1ubuntu2.1~18.04.151.1.1-1ubuntu2.1~18.04.171.1.1-1ubuntu2.1~18.04.191.1.1-1ubuntu2.1~18.04.201.1.1-1ubuntu2.1~18.04.211.1.1-1ubuntu2.1~18.04.221.1.1-1ubuntu2.1~18.04.231.1.1-1ubuntu2.1~18.04.23+esm11.1.1-1ubuntu2.1~18.04.23+esm31.1.1-1ubuntu2.1~18.04.23+esm41.1.1-1ubuntu2.1~18.04.23+esm51.1.1-1ubuntu2.1~18.04.23+esm61.1.1-1ubuntu2.1~18.04.23+esm71.1.1-1ubuntu2.1~18.04.23+esm81.1.1-1ubuntu2.1~18.04.23+esm91.1.1-1ubuntu2.1~18.04.23+esm10 |
1.1.1-1ubuntu2.1~18.04.23+esm11 |
openssl1.0Ubuntu:Pro:18.04:LTS From an advisory covering 4 CVEs |
before 1.0.2n-1ubuntu5.13+esm7, plus listed versions 1.0.2n-1ubuntu21.0.2n-1ubuntu31.0.2n-1ubuntu41.0.2n-1ubuntu51.0.2n-1ubuntu5.1 Show 18 moreShow less1.0.2n-1ubuntu5.21.0.2n-1ubuntu5.31.0.2n-1ubuntu5.41.0.2n-1ubuntu5.51.0.2n-1ubuntu5.61.0.2n-1ubuntu5.71.0.2n-1ubuntu5.81.0.2n-1ubuntu5.91.0.2n-1ubuntu5.101.0.2n-1ubuntu5.111.0.2n-1ubuntu5.121.0.2n-1ubuntu5.131.0.2n-1ubuntu5.13+esm11.0.2n-1ubuntu5.13+esm21.0.2n-1ubuntu5.13+esm31.0.2n-1ubuntu5.13+esm41.0.2n-1ubuntu5.13+esm51.0.2n-1ubuntu5.13+esm6 |
1.0.2n-1ubuntu5.13+esm7 |
opensslUbuntu:Pro:20.04:LTS From an advisory covering 4 CVEs |
before 1.1.1f-1ubuntu2.24+esm6, plus listed versions 1.1.1c-1ubuntu41.1.1d-2ubuntu31.1.1d-2ubuntu61.1.1f-1ubuntu11.1.1f-1ubuntu2 Show 26 moreShow less1.1.1f-1ubuntu2.11.1.1f-1ubuntu2.21.1.1f-1ubuntu2.31.1.1f-1ubuntu2.41.1.1f-1ubuntu2.51.1.1f-1ubuntu2.81.1.1f-1ubuntu2.91.1.1f-1ubuntu2.101.1.1f-1ubuntu2.111.1.1f-1ubuntu2.121.1.1f-1ubuntu2.131.1.1f-1ubuntu2.151.1.1f-1ubuntu2.161.1.1f-1ubuntu2.171.1.1f-1ubuntu2.181.1.1f-1ubuntu2.191.1.1f-1ubuntu2.201.1.1f-1ubuntu2.211.1.1f-1ubuntu2.221.1.1f-1ubuntu2.231.1.1f-1ubuntu2.241.1.1f-1ubuntu2.24+esm11.1.1f-1ubuntu2.24+esm21.1.1f-1ubuntu2.24+esm31.1.1f-1ubuntu2.24+esm41.1.1f-1ubuntu2.24+esm5 |
1.1.1f-1ubuntu2.24+esm6 |
openssl-3openSUSE:Leap 16.0 From an advisory covering 11 CVEs |
before 3.5.0-160000.11.1 | 3.5.0-160000.11.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected, aliases, references | OSV | |
| affected | ||
| facts | OSV | |
| affected | ||
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2026-84782 is a high vulnerability (CVSS 8.2) in Openssl, published August 29, 2026. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.83%, the 57th percentile. Fixed in openssl 3.3.7-r2.
References
openssl-library.org/news/secadv/20260929.txt
github.com/openssl/openssl/commit/d951e02ede8f6a6ff8150546db44b34f0518192c
nvd.nist.gov/vuln/detail/CVE-2026-84782
Show 194 moreShow less
security.alpinelinux.org/vuln/CVE-2026-84782
access.redhat.com/errata/RHSA-2026:76918
bugzilla.redhat.com/2537080
errata.almalinux.org/10/ALSA-2026-76918.html
docs.bell-sw.com/security/cves/CVE-2026-84782
errata.tuxcare.com/els_os/centos8.5els/CLSA-2026-1790933161.html
security-tracker.debian.org/tracker/CVE-2026-84782
advisories.mageia.org/MGASA-2026-0481.html
bugs.mageia.org/show_bug.cgi?id=36358
openwall.com/lists/oss-security/2026/09/22/7
lists.debian.org/debian-security-announce/2026/msg00444.html
ubuntu.com/security/notices/USN-8847-1
openeuler.org/zh/security/security-bulletins/detail?id=openEuler-SA-2026-4416
images.redhat.com
security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_55543.json
cve.org/CVERecord?id=CVE-2026-7383
ruby-lang.org/en/news/2026/08/27/multiple-vulnerabilities-in-resolv
errata.rockylinux.org/RLSA-2026:76918
suse.com/support/update/announcement/2026/suse-su-202624133-1
bugzilla.suse.com/1280587
Left out here: 147 references and the rest of 4 source descriptions. The JSON record has them. Left out on purpose, here and in the API, to keep responses small: 22 source records.