OpenSSL Release Announcement and Security Advisory - 27th Jan 2026
OpenSSL Announce <[email protected]> Wed, 28 Jan 2026 00:33:21 +0000
| Newsgroups | gmane.comp.encryption.openssl.announce |
|---|---|
| Message-ID | <[email protected]> |
----_NmP-1b607504ee83647a-Part_1
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
OpenSSL Release Announcement and Security Advisory - 27th Jan 2026=20
https://api.ourmailsender4.com/open/image.png?key=3D710ed089fecca3a5033a34a=
86de10e1ef0c6dab67673de9f20329c6b51ef15c65cf77baeca94ddc37976060fb5d387c5_1=
f76734a29e0b75efdc418d5169ca8ba
https://cdn1.ourmailsender4.=
com/userContent/38291/fileManager/42391/OpenSSL_DarkRed_Library.png
OpenSSL Release Announcement and Security Advisory - 27th Jan 2026
------------------------------------------------------------------
Release Announcement for OpenSSL Library 3.6.1, 3.5 5, 3.4.4, 3.3.6, 3.0.19=
, 1.1.1ze and 1.0.2zn
The OpenSSL Project team announces the release of new=
versions of our open-source toolkit for SSL/TLS.
Changes and CVEs fixed in=
3.6.1:
---CVE-2025-11187: #cve-2025-11187
- Improper validation of PBMAC1 =
parameters in PKCS#12 MAC verification.
---CVE-2025-15467: #CVE-2025-15467
- Stack buffer overflow in CMS AuthEnvelopedData parsing.
---CVE-2025-15468: #CVE-2025-15468
- NULL dereference in SSL_CIPHER_find() =
function on unknown cipher ID.
---CVE-2025-15469: #CVE-2025-15469
- =E2=80=98openssl dgst=E2=80=99 one-shot codepath silently truncates =
inputs >16MB.
---CVE-2025-66199: #CVE-2025-66199
- TLS 1.3 CompressedCertificate excessive memory allocation.
---CVE-2025-68160: #CVE-2025-68160
- Heap out-of-bounds write in =
BIO_f_linebuffer on short writes.
---CVE-2025-69418: #CVE-2025-69418
- Unauthenticated/unencrypted trailing bytes with low-level OCB function =
calls
---CVE-2025-69419: #CVE-2025-69419
- Out of bounds write in =
PKCS12_get_friendlyname() UTF-8 conversion.
---CVE-2025-69420: =
#CVE-2025-69420
- Missing ASN1_TYPE validation in TS_RESP_verify_response()=
function.
---CVE-2025-69421: #CVE-2025-69421
- NULL Pointer Dereference in=
PKCS12_item_decrypt_d2i_ex function
---CVE-2026-22795: #CVE-2026-22795
- Missing ASN1_TYPE validation in PKCS#12 parsing
---CVE-2026-22796: =
#CVE-2026-22796
- ASN1_TYPE Type Confusion in the PKCS7_digest_from_attribu=
tes() function
Changes and CVEs fixed in 3.5.5:
---CVE-2025-11187: =
#cve-2025-11187
- Improper validation of PBMAC1 parameters in PKCS#12 MAC =
verification.
---CVE-2025-15467: #CVE-2025-15467
- Stack buffer overflow in=
CMS AuthEnvelopedData parsing.
---CVE-2025-15468: #CVE-2025-15468
- NULL dereference in SSL_CIPHER_find() function on unknown cipher ID.
---CVE-2025-15469: #CVE-2025-15469
- =E2=80=98openssl dgst=E2=80=99 =
one-shot codepath silently truncates inputs >16MB.
---CVE-2025-66199: #CVE-2025-66199
- TLS 1.3 CompressedCertificate =
excessive memory allocation.
---CVE-2025-68160: #CVE-2025-68160
- Heap out-of-bounds write in BIO_f_linebuffer on short writes.
---CVE-2025-69418: #CVE-2025-69418
- Unauthenticated/unencrypted trailing =
bytes with low-level OCB function calls
---CVE-2025-69419: #CVE-2025-69419
- Out of bounds write in PKCS12_get_friendlyname() UTF-8 conversion.
---CVE-2025-69420: #CVE-2025-69420
- Missing ASN1_TYPE validation in =
TS_RESP_verify_response() function.
---CVE-2025-69421: #CVE-2025-69421
- NULL Pointer Dereference in PKCS12_item_decrypt_d2i_ex function
---CVE-2026-22795: #CVE-2026-22795
- Missing ASN1_TYPE validation in =
PKCS#12 parsing
---CVE-2026-22796: #CVE-2026-22796
- ASN1_TYPE Type =
Confusion in the PKCS7_digest_from_attributes() function
CVEs fixed in 3.4.4:
---CVE-2025-11187: #cve-2025-11187
- Improper validation of PBMAC1 parameters in PKCS#12 MAC verification.
---CVE-2025-15467: #CVE-2025-15467
- Stack buffer overflow in CMS =
AuthEnvelopedData parsing.
---CVE-2025-15468: #CVE-2025-15468
- NULL dereference in SSL_CIPHER_find() function on unknown cipher ID.
---CVE-2025-66199: #CVE-2025-66199
- TLS 1.3 CompressedCertificate =
excessive memory allocation.
---CVE-2025-68160: #CVE-2025-68160
- Heap out-of-bounds write in BIO_f_linebuffer on short writes.
---CVE-2025-69418: #CVE-2025-69418
- Unauthenticated/unencrypted trailing =
bytes with low-level OCB function calls
---CVE-2025-69419: #CVE-2025-69419
- Out of bounds write in PKCS12_get_friendlyname() UTF-8 conversion.
---CVE-2025-69420: #CVE-2025-69420
- Missing ASN1_TYPE validation in =
TS_RESP_verify_response() function.
---CVE-2025-69421: #CVE-2025-69421
- NULL Pointer Dereference in PKCS12_item_decrypt_d2i_ex function
---CVE-2026-22795: #CVE-2026-22795
- Missing ASN1_TYPE validation in =
PKCS#12 parsing
---CVE-2026-22796: #CVE-2026-22796
- ASN1_TYPE Type =
Confusion in the PKCS7_digest_from_attributes() function
CVEs fixed in 3.3.6:
---CVE-2025-15467: #CVE-2025-15467
- Stack buffer overflow in CMS AuthEnvelopedData parsing.
---CVE-2025-15468: #CVE-2025-15468
- NULL dereference in SSL_CIPHER_find() =
function on unknown cipher ID.
---CVE-2025-66199: #CVE-2025-66199
- TLS 1.3 CompressedCertificate excessive memory allocation.
---CVE-2025-68160: #CVE-2025-68160
- Heap out-of-bounds write in =
BIO_f_linebuffer on short writes.
---CVE-2025-69418: #CVE-2025-69418
- Unauthenticated/unencrypted trailing bytes with low-level OCB function =
calls
---CVE-2025-69419: #CVE-2025-69419
- Out of bounds write in =
PKCS12_get_friendlyname() UTF-8 conversion.
---CVE-2025-69420: =
#CVE-2025-69420
- Missing ASN1_TYPE validation in TS_RESP_verify_response()=
function.
---CVE-2025-69421: #CVE-2025-69421
- NULL Pointer Dereference in=
PKCS12_item_decrypt_d2i_ex function
---CVE-2026-22795: #CVE-2026-22795
- Missing ASN1_TYPE validation in PKCS#12 parsing
---CVE-2026-22796: =
#CVE-2026-22796
- ASN1_TYPE Type Confusion in the PKCS7_digest_from_attribu=
tes() function
---
CVEs fixed in 3.0.19:
---CVE-2025-15467: #CVE-2025-15467
- Stack buffer overflow in CMS AuthEnvelopedData parsing.
---CVE-2025-68160: #CVE-2025-68160
- Heap out-of-bounds write in =
BIO_f_linebuffer on short writes.
---CVE-2025-69418: #CVE-2025-69418
- Unauthenticated/unencrypted trailing bytes with low-level OCB function =
calls
---CVE-2025-69419: #CVE-2025-69419
- Out of bounds write in =
PKCS12_get_friendlyname() UTF-8 conversion.
---CVE-2025-69420: =
#CVE-2025-69420
- Missing ASN1_TYPE validation in TS_RESP_verify_response()=
function.
---CVE-2025-69421: #CVE-2025-69421
- NULL Pointer Dereference in=
PKCS12_item_decrypt_d2i_ex function
---CVE-2026-22795: #CVE-2026-22795
- Missing ASN1_TYPE validation in PKCS#12 parsing
---CVE-2026-22796: =
#CVE-2026-22796
- ASN1_TYPE Type Confusion in the PKCS7_digest_from_attribu=
tes() function
CVEs fixed in 1.1.1ze: (premium support customers only)
---CVE-2025-68160: #CVE-2025-68160
- Heap out-of-bounds write in =
BIO_f_linebuffer on short writes.
---CVE-2025-69418: #CVE-2025-69418
- Unauthenticated/unencrypted trailing bytes with low-level OCB function =
calls
---CVE-2025-69419: #CVE-2025-69419
- Out of bounds write in =
PKCS12_get_friendlyname() UTF-8 conversion.
---CVE-2025-69420: =
#CVE-2025-69420
- Missing ASN1_TYPE validation in TS_RESP_verify_response()=
function.
---CVE-2025-69421: #CVE-2025-69421
- NULL Pointer Dereference in=
PKCS12_item_decrypt_d2i_ex function
---CVE-2026-22795: #CVE-2026-22795
- Missing ASN1_TYPE validation in PKCS#12 parsing
---CVE-2026-22796: =
#CVE-2026-22796
- ASN1_TYPE Type Confusion in the PKCS7_digest_from_attribu=
tes() function
CVEs fixed in 1.0.2zn: (premium support customers only)
---CVE-2025-68160: #CVE-2025-68160
- Heap out-of-bounds write in =
BIO_f_linebuffer on short writes.
---CVE-2025-69421: #CVE-2025-69421
- NULL Pointer Dereference in PKCS12_item_decrypt_d2i_ex function
---CVE-2026-22796: #CVE-2026-22796
- ASN1_TYPE Type Confusion in the =
PKCS7_digest_from_attributes() function
All releases contain miscellaneous =
minor bug fixes. For details of the changes, refer to the release notes for=
versions 1.0.2, 1.1.1, 3.0, 3.3, 3.4, 3.5 and 3.6.
Specific notes on upgrading from previous versions are available in the =
OpenSSL Migration Guide: https://docs.openssl.org/master/man7/ossl-guide-mi=
gration/
.
OpenSSL Library 3.x is available for download at these URLs:
---https://www.openssl.org/source/: https://www.openssl.org/source/
---https://github.com/openssl/openssl/releases: https://github.=
com/openssl/openssl/releases
The distribution file names are for:
---OpenSSL Library 3.6.1 - openssl-3.6.1: https://github.=
com/openssl/openssl/releases/tag/openssl-3.6.1
---OpenSSL Library 3.5.5 - =
openssl-3.5.5: https://github.com/openssl/openssl/releases/tag/openssl-3.5.=
5
---OpenSSL Library 3.4.4 - openssl-3.4.4: https://github.=
com/openssl/openssl/releases/tag/openssl-3.4.4
---OpenSSL Library 3.3.6 - =
openssl-3.3.6: https://github.com/openssl/openssl/releases/tag/openssl-3.3.=
6
---OpenSSL Library 3.0.19 - openssl-3.0.19: https://github.=
com/openssl/openssl/releases/tag/openssl-3.0.19
---OpenSSL Library 1.1.1ze =
- openssl-1.1.1ze: https://support.openssl.org/hc/en-us/articles/3287450153=
7682-Extended-Release-1-1-1ze
---OpenSSL Library 1.0.2zn - openssl-1.0.2zn:=
https://support.openssl.org/hc/en-us/articles/32874498766738-Extended-Rele=
ase-1-0-2zn
Security Advisory - 27th January 2026
------------------------=
---------------------
<a contenteditable=3D"false" =
name=3D"cve-2025-11187" class=3D"mce-item-anchor" style=3D"color: =
#000000;"></a>CVE-2025-11187 - Improper validation of PBMAC1 parameters in =
PKCS#12 MAC verification
Link for this security advisory: CVE-2025-11187: =
https://www.openssl.org/news/vulnerabilities.html#CVE-2025-11187
Severity: Moderate
Issue summary: PBMAC1 parameters in PKCS#12 files are =
missing validation which can trigger a stack-based buffer overflow, invalid=
pointer or NULL pointer dereference during MAC verification.
Impact summary: The stack buffer overflow or NULL pointer dereference may =
cause a crash, leading to Denial of Service for an application that parses =
untrusted PKCS#12 files. The buffer overflow may also potentially enable =
code execution depending on platform mitigations.
When verifying a PKCS#12 =
file that uses PBMAC1 for the MAC, the PBKDF2 salt and keylength parameters=
from the file are used without validation. If the value of keylength =
exceeds the size of the fixed stack buffer used for the derived key (64 =
bytes), the key derivation will overflow the buffer. The overflow length is=
attacker-controlled. Also, if the salt parameter is not an OCTET STRING =
type this can lead to invalid or NULL pointer dereference.
Exploiting this issue requires a user or application to process a =
maliciously crafted PKCS#12 file. It is uncommon to accept untrusted =
PKCS#12 files in applications as they are usually used to store private =
keys which are trusted by definition. For this reason the issue was =
assessed as Moderate severity.
The FIPS modules in 3.6, 3.5 and 3.4 are not=
affected by this issue, as PKCS#12 processing is outside the OpenSSL FIPS =
module boundary.
OpenSSL 3.6, 3.5 and 3.4 are vulnerable to this issue.
OpenSSL 3.3, 3.0, 1.1.1 and 1.0.2 are not affected by this issue as they do=
not support PBMAC1 in PKCS#12.
OpenSSL 3.6 users should upgrade to OpenSSL=
3.6.1.
OpenSSL 3.5 users should upgrade to OpenSSL 3.5.5.
OpenSSL 3.4 users should upgrade to OpenSSL 3.4.4.
This issue was reported =
on 11th September 2025 by Stanislav Fort (Aisle Research) with a follow-up =
report on 21st November 2025 by Stanislav Fort and Petr =C5=A0ime=C4=8Dek =
(Aisle Research). It was also independently reported on 14th October 2025 =
by Hamza (Metadust).
The fix was developed by Tomas Mraz.
<a contenteditable=3D"false" name=3D"CVE-2025-15467" =
class=3D"mce-item-anchor" style=3D"color: #000000;"></a>CVE-2025-15467 - =
Stack buffer overflow in CMS AuthEnvelopedData parsing
Link for this security advisory: CVE-2025-15467: https://www.openssl.=
org/news/vulnerabilities.html#CVE-2025-15467
Severity: High
Issue summary: Parsing CMS AuthEnvelopedData message with maliciously =
crafted AEAD parameters can trigger a stack buffer overflow.
Impact summary: A stack buffer overflow may lead to a crash, causing Denial=
of Service, or potentially remote code execution.
When parsing CMS =
AuthEnvelopedData structures that use AEAD ciphers such as AES-GCM, the IV =
(Initialization Vector) encoded in the ASN.1 parameters is copied into a =
fixed-size stack buffer without verifying that its length fits the =
destination. An attacker can supply a crafted CMS message with an oversized=
IV, causing a stack-based out-of-bounds write before any authentication or=
tag verification occurs.
Applications and services that parse untrusted =
CMS or PKCS#7 content using AEAD ciphers (e.g., S/MIME AuthEnvelopedData =
with AES-GCM) are vulnerable. Because the overflow occurs prior to =
authentication, no valid key material is required to trigger it. While =
exploitability to remote code execution depends on platform and toolchain =
mitigations, the stack-based write primitive represents a severe risk.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this =
issue, as the CMS implementation is outside the OpenSSL FIPS module =
boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3 and 3.0 are vulnerable to this issue.
OpenSSL 1.1.1 and 1.0.2 are not affected by this issue.
OpenSSL 3.6 users should upgrade to OpenSSL 3.6.1.
OpenSSL 3.5 users should=
upgrade to OpenSSL 3.5.5.
OpenSSL 3.4 users should upgrade to OpenSSL 3.4.=
4.
OpenSSL 3.3 users should upgrade to OpenSSL 3.3.6.
OpenSSL 3.0 users should upgrade to OpenSSL 3.0.19.
This issue was reported on 14th December 2025 by Stanislav Fort (Aisle =
Research).=20
The fix was developed by Igor Ustinov.
<a contenteditable=3D"false" name=3D"CVE-2025-15468" =
class=3D"mce-item-anchor" style=3D"color: #000000;"></a>CVE-2025-15468 - =
NULL dereference in SSL_CIPHER_find() function on unknown cipher ID
Link for this security advisory: CVE-2025-15468: https://www.openssl.=
org/news/vulnerabilities.html#CVE-2025-15468
Severity: Low
Issue summary: If an application using the SSL_CIPHER_find() function in a =
QUIC protocol client or server receives an unknown cipher suite from the =
peer, a NULL dereference occurs.
Impact summary: A NULL pointer dereference=
leads to abnormal termination of the running process causing Denial of =
Service.
Some applications call SSL_CIPHER_find() from the client_hello_cb =
callback on the cipher ID received from the peer. If this is done with an =
SSL object implementing the QUIC protocol, NULL pointer dereference will =
happen if the examined cipher ID is unknown or unsupported. As it is not =
very common to call this function in applications using the QUIC protocol =
and the worst outcome is Denial of Service, the issue was assessedas Low =
severity.
The vulnerable code was introduced in the 3.2 version with the =
addition of the QUIC protocol support.
The FIPS modules in 3.6, 3.5, 3.4 =
and 3.3 are not affected by this issue, as the QUIC implementation is =
outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4 and 3.3 are=
vulnerable to this issue.
OpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by=
this issue.
OpenSSL 3.6 users should upgrade to OpenSSL 3.6.1.
OpenSSL 3.5 users should upgrade to OpenSSL 3.5.5.
OpenSSL 3.4 users should=
upgrade to OpenSSL 3.4.4.
OpenSSL 3.3 users should upgrade to OpenSSL 3.3.=
6.
This issue was reported on 13th December 2025 by Stanislav Fort (Aisle =
Research).The fix was developed by Stanislav Fort (Aisle Research).
<a contenteditable=3D"false" name=3D"CVE-2025-15469" =
class=3D"mce-item-anchor" style=3D"color: #000000;"></a>CVE-2025-15469 - =
"openssl dgst" one-shot codepath silently truncates inputs >16MB
Link for this security advisory: CVE-2025-15469: https://www.openssl.=
org/news/vulnerabilities.html#CVE-2025-15469
Severity: Low
Issue summary: The "openssl dgst" command-line tool silently truncates =
input data to 16MB when using one-shot signing algorithms and reports =
success instead of an error.
Impact summary: A user signing or verifying =
files larger than 16MB with one-shot algorithms (such as Ed25519, Ed448, or=
ML-DSA) may believe the entire file is authenticated while trailing data =
beyond 16MB remains unauthenticated.
When the "openssl dgst" command is =
used with algorithms that only support one-shot signing (Ed25519, Ed448, =
ML-DSA-44, ML-DSA-65, ML-DSA-87), the input is buffered with a 16MB limit. =
If the input exceeds this limit, the tool silently truncates to the first =
16MB and continues without signaling an error, contrary to what the =
documentation states. This creates an integrity gap where trailing bytes =
can be modified without detection if both signing and verification are =
performed using the same affected codepath.
The issue affects only the =
command-line tool behavior. Verifiers that process the full message using =
library APIs will reject the signature, so the risk primarily affects =
workflows that both sign and verify with the affected "openssl dgst" =
command. Streaming digest algorithms for "openssl dgst" and library users =
are unaffected.
The FIPS modules in 3.5 and 3.6 are not affected by this =
issue, as the command-line tools are outside the OpenSSL FIPS module =
boundary.
OpenSSL 3.5 and 3.6 are vulnerable to this issue.
OpenSSL 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are not affected by this issue.
OpenSSL 3.6 users should upgrade to OpenSSL 3.6.1.
OpenSSL 3.5 users should=
upgrade to OpenSSL 3.5.5.
This issue was reported on 13th December 2025 by=
Stanislav Fort (Aisle Research). The fix was developed by Viktor Dukhovni.
<a contenteditable=3D"false" name=3D"CVE-2025-66199" =
class=3D"mce-item-anchor" style=3D"color: #000000;"></a>CVE-2025-66199 - =
TLS 1.3 CompressedCertificate excessive memory allocation
Link for this security advisory: CVE-2025-66199: https://www.openssl.=
org/news/vulnerabilities.html#CVE-2025-66199
Severity: Low
Issue summary: A TLS 1.3 connection using certificate compression can be =
forced to allocate a large buffer before decompression without checking =
against the configured certificate size limit.
Impact summary: An attacker =
can cause per-connection memory allocations of up to approximately 22 MiB =
and extra CPU work, potentially leading to service degradation or resource =
exhaustion (Denial of Service).
In affected configurations, the =
peer-supplied uncompressed certificate length from a CompressedCertificate =
message is used to grow a heap buffer prior to decompression. This length =
is not bounded by the max_cert_list setting, which otherwise constrains =
certificate message sizes. An attacker can exploit this to cause large =
per-connection allocations followed by handshake failure. No memory =
corruption or information disclosure occurs.
This issue only affects builds=
where TLS 1.3 certificate compression is compiled in (i.e., not =
OPENSSL_NO_COMP_ALG) and at least one compression algorithm (brotli, zlib, =
or zstd) is available, and where the compression extension is negotiated. =
Both clients receiving a server CompressedCertificateand servers in mutual =
TLS scenarios receiving a client CompressedCertificate are affected. =
Servers that do not request client certificates are not vulnerable to =
client-initiated attacks.
Users can mitigate this issue by setting =
SSL_OP_NO_RX_CERTIFICATE_COMPRESSION to disable receiving compressed =
certificates.
The FIPS modules in 3.6, 3.5, 3.4 and 3.3 are not affected by=
this issue, as the TLS implementation is outside the OpenSSL FIPS module =
boundary.
OpenSSL 3.6, 3.5, 3.4 and 3.3 are vulnerable to this issue.
OpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue.
OpenSSL 3.6 users should upgrade to OpenSSL 3.6.1.
OpenSSL 3.5 users should=
upgrade to OpenSSL 3.5.5.
OpenSSL 3.4 users should upgrade to OpenSSL 3.4.=
4.
OpenSSL 3.3 users should upgrade to OpenSSL 3.3.6.
This issue was reported on 8th November 2025 by Tomas Dulka (Aisle =
Research) and Stanislav Fort (Aisle Research). The fix was developed by =
Tomas Dulka (Aisle Research) and Stanislav Fort (Aisle Research).
<a contenteditable=3D"false" name=3D"CVE-2025-68160" =
class=3D"mce-item-anchor" style=3D"color: #000000;"></a>CVE-2025-68160 - =
Heap out-of-bounds write in BIO_f_linebuffer on short writes
Link for this security advisory: CVE-2025-68160: https://www.openssl.=
org/news/vulnerabilities.html#CVE-2025-68160
Severity: Low
Issue summary: Writing large, newline-free data into a BIO chain using the =
line-buffering filter where the next BIO performs short writes can trigger =
a heap-based out-of-bounds write.
Impact summary: This out-of-bounds write =
can cause memory corruption which typically results in a crash, leading to =
Denial of Service for an application.
The line-buffering BIO filter =
(BIO_f_linebuffer) is not used by default in TLS/SSL data paths. In OpenSSL=
command-line applications, it is typically only pushed onto stdout/stderr =
on VMS systems. Third-party applications that explicitly use this filter =
with a BIO chain that can short-write and that write large, newline-free =
data influenced by an attacker would be affected. However, the =
circumstances where this could happen are unlikely to be under attacker =
control, and BIO_f_linebuffer is unlikely to be handling non-curated data =
controlled by an attacker. For that reason the issue was assessed as Low =
severity.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected =
by this issue, as the BIO implementation is outside the OpenSSL FIPS module=
boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable =
to this issue.
OpenSSL 3.6 users should upgrade to OpenSSL 3.6.1.
OpenSSL 3.5 users should upgrade to OpenSSL 3.5.5.OpenSSL 3.4 users should =
upgrade to OpenSSL 3.4.4.
OpenSSL 3.3 users should upgrade to OpenSSL 3.3.6=
.
OpenSSL 3.0 users should upgrade to OpenSSL 3.0.19.
OpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1ze (premium support =
customers only).
OpenSSL 1.0.2 users should upgrade to OpenSSL 1.0.2zn =
(premium support customers only).
This issue was reported on 1st December =
2025 by Petr Simecek (Aisle Research) and Stanislav Fort (Aisle Research).=
=20
The fix was developed by Stanislav Fort (Aisle Research) and Neil =
Horman.
<a contenteditable=3D"false" name=3D"CVE-2025-69418" =
class=3D"mce-item-anchor" style=3D"color: #000000;"></a>CVE-2025-69418 - =
Unauthenticated/unencrypted trailing bytes with low-level OCB function =
calls
Link for this security advisory: CVE-2025-69418: https://www.openssl=
.org/news/vulnerabilities.html#CVE-2025-69418
Severity: Low
Issue summary: When using the low-level OCB API directly with AES-NI or =
other hardware-accelerated code paths, inputs whose length is not a =
multiple of 16 bytes can leave the final partial block unencrypted and =
unauthenticated.
Impact summary: The trailing 1-15 bytes of a message may =
be exposed in cleartext on encryption and are not covered by the =
authentication tag, allowing an attacker to read or tamper with those bytes=
without detection.=20
The low-level OCB encrypt and decrypt routines in =
the hardware-accelerated stream path process full 16-byte blocks but do not=
advance the input/output pointers. The subsequent tail-handling code then =
operates on the original base pointers, effectively reprocessing the =
beginning of the buffer while leaving the actual trailing bytes unprocessed=
. The authentication checksum also excludes the true tail bytes.
However, typical OpenSSL consumers using EVP are not affected because the =
higher-level EVP and provider OCB implementations split inputs so that full=
blocks and trailing partial blocks are processed in separate calls, =
avoiding the problematic code path. Additionally, TLS does not use OCB =
ciphersuites. The vulnerability only affects applications that call the =
low-level CRYPTO_ocb128_encrypt() or CRYPTO_ocb128_decrypt() functions =
directly with non-block-aligned lengths in a single call on =
hardware-accelerated builds. For these reasons, the issue was assessed as =
Low severity.
The FIPS modules in 3.6, 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are =
not affected by this issue, as OCB mode is not a FIPS-approved algorithm.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.
OpenSSL 1.0.2 is not affected by this issue.
OpenSSL 3.6 users should =
upgrade to OpenSSL 3.6.1.
OpenSSL 3.5 users should upgrade to OpenSSL 3.5.5=
.
OpenSSL 3.4 users should upgrade to OpenSSL 3.4.4.
OpenSSL 3.3 users should upgrade to OpenSSL 3.3.6.
OpenSSL 3.0 users should=
upgrade to OpenSSL 3.0.19.
OpenSSL 1.1.1 users should upgrade to OpenSSL 1=
.1.1ze. (premium support customers only).
This issue was reported on 16th =
December 2025 by Stanislav Fort (Aisle Research).
The fix was developed by =
Stanislav Fort (Aisle Research).
<a contenteditable=3D"false" =
name=3D"CVE-2025-69419" class=3D"mce-item-anchor" style=3D"color: =
#000000;"></a>CVE-2025-69419 - Out of bounds write in =
PKCS12_get_friendlyname() UTF-8 conversion
Link for this security =
advisory: CVE-2025-69419: https://www.openssl.org/news/vulnerabilities.=
html#CVE-2025-69419
Severity: Moderate
Issue summary: Calling =
PKCS12_get_friendlyname() function on a maliciously crafted PKCS#12 file =
with a BMPString (UTF-16BE) friendly name containing non-ASCII BMP code =
points can trigger a write before the allocated buffer.
Impact summary: The out-of-bounds write can cause a memory corruption which=
can have various consequences including a Denial of Service or Execution =
of attacker-supplied code.
The OPENSSL_uni2utf8() function performs a =
two-pass conversion of a PKCS#12 BMPString (UTF-16BE) to UTF-8. In the =
second pass, when emitting UTF-8 bytes, the helper function bmp_to_utf8() =
incorrectly forwards the remaining UTF-16 source byte count as the =
destination buffer capacity to UTF8_putc(). For BMP code points above =
U+07FF, UTF-8 requires three bytes, but the forwarded capacity can be just =
two bytes. UTF8_putc() then returns -1, and this negative value is added to=
the output length without validation, causing the length to become =
negative. The subsequent trailing NUL byte is then written at a negative =
offset, causing write outside of heap allocated buffer.
The vulnerability is reachable via the public PKCS12_get_friendlyname() API=
when parsing attacker-controlled PKCS#12 files. While PKCS12_parse() uses =
a different code path that avoids this issue, PKCS12_get_friendlyname() =
directly invokes the vulnerable function. Exploitation requires an attacker=
to provide a malicious PKCS#12 file to be parsed by the application. For =
that reason the issue was assessed as Moderate severity according to our =
Security Policy.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not =
affected by this issue, as the PKCS#12 implementation is outside the =
OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are=
vulnerable to this issue.
OpenSSL 1.0.2 is not affected by this issue.
OpenSSL 3.6 users should upgrade to OpenSSL 3.6.1.
OpenSSL 3.5 users should=
upgrade to OpenSSL 3.5.5.
OpenSSL 3.4 users should upgrade to OpenSSL 3.4.=
4.
OpenSSL 3.3 users should upgrade to OpenSSL 3.3.6.
OpenSSL 3.0 users should upgrade to OpenSSL 3.0.19.
OpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1ze (premium support =
customers only).
This issue was reported on 16th December 2025 by Stanislav=
Fort (Aisle Research).
The fix was developed by Norbert Pocs.
<a contenteditable=3D"false" name=3D"CVE-2025-69420" =
class=3D"mce-item-anchor" style=3D"color: #000000;"></a>CVE-2025-69420 - =
Missing ASN1_TYPE validation in TS_RESP_verify_response() function
Link for this security advisory: CVE-2025-69420: https://www.openssl.=
org/news/vulnerabilities.html#CVE-2025-69420
Severity: Low
Issue summary: A type confusion vulnerability exists in the TimeStamp =
Response verification code where an ASN1_TYPE union member is accessed =
without first validating the type, causing an invalid or NULL pointer =
dereference when processing a malformed TimeStamp Response file.
Impact summary: An application calling TS_RESP_verify_response() with a =
malformed TimeStamp Response can be caused to dereference an invalid or =
NULL pointer when reading, resulting in a Denial of Service.
The functions ossl_ess_get_signing_cert() and ossl_ess_get_signing_cert_v2(=
) access the signing cert attribute value without validating its type. When=
the type is not V_ASN1_SEQUENCE, this results in accessing invalid memory =
through the ASN1_TYPE union, causing a crash.
Exploiting this vulnerability=
requires an attacker to provide a malformed TimeStamp Response to an =
application that verifies timestamp responses. The TimeStamp protocol (RFC =
3161) is not widely used and the impact of the exploit is just a Denial of =
Service. For these reasons the issue was assessed as Low severity.
The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, =
as the TimeStamp Response implementation is outside the OpenSSL FIPS module=
boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this=
issue.
OpenSSL 1.0.2 is not affected by this issue.
OpenSSL 3.6 users should upgrade to OpenSSL 3.6.1.
OpenSSL 3.5 users should=
upgrade to OpenSSL 3.5.5.
OpenSSL 3.4 users should upgrade to OpenSSL 3.4.=
4.
OpenSSL 3.3 users should upgrade to OpenSSL 3.3.6.
OpenSSL 3.0 users should upgrade to OpenSSL 3.0.19.
OpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1zn. (premium support =
customers only).
This issue was reported on 16th December 2025 by Luigino =
Camastra (Aisle Research).
The fix was developed by Bob Beck.
<a contenteditable=3D"false" name=3D"CVE-2025-69421" =
class=3D"mce-item-anchor" style=3D"color: #000000;"></a>CVE-2025-69421 - =
NULL Pointer Dereference in PKCS12_item_decrypt_d2i_ex function
Link for this security advisory: CVE-2025-69421: https://www.openssl.=
org/news/vulnerabilities.html#CVE-2025-69421
Severity: Low
Issue summary: Processing a malformed PKCS#12 file can trigger a NULL =
pointer dereference in the PKCS12_item_decrypt_d2i_ex() function.
Impact summary: A NULL pointer dereference can trigger a crash which leads =
to Denial of Service for an application processing PKCS#12 files.
The PKCS12_item_decrypt_d2i_ex() function does not check whether the oct =
parameter is NULL before dereferencing it. When called from =
PKCS12_unpack_p7encdata() with a malformed PKCS#12 file, this parameter can=
be NULL, causing a crash. The vulnerability is limited to Denial of =
Service and cannot be escalated to achieve code execution or memory =
disclosure.
Exploiting this issue requires an attacker to provide a =
malformed PKCS#12 file to an application that processes it. For that reason=
the issue was assessed as Low severity according to our Security Policy.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this =
issue, as the PKCS#12 implementation is outside the OpenSSL FIPS module =
boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable =
to this issue.
OpenSSL 3.6 users should upgrade to OpenSSL 3.6.1.
OpenSSL 3.5 users should upgrade to OpenSSL 3.5.5.
OpenSSL 3.4 users should=
upgrade to OpenSSL 3.4.4.
OpenSSL 3.3 users should upgrade to OpenSSL 3.3.=
6.
OpenSSL 3.0 users should upgrade to OpenSSL 3.0.19.
OpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1ze (premium support =
customers only).
OpenSSL 1.0.2 users should upgrade to OpenSSL 1.0.2zn =
(premium support customers only).
This issue was reported on 21st December =
2025 by Luigino Camastra (Aisle Research).=20
The fix was developed by =
Luigino Camastra (Aisle Research).
<a contenteditable=3D"false" =
name=3D"CVE-2026-22795" class=3D"mce-item-anchor" style=3D"color: =
#000000;"></a>CVE-2026-22795 - Missing ASN1_TYPE validation in PKCS#12 =
parsing
Link for this security advisory: CVE-2026-22795: https://www.=
openssl.org/news/vulnerabilities.html#CVE-2026-22795
Severity: Low
Issue summary: An invalid or NULL pointer dereference can happen in
an application processing a malformed PKCS#12 file.
Impact summary: An application processing a malformed PKCS#12 file can be =
caused to dereference an invalid or NULL pointer on memory read, resulting =
in a Denial of Service.
A type confusion vulnerability exists in PKCS#12 =
parsing code where an ASN1_TYPE union member is accessed without first =
validating the type, causing an invalid pointer read.
The location is constrained to a 1-byte address space, meaning any =
attempted pointer manipulation can only target addresses between 0x00 and =
0xFF. This range corresponds to the zero page, which is unmapped on most =
modern operating systems and will reliably result in a crash, leading only =
to a Denial of Service. Exploiting this issue also requires a user or =
application
to process a maliciously crafted PKCS#12 file. It is uncommon =
to accept untrusted PKCS#12 files in applications as they are usually used =
to store private keys which are trusted by definition. For these reasons, =
the issue was assessed as Low severity.
The FIPS modules in 3.5, 3.4, 3.3 =
and 3.0 are not affected by this issue, as the PKCS12 implementation is =
outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 =
and 1.1.1 are vulnerable to this issue.
OpenSSL 1.0.2 is not affected by =
this issue.
OpenSSL 3.6 users should upgrade to OpenSSL 3.6.1.
OpenSSL 3.5 users should upgrade to OpenSSL 3.5.5.
OpenSSL 3.4 users should=
upgrade to OpenSSL 3.4.4.
OpenSSL 3.3 users should upgrade to OpenSSL 3.3.=
6.
OpenSSL 3.0 users should upgrade to OpenSSL 3.0.19.
OpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1ze. (premium support =
customers only).
This issue was reported on 8th January 2026 by Luigino =
Camastra (Aisle Research).
The fix was developed by Bob Beck.
<a contenteditable=3D"false" name=3D"CVE-2026-22796" =
class=3D"mce-item-anchor" style=3D"color: #000000;"></a>CVE-2026-22796 - =
ASN1_TYPE Type Confusion in the PKCS7_digest_from_attributes() function
Link for this security advisory: CVE-2026-22796: https://www.openssl.=
org/news/vulnerabilities.html#CVE-2026-22796
Severity: Low
Issue summary: A type confusion vulnerability exists in the signature =
verification of signed PKCS#7 data where an ASN1_TYPE union member is =
accessed without first validating the type, causing an invalid or NULL =
pointer dereference when processing malformed PKCS#7 data.
Impact summary: An application performing signature verification of PKCS#7 =
data or calling directly the PKCS7_digest_from_attributes() function can be=
caused to dereference an invalid or NULL pointer when reading, resulting =
in a Denial of Service.
The function PKCS7_digest_from_attributes() =
accesses the message digest attribute value without validating its type. =
When the type is not V_ASN1_OCTET_STRING, this results in accessing invalid=
memory through the ASN1_TYPE union, causing a crash.
Exploiting this vulnerability requires an attacker to provide a malformed =
signed PKCS#7 to an application that verifies it. The impact of the exploit=
is just a Denial of Service, the PKCS7 API is legacy and applications =
should be using the CMS API instead. For these reasons the issue was =
assessed as Low severity.
The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not=
affected by this issue, as the PKCS#7 parsing implementation is outside =
the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 =
and 1.0.2 are vulnerable to this issue.
OpenSSL 3.6 users should upgrade to=
OpenSSL 3.6.1.
OpenSSL 3.5 users should upgrade to OpenSSL 3.5.5.
OpenSSL 3.4 users should upgrade to OpenSSL 3.4.4.
OpenSSL 3.3 users should=
upgrade to OpenSSL 3.3.6.
OpenSSL 3.0 users should upgrade to OpenSSL 3.0.=
19.
OpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1ze. (premium support=
customers only).
OpenSSL 1.0.2 users should upgrade to OpenSSL 1.0.2zn. =
(premium support customers only).
This issue was reported on 8th January =
2026 by Luigino Camastra (Aisle Research).=20
The fix was developed by Bob =
Beck.
General Advisory Notes
URL for this Security Advisory:
https://openssl-library.org/news/secadv/20260127.txt: =
https://openssl-library.org/news/secadv/20260127.txt
Note: the online version of the advisory may be updated with additional =
details over time.
For details of OpenSSL severity classifications, please =
see:
https://openssl-library.org/policies/general/security-policy/: =
https://openssl-library.org/policies/general/security-policy/
OpenSSL Corporation: https://openssl-corporation.org
, Inc. 40 East Main Street, Newark,=20
New Castle County, 19711, USA
Unsubscribe: https://api.ourmailsender4.com/api/unsubscribe?=
key=3D710ed089fecca3a5033a34a86de10e1ef0c6dab67673de9f20329c6b51ef15c65cf77=
baeca94ddc37976060fb5d387c5_1f76734a29e0b75efdc418d5169ca8ba
| Update Profile: https://api.ourmailsender4.com/api/update?=
key=3D710ed089fecca3a5033a34a86de10e1ef0c6dab67673de9f20329c6b51ef15c65cf77=
baeca94ddc37976060fb5d387c5_1f76734a29e0b75efdc418d5169ca8ba
| Report Junk: https://api.ourmailsender4.com/api/junk?=
key=3D710ed089fecca3a5033a34a86de10e1ef0c6dab67673de9f20329c6b51ef15c65cf77=
baeca94ddc37976060fb5d387c5_1f76734a29e0b75efdc418d5169ca8ba
View this email in your browser: https://api.ourmailsender4.=
com/templatePreview?key=3D710ed089fecca3a5033a34a86de10e1ef0c6dab67673de9f2=
0329c6b51ef15c65cf77baeca94ddc37976060fb5d387c5_1f76734a29e0b75efdc418d5169=
ca8ba&html=3Dtrue
----_NmP-1b607504ee83647a-Part_1
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.=
w3.org/TR/html4/loose.dtd"><html ><head><style type=3D"text/css">=20
@font-face {
font-family: =
Inter;
src: url(https://cdn1.ourmailsender4.=
com/fonts/inter/Inter-Regular.ttf);
}
</style>
<style =
type=3D"text/css">=20
@font-face {
font-family: Play;
src: =
url(https://cdn1.ourmailsender4.com/fonts/play/Play-Regular.ttf);
}
</style>
<style type=3D"text/css">=20
=
@font-face {
font-family: Roboto;
src: url(https://cdn1.ourmailsender4.=
com/fonts/roboto/Roboto-Regular.ttf);
}
</style>
<style>a {color:#000000;=
text-decoration:underline; }
p {margin:10px 0; padding:0; }
td {border-collapse:collapse; }
body {color:#000000; width:100%; =
height:100%; margin:0; padding:0; font-size:14px; text-align:left; =
font-family:arial; font-weight:normal; letter-spacing:normal; =
background-color:#FFFFFF; }
table {border-collapse:collapse; =
mso-table-lspace:0pt; mso-table-rspace:0pt; }
h1, .mph1 {color:#000000; =
font-size:40px; font-style:normal; text-align:left; font-family:arial; =
font-weight:bold; line-height:normal; letter-spacing:normal; }
h2, .mph2 {color:#000000; font-size:30px; font-style:normal; =
text-align:left; font-family:arial; font-weight:bold; line-height:normal; =
letter-spacing:normal; }
h3, .mph3 {color:#000000; font-size:20px; =
font-style:normal; text-align:left; font-family:arial; font-weight:normal; =
line-height:normal; letter-spacing:normal; }
h4, .mph4 {color:#000000; =
font-size:14px; font-style:italic; text-align:left; font-family:arial; =
font-weight:bold; line-height:100%; letter-spacing:normal; }
.mpmFButt1 {font:arial; color:#FFFFFF; font-size:14px; border-radius:3px; =
background-color:#000000; }
img, a img {border:none; outline:none; =
text-decoration:none; -ms-text-size-adjust:100%; mso-line-height-rule:exact=
ly; -ms-interpolation-mode:bicubic; -webkit-text-size-adjust:100%; }
.hideInEmail {display:none; mso-hide:all; }
p, a, li, td, blockquote =
{mso-line-height-rule:exactly; }
a[href^=3Dtel], [href^=3Dsms] =
{color:inherit; cursor:default; text-decoration:none; }
a[x-apple-data-detectors] {color:inherit!important; font-size:inherit !=
important; font-family:inherit !important; font-weight:inherit !important; =
line-height:inherit !important; text-decoration:none !important; }
@media screen and (max-width: 640px) {.mobile-hide {display: none !=
important; hide-mso: all !important; }
.desktop-hide {display: revert !=
important; mso-hide: all !important; }
.responsiveTd {width: 100% !=
important; border: none !important; display: block !important; padding: 0px=
!important; max-width: 100% !important; min-width: 100% !important; =
padding-left: 0px !important; padding-right: 0px !important; }
.responsiveTbl {width: 100% !important; border: none !important; min-width:=
100% !important; }
.mobiledesktop-hide {display: none !important; =
mso-hide: all; }
}
@media screen and (min-width: 641px) {.mobile-hide =
{display: revert !important; mso-hide: none !important; }
.desktop-hide {height: auto !important; display: none !important; overflow:=
visible !important; }
.mobiledesktop-hide {display: none !important; =
mso-hide: all; }
}
p, a, li, td, body, table, blockquote =
{-ms-text-size-adjust:100%; -webkit-text-size-adjust:100%; }
h1, h2, h3, h4, h5, h6, .mph1, .mph2, .mph3, .mph4 {margin:0; =
display:block; padding:0; }
</style><title></title><meta name=3D"viewport" =
content=3D"width=3Ddevice-width, initial-scale=3D1, =
maximum-scale=3D1"/></head><body><div style=3D"display:none; =
max-height:0px; overflow:hidden; font-size:0px; line-height:0px; =
color:transparent; opacity:0; visibility:hidden; mso-hide:all;">
OpenSSL Release Announcement and Security Advisory - 27th Jan 2026
<div id=3D"preheaderpad" style=3D"display:none; max-height:0px; =
overflow:hidden; font-size:0px; line-height:0px; color:tran#sparent; =
opacity:0; visibility:hidden; mso-hide:all;"> =E2=80=8C =E2=80=8C=
=E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C=
=E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C=
=E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C=
=E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C=
=E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C=
=E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C=
=E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C=
=E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C=
=E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C=
=E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C=
=E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C=
=E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C=
=E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C=
=E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C=
=E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C=
=E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C=
=E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C=
=E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C=
=E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C=
=E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C=
=E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C=
=E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C=
=E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C=
=E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C=
=E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C=
=E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C=
=E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C=
=E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C=
=E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C=
=E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C=
=E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C=
=E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C=
=E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C=
=E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C=
=E2=80=8C =E2=80=8C =E2=80=8C</div>
</div>
<div style=3D"height: 0;"><img src=3D"https://api.ourmailsender4.=
com/open/image.png?key=3D710ed089fecca3a5033a34a86de10e1ef0c6dab67673de9f20=
329c6b51ef15c65cf77baeca94ddc37976060fb5d387c5_1f76734a29e0b75efdc418d5169c=
a8ba" href=3D"https://api.ourmailsender4.com/openclick" title=3D"" alt=3D""=
/></div><table width=3D"100%" cellspacing=3D"0" cellpadding=3D"0" =
class=3D"templateBody" style=3D"width: 100%; height: 100%; margin: 0; =
padding-top: 20px; padding-left: 0px; padding-right: 0px; padding-bottom: =
20px; -ms-text-size-adjust: 100%; -webkit-text-size-adjust: 100%; " =
bgColor=3D"#FFFFFF"><tr><td valign=3D"top"><table align=3D"center" =
style=3D"width: 100%; margin: 0; max-width: 100%; " width=3D"100%" =
cellPadding=3D"0" cellSpacing=3D"0"><tr><td style=3D"padding-top: 20px; =
padding-left: 0px; padding-right: 0px; padding-bottom: 20px; =
background-color: #FFFFFF; -ms-text-size-adjust: 100%; =
-webkit-text-size-adjust: 100%; " valign=3D"top"><table align=3D"center" =
class=3D"" style=3D"margin: 0 auto; max-width: 100%; min-width: 100%; " =
width=3D"100%" cellPadding=3D"0" cellSpacing=3D"0"><tr><td align=3D"center"=
style=3D"padding-top: 0px; padding-left: 0px; padding-right: 0px; =
padding-bottom: 0px; background-size: cover; background-color: #f4f4f4; =
background-image: url(); background-repeat: repeat; background-position: =
center; " width=3D"100%" valign=3D"top"><table align=3D"center" =
class=3D"responsiveTbl" width=3D"600" cellPadding=3D"0" =
cellSpacing=3D"0"><tr><td class=3D"responsiveTd" style=3D"max-width: 100%; =
padding-top: 15px; border-style: none; border-width: 1px; padding-left: =
15px; padding-right: 15px; padding-bottom: 0px; background-size: cover; =
background-color: #ffffff; background-image: url(); background-repeat: =
repeat; background-position: center; " width=3D"100%" valign=3D"top"><table=
align=3D"center" class=3D"" style=3D"max-width: 100%; min-width: 100%; " =
width=3D"100%" cellPadding=3D"0" cellSpacing=3D"0"><tr><td =
style=3D"padding-top: 0px; padding-left: 0px; padding-right: 0px; =
padding-bottom: 20px; " width=3D"100%" valign=3D"undefined"><table =
align=3D"left" style=3D"border-collapse: collapse; mso-table-lspace: 0pt; =
mso-table-rspace: 0pt; -ms-text-size-adjust: 100%; -webkit-text-size-adjust=
: 100%; " width=3D"40%" cellPadding=3D"0" cellSpacing=3D"0"><tr><td =
style=3D"-ms-text-size-adjust: 100%; mso-line-height-rule: exactly; =
-webkit-text-size-adjust: 100%; "><img alt=3D"" src=3D"https://cdn1.=
ourmailsender4.com/userContent/38291/fileManager/42391/OpenSSL_DarkRed_Libr=
ary.png" style=3D"border: 0; height: auto !important; margin: 0; display: =
block !important; outline: none; padding: 0; border-radius: 0; =
padding-bottom: 0; vertical-align: bottom; text-decoration: none; =
-ms-interpolation-mode: bicubic; max-width: 100%; min-width: 100%; " =
title=3D"" width=3D"228" data-custom=3D""/></td></tr></table></td></tr></ta=
ble><table align=3D"center" class=3D"" style=3D"max-width: 100%; min-width:=
100%; " width=3D"100%" cellPadding=3D"0" cellSpacing=3D"0"><tr><td =
style=3D"padding-top: 0; padding-left: 0; padding-right: 0; padding-bottom:=
0; " width=3D"100%"><table align=3D"center" style=3D"max-width: 100%; " =
width=3D"100%" cellPadding=3D"0" cellSpacing=3D"0"><tr><td =
style=3D"padding-top: 20px; border-width: 0; padding-left: 0px; =
padding-right: 0px; padding-bottom: 10px; background-color: transparent; " =
width=3D"100%"><div style=3D"color: #000000; position: relative; font-size:=
14px; textAlign: left; word-break: break-word; font-family: arial; =
font-weight: normal; mso-line-height-rule: exactly; line-height: =
normal;letter-spacing: normal; "><h2><span style=3D"font-family: Roboto, =
sans-serif;" data-mce-style=3D"font-family: Roboto, sans-serif;">OpenSSL =
Release Announcement and Security Advisory - 27th Jan =
2026</span></h2><p><span style=3D"font-family: Roboto, sans-serif;" =
data-mce-style=3D"font-family: Roboto, sans-serif;"> </span>Release =
Announcement for OpenSSL Library <strong>3.6.1</strong>, <strong>3.5 =
5</strong>, <strong>3.4.4</strong>, <strong>3.3.6</strong>, <strong>3.0.=
19</strong>, <strong>1.1.1ze</strong> and <strong>1.0.=
2zn</strong></p><p>The OpenSSL Project team announces the release of new =
versions of our open-source toolkit for SSL/TLS.</p><p>Changes and CVEs =
fixed in 3.6.1:</p><ul><li><a href=3D"#cve-2025-11187" target=3D"_self" =
data-mce-href=3D"#cve-2025-11187" style=3D"color: #000000;">CVE-2025-11187<=
/a> - Improper validation of PBMAC1 parameters in PKCS#12 MAC verification.=
</li><li><a href=3D"#CVE-2025-15467" target=3D"_self" =
data-mce-href=3D"#CVE-2025-15467" style=3D"color: #000000;">CVE-2025-15467<=
/a> - Stack buffer overflow in CMS AuthEnvelopedData parsing.</li><li><a =
href=3D"#CVE-2025-15468" target=3D"_self" data-mce-href=3D"#CVE-2025-15468"=
style=3D"color: #000000;">CVE-2025-15468</a> - NULL dereference in =
SSL_CIPHER_find() function on unknown cipher ID.</li><li><a =
href=3D"#CVE-2025-15469" target=3D"_self" data-mce-href=3D"#CVE-2025-15469"=
style=3D"color: #000000;">CVE-2025-15469</a> - =E2=80=98openssl =
dgst=E2=80=99 one-shot codepath silently truncates inputs >16MB.=
</li><li><a href=3D"#CVE-2025-66199" target=3D"_self" =
data-mce-href=3D"#CVE-2025-66199" style=3D"color: #000000;">CVE-2025-66199<=
/a> - TLS 1.3 CompressedCertificate excessive memory allocation.</li><li><a=
href=3D"#CVE-2025-68160" target=3D"_self" data-mce-href=3D"#CVE-2025-68160=
" style=3D"color: #000000;">CVE-2025-68160</a> - Heap out-of-bounds write =
in BIO_f_linebuffer on short writes.</li><li><a href=3D"#CVE-2025-69418" =
target=3D"_self" data-mce-href=3D"#CVE-2025-69418" style=3D"color: =
#000000;">CVE-2025-69418</a> - Unauthenticated/unencrypted trailing bytes =
with low-level OCB function calls</li><li><a href=3D"#CVE-2025-69419" =
target=3D"_self" data-mce-href=3D"#CVE-2025-69419" style=3D"color: =
#000000;">CVE-2025-69419</a> - Out of bounds write in =
PKCS12_get_friendlyname() UTF-8 conversion.</li><li><a =
href=3D"#CVE-2025-69420" target=3D"_self" data-mce-href=3D"#CVE-2025-69420"=
style=3D"color: #000000;">CVE-2025-69420</a> - Missing ASN1_TYPE =
validation in TS_RESP_verify_response() function.</li><li><a =
href=3D"#CVE-2025-69421" target=3D"_self" data-mce-href=3D"#CVE-2025-69421"=
style=3D"color: #000000;">CVE-2025-69421</a> - NULL Pointer Dereference in=
PKCS12_item_decrypt_d2i_ex function</li><li><a href=3D"#CVE-2026-22795" =
target=3D"_self" data-mce-href=3D"#CVE-2026-22795" style=3D"color: =
#000000;">CVE-2026-22795</a> - Missing ASN1_TYPE validation in PKCS#12 =
parsing</li><li><a href=3D"#CVE-2026-22796" target=3D"_self" =
data-mce-href=3D"#CVE-2026-22796" style=3D"color: #000000;">CVE-2026-22796<=
/a> - ASN1_TYPE Type Confusion in the PKCS7_digest_from_attributes() =
function</li></ul><p>Changes and CVEs fixed in 3.5.5:</p><ul><li><a =
href=3D"#cve-2025-11187" target=3D"_self" data-mce-href=3D"#cve-2025-11187"=
style=3D"color: #000000;">CVE-2025-11187</a> - Improper validation of =
PBMAC1 parameters in PKCS#12 MAC verification.</li><li><a =
href=3D"#CVE-2025-15467" target=3D"_self" data-mce-href=3D"#CVE-2025-15467"=
style=3D"color: #000000;">CVE-2025-15467</a> - Stack buffer overflow in =
CMS AuthEnvelopedData parsing.</li><li><a href=3D"#CVE-2025-15468" =
target=3D"_self" data-mce-href=3D"#CVE-2025-15468" style=3D"color: =
#000000;">CVE-2025-15468</a> - NULL dereference in SSL_CIPHER_find() =
function on unknown cipher ID.</li><li><a href=3D"#CVE-2025-15469" =
target=3D"_self" data-mce-href=3D"#CVE-2025-15469" style=3D"color: =
#000000;">CVE-2025-15469</a> - =E2=80=98openssl dgst=E2=80=99 one-shot =
codepath silently truncates inputs >16MB.</li><li><a =
href=3D"#CVE-2025-66199" target=3D"_self" data-mce-href=3D"#CVE-2025-66199"=
style=3D"color: #000000;">CVE-2025-66199</a> - TLS 1.3 =
CompressedCertificate excessive memory allocation.</li><li><a =
href=3D"#CVE-2025-68160" target=3D"_self" data-mce-href=3D"#CVE-2025-68160"=
style=3D"color: #000000;">CVE-2025-68160</a> - Heap out-of-bounds write in=
BIO_f_linebuffer on short writes.</li><li><a href=3D"#CVE-2025-69418" =
target=3D"_self" data-mce-href=3D"#CVE-2025-69418" style=3D"color: =
#000000;">CVE-2025-69418</a> - Unauthenticated/unencrypted trailing bytes =
with low-level OCB function calls</li><li><a href=3D"#CVE-2025-69419" =
target=3D"_self" data-mce-href=3D"#CVE-2025-69419" style=3D"color: =
#000000;">CVE-2025-69419</a> - Out of bounds write in =
PKCS12_get_friendlyname() UTF-8 conversion.</li><li><a =
href=3D"#CVE-2025-69420" target=3D"_self" data-mce-href=3D"#CVE-2025-69420"=
style=3D"color: #000000;">CVE-2025-69420</a> - Missing ASN1_TYPE =
validation in TS_RESP_verify_response() function.</li><li><a =
href=3D"#CVE-2025-69421" target=3D"_self" data-mce-href=3D"#CVE-2025-69421"=
style=3D"color: #000000;">CVE-2025-69421</a> - NULL Pointer Dereference in=
PKCS12_item_decrypt_d2i_ex function</li><li><a href=3D"#CVE-2026-22795" =
target=3D"_self" data-mce-href=3D"#CVE-2026-22795" style=3D"color: =
#000000;">CVE-2026-22795</a> - Missing ASN1_TYPE validation in PKCS#12 =
parsing</li><li><a href=3D"#CVE-2026-22796" target=3D"_self" =
data-mce-href=3D"#CVE-2026-22796" style=3D"color: #000000;">CVE-2026-22796<=
/a> - ASN1_TYPE Type Confusion in the PKCS7_digest_from_attributes() =
function</li></ul><p>CVEs fixed in 3.4.4:</p><ul><li><a =
href=3D"#cve-2025-11187" target=3D"_self" data-mce-href=3D"#cve-2025-11187"=
style=3D"color: #000000;">CVE-2025-11187</a> - Improper validation of =
PBMAC1 parameters in PKCS#12 MAC verification.</li><li><a =
href=3D"#CVE-2025-15467" target=3D"_self" data-mce-href=3D"#CVE-2025-15467"=
style=3D"color: #000000;">CVE-2025-15467</a> - Stack buffer overflow in =
CMS AuthEnvelopedData parsing.</li><li><a href=3D"#CVE-2025-15468" =
target=3D"_self" data-mce-href=3D"#CVE-2025-15468" style=3D"color: =
#000000;">CVE-2025-15468</a> - NULL dereference in SSL_CIPHER_find() =
function on unknown cipher ID.</li><li><a href=3D"#CVE-2025-66199" =
target=3D"_self" data-mce-href=3D"#CVE-2025-66199" style=3D"color: =
#000000;">CVE-2025-66199</a> - TLS 1.3 CompressedCertificate excessive =
memory allocation.</li><li><a href=3D"#CVE-2025-68160" target=3D"_self" =
data-mce-href=3D"#CVE-2025-68160" style=3D"color: #000000;">CVE-2025-68160<=
/a> - Heap out-of-bounds write in BIO_f_linebuffer on short writes.=
</li><li><a href=3D"#CVE-2025-69418" target=3D"_self" =
data-mce-href=3D"#CVE-2025-69418" style=3D"color: #000000;">CVE-2025-69418<=
/a> - Unauthenticated/unencrypted trailing bytes with low-level OCB =
function calls</li><li><a href=3D"#CVE-2025-69419" target=3D"_self" =
data-mce-href=3D"#CVE-2025-69419" style=3D"color: #000000;">CVE-2025-69419<=
/a> - Out of bounds write in PKCS12_get_friendlyname() UTF-8 conversion.=
</li><li><a href=3D"#CVE-2025-69420" target=3D"_self" =
data-mce-href=3D"#CVE-2025-69420" style=3D"color: #000000;">CVE-2025-69420<=
/a> - Missing ASN1_TYPE validation in TS_RESP_verify_response() function.=
</li><li><a href=3D"#CVE-2025-69421" target=3D"_self" =
data-mce-href=3D"#CVE-2025-69421" style=3D"color: #000000;">CVE-2025-69421<=
/a> - NULL Pointer Dereference in PKCS12_item_decrypt_d2i_ex =
function</li><li><a href=3D"#CVE-2026-22795" target=3D"_self" =
data-mce-href=3D"#CVE-2026-22795" style=3D"color: #000000;">CVE-2026-22795<=
/a> - Missing ASN1_TYPE validation in PKCS#12 parsing</li><li><a =
href=3D"#CVE-2026-22796" target=3D"_self" data-mce-href=3D"#CVE-2026-22796"=
style=3D"color: #000000;">CVE-2026-22796</a> - ASN1_TYPE Type Confusion in=
the PKCS7_digest_from_attributes() function</li></ul><p>CVEs fixed in 3.3.=
6:</p><ul><li><a href=3D"#CVE-2025-15467" target=3D"_self" =
data-mce-href=3D"#CVE-2025-15467" style=3D"color: #000000;">CVE-2025-15467<=
/a> - Stack buffer overflow in CMS AuthEnvelopedData parsing.</li><li><a =
href=3D"#CVE-2025-15468" target=3D"_self" data-mce-href=3D"#CVE-2025-15468"=
style=3D"color: #000000;">CVE-2025-15468</a> - NULL dereference in =
SSL_CIPHER_find() function on unknown cipher ID.</li><li><a =
href=3D"#CVE-2025-66199" target=3D"_self" data-mce-href=3D"#CVE-2025-66199"=
style=3D"color: #000000;">CVE-2025-66199</a> - TLS 1.3 =
CompressedCertificate excessive memory allocation.</li><li><a =
href=3D"#CVE-2025-68160" target=3D"_self" data-mce-href=3D"#CVE-2025-68160"=
style=3D"color: #000000;">CVE-2025-68160</a> - Heap out-of-bounds write in=
BIO_f_linebuffer on short writes.</li><li><a href=3D"#CVE-2025-69418" =
target=3D"_self" data-mce-href=3D"#CVE-2025-69418" style=3D"color: =
#000000;">CVE-2025-69418</a> - Unauthenticated/unencrypted trailing bytes =
with low-level OCB function calls</li><li><a href=3D"#CVE-2025-69419" =
target=3D"_self" data-mce-href=3D"#CVE-2025-69419" style=3D"color: =
#000000;">CVE-2025-69419</a> - Out of bounds write in =
PKCS12_get_friendlyname() UTF-8 conversion.</li><li><a =
href=3D"#CVE-2025-69420" target=3D"_self" data-mce-href=3D"#CVE-2025-69420"=
style=3D"color: #000000;">CVE-2025-69420</a> - Missing ASN1_TYPE =
validation in TS_RESP_verify_response() function.</li><li><a =
href=3D"#CVE-2025-69421" target=3D"_self" data-mce-href=3D"#CVE-2025-69421"=
style=3D"color: #000000;">CVE-2025-69421</a> - NULL Pointer Dereference in=
PKCS12_item_decrypt_d2i_ex function</li><li><a href=3D"#CVE-2026-22795" =
target=3D"_self" data-mce-href=3D"#CVE-2026-22795" style=3D"color: =
#000000;">CVE-2026-22795</a> - Missing ASN1_TYPE validation in PKCS#12 =
parsing</li><li><a href=3D"#CVE-2026-22796" target=3D"_self" =
data-mce-href=3D"#CVE-2026-22796" style=3D"color: #000000;">CVE-2026-22796<=
/a> - ASN1_TYPE Type Confusion in the PKCS7_digest_from_attributes() =
function</li><li><br></li></ul><p>CVEs fixed in 3.0.19:</p><ul><li><a =
href=3D"#CVE-2025-15467" target=3D"_self" data-mce-href=3D"#CVE-2025-15467"=
style=3D"color: #000000;">CVE-2025-15467</a> - Stack buffer overflow in =
CMS AuthEnvelopedData parsing.</li><li><a href=3D"#CVE-2025-68160" =
target=3D"_self" data-mce-href=3D"#CVE-2025-68160" style=3D"color: =
#000000;">CVE-2025-68160</a> - Heap out-of-bounds write in BIO_f_linebuffer=
on short writes.</li><li><a href=3D"#CVE-2025-69418" target=3D"_self" =
data-mce-href=3D"#CVE-2025-69418" style=3D"color: #000000;">CVE-2025-69418<=
/a> - Unauthenticated/unencrypted trailing bytes with low-level OCB =
function calls</li><li><a href=3D"#CVE-2025-69419" target=3D"_self" =
data-mce-href=3D"#CVE-2025-69419" style=3D"color: #000000;">CVE-2025-69419<=
/a> - Out of bounds write in PKCS12_get_friendlyname() UTF-8 conversion.=
</li><li><a href=3D"#CVE-2025-69420" target=3D"_self" =
data-mce-href=3D"#CVE-2025-69420" style=3D"color: #000000;">CVE-2025-69420<=
/a> - Missing ASN1_TYPE validation in TS_RESP_verify_response() function.=
</li><li><a href=3D"#CVE-2025-69421" target=3D"_self" =
data-mce-href=3D"#CVE-2025-69421" style=3D"color: #000000;">CVE-2025-69421<=
/a> - NULL Pointer Dereference in PKCS12_item_decrypt_d2i_ex =
function</li><li><a href=3D"#CVE-2026-22795" target=3D"_self" =
data-mce-href=3D"#CVE-2026-22795" style=3D"color: #000000;">CVE-2026-22795<=
/a> - Missing ASN1_TYPE validation in PKCS#12 parsing</li><li><a =
href=3D"#CVE-2026-22796" target=3D"_self" data-mce-href=3D"#CVE-2026-22796"=
style=3D"color: #000000;">CVE-2026-22796</a> - ASN1_TYPE Type Confusion in=
the PKCS7_digest_from_attributes() function</li></ul><p>CVEs fixed in 1.1.=
1ze: <em>(premium support customers only)</em></p><ul><li><a =
href=3D"#CVE-2025-68160" target=3D"_self" data-mce-href=3D"#CVE-2025-68160"=
style=3D"color: #000000;">CVE-2025-68160</a> - Heap out-of-bounds write in=
BIO_f_linebuffer on short writes.</li><li><a href=3D"#CVE-2025-69418" =
target=3D"_self" data-mce-href=3D"#CVE-2025-69418" style=3D"color: =
#000000;">CVE-2025-69418</a> - Unauthenticated/unencrypted trailing bytes =
with low-level OCB function calls</li><li><a href=3D"#CVE-2025-69419" =
target=3D"_self" data-mce-href=3D"#CVE-2025-69419" style=3D"color: =
#000000;">CVE-2025-69419</a> - Out of bounds write in =
PKCS12_get_friendlyname() UTF-8 conversion.</li><li><a =
href=3D"#CVE-2025-69420" target=3D"_self" data-mce-href=3D"#CVE-2025-69420"=
style=3D"color: #000000;">CVE-2025-69420</a> - Missing ASN1_TYPE =
validation in TS_RESP_verify_response() function.</li><li><a =
href=3D"#CVE-2025-69421" target=3D"_self" data-mce-href=3D"#CVE-2025-69421"=
style=3D"color: #000000;">CVE-2025-69421</a> - NULL Pointer Dereference in=
PKCS12_item_decrypt_d2i_ex function</li><li><a href=3D"#CVE-2026-22795" =
target=3D"_self" data-mce-href=3D"#CVE-2026-22795" style=3D"color: =
#000000;">CVE-2026-22795</a> - Missing ASN1_TYPE validation in PKCS#12 =
parsing</li><li><a href=3D"#CVE-2026-22796" target=3D"_self" =
data-mce-href=3D"#CVE-2026-22796" style=3D"color: #000000;">CVE-2026-22796<=
/a> - ASN1_TYPE Type Confusion in the PKCS7_digest_from_attributes() =
function</li></ul><p>CVEs fixed in 1.0.2zn: <em>(premium support customers =
only)</em></p><ul><li><a href=3D"#CVE-2025-68160" target=3D"_self" =
data-mce-href=3D"#CVE-2025-68160" style=3D"color: #000000;">CVE-2025-68160<=
/a> - Heap out-of-bounds write in BIO_f_linebuffer on short writes.=
</li><li><a href=3D"#CVE-2025-69421" target=3D"_self" =
data-mce-href=3D"#CVE-2025-69421" style=3D"color: #000000;">CVE-2025-69421<=
/a> - NULL Pointer Dereference in PKCS12_item_decrypt_d2i_ex =
function</li><li><a href=3D"#CVE-2026-22796" target=3D"_self" =
data-mce-href=3D"#CVE-2026-22796" style=3D"color: #000000;">CVE-2026-22796<=
/a> - ASN1_TYPE Type Confusion in the PKCS7_digest_from_attributes() =
function</li></ul><p>All releases contain miscellaneous minor bug fixes. =
For details of the changes, refer to the release notes for versions 1.0.2, =
1.1.1, 3.0, 3.3, 3.4, 3.5 and 3.6.</p><p>Specific notes on upgrading from =
previous versions are available in the <a href=3D"https://api.=
ourmailsender4.com/c/9cc3d3e04ce4e0e6905ea3b74f9102de_bc1df5d4c4dadc31f844c=
dc9e76b51ea?sid=3D9df465b02c94538ace6e1dbdac2fe500_bb75162114c0cdc6931c4430=
f84ff78f&aid=3DXp2h" data-mce-href=3D"https://docs.openssl.=
org/master/man7/ossl-guide-migration/" style=3D"color: #000000;">OpenSSL =
Migration Guide</a>.</p><p>OpenSSL Library 3.x is available for download at=
these URLs:</p><ul><li><a href=3D"https://api.ourmailsender4.=
com/c/08d76d662e29ff866e473114a3bad23a_1698fc2e4124f4e2b4e00bd71f146103?=
sid=3D9df465b02c94538ace6e1dbdac2fe500_bb75162114c0cdc6931c4430f84ff78f&aid=
=3DXp2h" data-mce-href=3D"https://www.openssl.org/source/" style=3D"color: =
#000000;">https://www.openssl.org/source/</a></li><li><a =
href=3D"https://api.ourmailsender4.com/c/bb8d4229e3d918139016d796a79b922c_2=
49bd45bc3e64634b9fa1a47316267fa?sid=3D9df465b02c94538ace6e1dbdac2fe500_bb75=
162114c0cdc6931c4430f84ff78f&aid=3DXp2h" data-mce-href=3D"https://github.=
com/openssl/openssl/releases" style=3D"color: #000000;">https://github.=
com/openssl/openssl/releases</a></li></ul><p>The distribution file names =
are for:</p><ul><li>OpenSSL Library 3.6.1 - <a href=3D"https://api.=
ourmailsender4.com/c/6d98f2dcb7fc2fde20070d5625882c6e_4c1cb9b2ecf831de00e54=
bd080affab1?sid=3D9df465b02c94538ace6e1dbdac2fe500_bb75162114c0cdc6931c4430=
f84ff78f&aid=3DXp2h" data-mce-href=3D"https://github.=
com/openssl/openssl/releases/tag/openssl-3.6.1" style=3D"color: =
#000000;">openssl-3.6.1</a></li><li>OpenSSL Library 3.5.5 - <a =
href=3D"https://api.ourmailsender4.com/c/cf4acffa28c318bd38747cc4db5ef2d7_6=
dbcf086ee62cbb0c6b2ba10e1fd8e23?sid=3D9df465b02c94538ace6e1dbdac2fe500_bb75=
162114c0cdc6931c4430f84ff78f&aid=3DXp2h" data-mce-href=3D"https://github.=
com/openssl/openssl/releases/tag/openssl-3.5.5" style=3D"color: =
#000000;">openssl-3.5.5</a></li><li>OpenSSL Library 3.4.4 - <a =
href=3D"https://api.ourmailsender4.com/c/c5fb3bc71e13dfa859faa4341d73ecf9_6=
1def728dd9331f5fabdbf43162938fd?sid=3D9df465b02c94538ace6e1dbdac2fe500_bb75=
162114c0cdc6931c4430f84ff78f&aid=3DXp2h" data-mce-href=3D"https://github.=
com/openssl/openssl/releases/tag/openssl-3.4.4" style=3D"color: =
#000000;">openssl-3.4.4</a></li><li>OpenSSL Library 3.3.6 - <a =
href=3D"https://api.ourmailsender4.com/c/3ca7a785a87f0a6ff4c0a3eaf9126e8b_6=
ade310764eae7aaafdde7fd6c55d58e?sid=3D9df465b02c94538ace6e1dbdac2fe500_bb75=
162114c0cdc6931c4430f84ff78f&aid=3DXp2h" data-mce-href=3D"https://github.=
com/openssl/openssl/releases/tag/openssl-3.3.6" style=3D"color: =
#000000;">openssl-3.3.6</a></li><li>OpenSSL Library 3.0.19 - <a =
href=3D"https://api.ourmailsender4.com/c/5f67c308e0721d447d62bde2a2e45ff6_d=
c52f6024f01c6e392df6803602d9ffc?sid=3D9df465b02c94538ace6e1dbdac2fe500_bb75=
162114c0cdc6931c4430f84ff78f&aid=3DXp2h" data-mce-href=3D"https://github.=
com/openssl/openssl/releases/tag/openssl-3.0.19" style=3D"color: =
#000000;">openssl-3.0.19</a></li><li>OpenSSL Library 1.1.1ze - <a =
href=3D"https://api.ourmailsender4.com/c/b5839d85814eb078a38683e48d1c04c5_6=
4334f36313c88622bc98a8234d77cae?sid=3D9df465b02c94538ace6e1dbdac2fe500_bb75=
162114c0cdc6931c4430f84ff78f&aid=3DXp2h" data-mce-href=3D"https://support.=
openssl.org/hc/en-us/articles/32874501537682-Extended-Release-1-1-1ze" =
style=3D"color: #000000;">openssl-1.1.1ze</a></li><li>OpenSSL Library 1.0.=
2zn - <a href=3D"https://api.ourmailsender4.com/c/6d871cf967056afe53b9ceda4=
d2a3189_8a884ddac9a212693f3b22daf72ec515?sid=3D9df465b02c94538ace6e1dbdac2f=
e500_bb75162114c0cdc6931c4430f84ff78f&aid=3DXp2h" data-mce-href=3D"https://=
support.openssl.org/hc/en-us/articles/32874498766738-Extended-Release-1-0-2=
zn" style=3D"color: #000000;">openssl-1.0.2zn</a></li></ul><hr><h2><span =
style=3D"font-family: Roboto, sans-serif;" data-mce-style=3D"font-family: =
Roboto, sans-serif;">Security Advisory - 27th January =
2026<br><br></span></h2><h3><a contenteditable=3D"false" =
name=3D"cve-2025-11187" class=3D"mce-item-anchor" style=3D"color: =
#000000;"></a><strong><span style=3D"text-decoration: underline;" =
data-mce-style=3D"text-decoration: underline;">CVE-2025-11187 - Improper =
validation of PBMAC1 parameters in PKCS#12 MAC verification</span></strong>=
</h3><p><strong><em>Link for this security advisory: </em><a =
href=3D"https://api.ourmailsender4.com/c/b443b6121dc8606af0c80a5eecee5e0d_2=
6ce66a875eff71caf700d22e348e80f?sid=3D9df465b02c94538ace6e1dbdac2fe500_bb75=
162114c0cdc6931c4430f84ff78f&aid=3DXp2h" target=3D"_blank" rel=3D"noopener"=
data-mce-href=3D"https://www.openssl.org/news/vulnerabilities.=
html#CVE-2025-11187" style=3D"color: #000000;">CVE-2025-11187</a><br><br>Se=
verity</strong>: Moderate</p><p><strong>Issue summary</strong>: PBMAC1 =
parameters in PKCS#12 files are missing validation which can trigger a =
stack-based buffer overflow, invalid pointer or NULL pointer dereference =
during MAC verification.</p><p><strong>Impact summary</strong>: The stack =
buffer overflow or NULL pointer dereference may cause a crash, leading to =
Denial of Service for an application that parses untrusted PKCS#12 files. =
The buffer overflow may also potentially enable code execution depending on=
platform mitigations.</p><p>When verifying a PKCS#12 file that uses PBMAC1=
for the MAC, the PBKDF2 salt and keylength parameters from the file are =
used without validation. If the value of keylength exceeds the size of the =
fixed stack buffer used for the derived key (64 bytes), the key derivation =
will overflow the buffer. The overflow length is attacker-controlled. Also,=
if the salt parameter is not an OCTET STRING type this can lead to invalid=
or NULL pointer dereference.</p><p>Exploiting this issue requires a user =
or application to process a maliciously crafted PKCS#12 file. It is =
uncommon to accept untrusted PKCS#12 files in applications as they are =
usually used to store private keys which are trusted by definition. For =
this reason the issue was assessed as Moderate severity.</p><p>The FIPS =
modules in 3.6, 3.5 and 3.4 are not affected by this issue, as PKCS#12 =
processing is outside the OpenSSL FIPS module boundary.</p><p>OpenSSL 3.6, =
3.5 and 3.4 are vulnerable to this issue.<br>OpenSSL 3.3, 3.0, 1.1.1 and 1.=
0.2 are not affected by this issue as they do not support PBMAC1 in PKCS#12=
.<br>OpenSSL 3.6 users should upgrade to OpenSSL 3.6.1.<br>OpenSSL 3.5 =
users should upgrade to OpenSSL 3.5.5.<br>OpenSSL 3.4 users should upgrade =
to OpenSSL 3.4.4.</p><p>This issue was reported on 11th September 2025 by =
Stanislav Fort (Aisle Research) with a follow-up report on 21st November =
2025 by Stanislav Fort and Petr =C5=A0ime=C4=8Dek (Aisle Research). It was =
also independently reported on 14th October 2025 by Hamza (Metadust).=
<br>The fix was developed by Tomas Mraz.<br><br></p><h3><a =
contenteditable=3D"false" name=3D"CVE-2025-15467" class=3D"mce-item-anchor"=
style=3D"color: #000000;"></a><strong><span style=3D"text-decoration: =
underline;" data-mce-style=3D"text-decoration: underline;">CVE-2025-15467 -=
Stack buffer overflow in CMS AuthEnvelopedData parsing</span></strong></h3=
><p><strong><em>Link for this security advisory: </em><a =
href=3D"https://api.ourmailsender4.com/c/0fa1ea26d555517c5f5577ace0c322a8_5=
0cd8b9cf925410cd676be9f4d804e82?sid=3D9df465b02c94538ace6e1dbdac2fe500_bb75=
162114c0cdc6931c4430f84ff78f&aid=3DXp2h" target=3D"_blank" rel=3D"noopener"=
data-mce-href=3D"https://www.openssl.org/news/vulnerabilities.=
html#CVE-2025-15467" style=3D"color: #000000;">CVE-2025-15467</a><br><br>Se=
verity</strong>: High</p><p><strong>Issue summary</strong>: Parsing CMS =
AuthEnvelopedData message with maliciously crafted AEAD parameters can =
trigger a stack buffer overflow.</p><p><strong>Impact summary:</strong> A =
stack buffer overflow may lead to a crash, causing Denial of Service, or =
potentially remote code execution.</p><p>When parsing CMS AuthEnvelopedData=
structures that use AEAD ciphers such as AES-GCM, the IV (Initialization =
Vector) encoded in the ASN.1 parameters is copied into a fixed-size stack =
buffer without verifying that its length fits the destination. An attacker =
can supply a crafted CMS message with an oversized IV, causing a =
stack-based out-of-bounds write before any authentication or tag =
verification occurs.</p><p>Applications and services that parse untrusted =
CMS or PKCS#7 content using AEAD ciphers (e.g., S/MIME AuthEnvelopedData =
with AES-GCM) are vulnerable. Because the overflow occurs prior to =
authentication, no valid key material is required to trigger it. While =
exploitability to remote code execution depends on platform and toolchain =
mitigations, the stack-based write primitive represents a severe risk.=
</p><p>The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by =
this issue, as the CMS implementation is outside the OpenSSL FIPS module =
boundary.</p><p>OpenSSL 3.6, 3.5, 3.4, 3.3 and 3.0 are vulnerable to this =
issue.<br>OpenSSL 1.1.1 and 1.0.2 are not affected by this issue.=
<br>OpenSSL 3.6 users should upgrade to OpenSSL 3.6.1.<br>OpenSSL 3.5 users=
should upgrade to OpenSSL 3.5.5.<br>OpenSSL 3.4 users should upgrade to =
OpenSSL 3.4.4.<br>OpenSSL 3.3 users should upgrade to OpenSSL 3.3.6.=
<br>OpenSSL 3.0 users should upgrade to OpenSSL 3.0.19.</p><p>This issue =
was reported on 14th December 2025 by Stanislav Fort (Aisle Research).=
<br>The fix was developed by Igor Ustinov.<br><br></p><h3><a =
contenteditable=3D"false" name=3D"CVE-2025-15468" class=3D"mce-item-anchor"=
style=3D"color: #000000;"></a><span style=3D"text-decoration: underline;" =
data-mce-style=3D"text-decoration: underline;"><strong>CVE-2025-15468 =
- NULL dereference in SSL_CIPHER_find() function on unknown cipher =
ID</strong></span></h3><p><strong><em>Link for this security =
advisory: </em><a href=3D"https://api.ourmailsender4.=
com/c/e93768e23f72aeb20eb4f61506cc4837_8a64d26cb3ab5934e7ae615cad576b4c?=
sid=3D9df465b02c94538ace6e1dbdac2fe500_bb75162114c0cdc6931c4430f84ff78f&aid=
=3DXp2h" target=3D"_blank" rel=3D"noopener" data-mce-href=3D"https://www.=
openssl.org/news/vulnerabilities.html#CVE-2025-15468" style=3D"color: =
#000000;">CVE-2025-15468</a><br><br>Severity</strong>: =
Low</p><p><strong>Issue summary</strong>: If an application using the =
SSL_CIPHER_find() function in a QUIC protocol client or server receives an =
unknown cipher suite from the peer, a NULL dereference occurs.=
</p><p><strong>Impact summary</strong>: A NULL pointer dereference leads to=
abnormal termination of the running process causing Denial of Service.=
</p><p>Some applications call SSL_CIPHER_find() from the client_hello_cb =
callback on the cipher ID received from the peer. If this is done with an =
SSL object implementing the QUIC protocol, NULL pointer dereference will =
happen if the examined cipher ID is unknown or unsupported. As it is not =
very common to call this function in applications using the QUIC protocol =
and the worst outcome is Denial of Service, the issue was assessedas Low =
severity.</p><p>The vulnerable code was introduced in the 3.2 version with =
the addition of the QUIC protocol support.</p><p>The FIPS modules in 3.6, 3=
.5, 3.4 and 3.3 are not affected by this issue, as the QUIC implementation =
is outside the OpenSSL FIPS module boundary.</p><p>OpenSSL 3.6, 3.5, 3.4 =
and 3.3 are vulnerable to this issue.<br>OpenSSL 3.0, 1.1.1 and 1.0.2 are =
not affected by this issue.<br>OpenSSL 3.6 users should upgrade to OpenSSL =
3.6.1.<br>OpenSSL 3.5 users should upgrade to OpenSSL 3.5.5.<br>OpenSSL 3.4=
users should upgrade to OpenSSL 3.4.4.<br>OpenSSL 3.3 users should upgrade=
to OpenSSL 3.3.6.</p><p>This issue was reported on 13th December 2025 by =
Stanislav Fort (Aisle Research).The fix was developed by Stanislav Fort =
(Aisle Research).</p><h3><a contenteditable=3D"false" =
name=3D"CVE-2025-15469" class=3D"mce-item-anchor" style=3D"color: =
#000000;"></a><strong><span style=3D"text-decoration: underline;" =
data-mce-style=3D"text-decoration: underline;">CVE-2025-15469 =
- "openssl dgst" one-shot codepath silently truncates inputs =
>16MB</span></strong></h3><p><strong><em>Link for this security =
advisory: </em><a href=3D"https://api.ourmailsender4.=
com/c/5cc2994f238f983900cf5ca3fbf983b3_ba9183653f28f0a2e13245f654d6bc49?=
sid=3D9df465b02c94538ace6e1dbdac2fe500_bb75162114c0cdc6931c4430f84ff78f&aid=
=3DXp2h" target=3D"_blank" rel=3D"noopener" data-mce-href=3D"https://www.=
openssl.org/news/vulnerabilities.html#CVE-2025-15469" style=3D"color: =
#000000;">CVE-2025-15469</a><br><br>Severity</strong>: =
Low</p><p><strong>Issue summary</strong>: The "openssl dgst" command-line =
tool silently truncates input data to 16MB when using one-shot signing =
algorithms and reports success instead of an error.</p><p><strong>Impact =
summary</strong>: A user signing or verifying files larger than 16MB with =
one-shot algorithms (such as Ed25519, Ed448, or ML-DSA) may believe the =
entire file is authenticated while trailing data beyond 16MB remains =
unauthenticated.</p><p>When the "openssl dgst" command is used with =
algorithms that only support one-shot signing (Ed25519, Ed448, ML-DSA-44, =
ML-DSA-65, ML-DSA-87), the input is buffered with a 16MB limit. If the =
input exceeds this limit, the tool silently truncates to the first 16MB and=
continues without signaling an error, contrary to what the documentation =
states. This creates an integrity gap where trailing bytes can be modified =
without detection if both signing and verification are performed using the =
same affected codepath.</p><p>The issue affects only the command-line tool =
behavior. Verifiers that process the full message using library APIs will =
reject the signature, so the risk primarily affects workflows that both =
sign and verify with the affected "openssl dgst" command. Streaming digest =
algorithms for "openssl dgst" and library users are unaffected.</p><p>The =
FIPS modules in 3.5 and 3.6 are not affected by this issue, as the =
command-line tools are outside the OpenSSL FIPS module boundary.=
</p><p>OpenSSL 3.5 and 3.6 are vulnerable to this issue.<br>OpenSSL 3.4, 3.=
3, 3.0, 1.1.1 and 1.0.2 are not affected by this issue.<br>OpenSSL 3.6 =
users should upgrade to OpenSSL 3.6.1.<br>OpenSSL 3.5 users should upgrade =
to OpenSSL 3.5.5.</p><p>This issue was reported on 13th December 2025 by =
Stanislav Fort (Aisle Research). The fix was developed by Viktor =
Dukhovni.</p><h3><a contenteditable=3D"false" name=3D"CVE-2025-66199" =
class=3D"mce-item-anchor" style=3D"color: #000000;"></a><span =
style=3D"text-decoration: underline;" data-mce-style=3D"text-decoration: =
underline;"><strong>CVE-2025-66199 - TLS 1.3 CompressedCertificate =
excessive memory allocation</strong></span></h3><p><strong><em>Link for =
this security advisory: </em><a href=3D"https://api.ourmailsender4.=
com/c/1c08b3cc40bec598ae7d1786d4d118f9_5313d6d18b3f6bad2057c39bbb452666?=
sid=3D9df465b02c94538ace6e1dbdac2fe500_bb75162114c0cdc6931c4430f84ff78f&aid=
=3DXp2h" target=3D"_blank" rel=3D"noopener" data-mce-href=3D"https://www.=
openssl.org/news/vulnerabilities.html#CVE-2025-66199" style=3D"color: =
#000000;">CVE-2025-66199</a><br><br>Severity</strong>: =
Low</p><p><strong>Issue summary</strong>: A TLS 1.3 connection using =
certificate compression can be forced to allocate a large buffer before =
decompression without checking against the configured certificate size =
limit.</p><p><strong>Impact summary</strong>: An attacker can cause =
per-connection memory allocations of up to approximately 22 MiB and extra =
CPU work, potentially leading to service degradation or resource exhaustion=
(Denial of Service).</p><p>In affected configurations, the peer-supplied =
uncompressed certificate length from a CompressedCertificate message is =
used to grow a heap buffer prior to decompression. This length is not =
bounded by the max_cert_list setting, which otherwise constrains =
certificate message sizes. An attacker can exploit this to cause large =
per-connection allocations followed by handshake failure. No memory =
corruption or information disclosure occurs.</p><p>This issue only affects =
builds where TLS 1.3 certificate compression is compiled in (i.e., not =
OPENSSL_NO_COMP_ALG) and at least one compression algorithm (brotli, zlib, =
or zstd) is available, and where the compression extension is negotiated. =
Both clients receiving a server CompressedCertificateand servers in mutual =
TLS scenarios receiving a client CompressedCertificate are affected. =
Servers that do not request client certificates are not vulnerable to =
client-initiated attacks.</p><p>Users can mitigate this issue by setting =
SSL_OP_NO_RX_CERTIFICATE_COMPRESSION to disable receiving compressed =
certificates.</p><p>The FIPS modules in 3.6, 3.5, 3.4 and 3.3 are not =
affected by this issue, as the TLS implementation is outside the OpenSSL =
FIPS module boundary.</p><p>OpenSSL 3.6, 3.5, 3.4 and 3.3 are vulnerable to=
this issue.<br>OpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue=
.<br>OpenSSL 3.6 users should upgrade to OpenSSL 3.6.1.<br>OpenSSL 3.5 =
users should upgrade to OpenSSL 3.5.5.<br>OpenSSL 3.4 users should upgrade =
to OpenSSL 3.4.4.<br>OpenSSL 3.3 users should upgrade to OpenSSL 3.3.6.=
</p><p>This issue was reported on 8th November 2025 by Tomas Dulka (Aisle =
Research) and Stanislav Fort (Aisle Research). The fix was developed =
by Tomas Dulka (Aisle Research) and Stanislav Fort (Aisle Research).=
</p><h3><a contenteditable=3D"false" name=3D"CVE-2025-68160" =
class=3D"mce-item-anchor" style=3D"color: #000000;"></a><strong><span =
style=3D"text-decoration: underline;" data-mce-style=3D"text-decoration: =
underline;">CVE-2025-68160 - Heap out-of-bounds write in =
BIO_f_linebuffer on short writes</span></strong></h3><p><strong><em>Link =
for this security advisory: </em><a href=3D"https://api.ourmailsender4=
.com/c/54289862e90b0e98f70aede0c1167797_72854908c3338b8691723e6bfc9f902e?=
sid=3D9df465b02c94538ace6e1dbdac2fe500_bb75162114c0cdc6931c4430f84ff78f&aid=
=3DXp2h" target=3D"_blank" rel=3D"noopener" data-mce-href=3D"https://www.=
openssl.org/news/vulnerabilities.html#CVE-2025-68160" style=3D"color: =
#000000;">CVE-2025-68160</a><br><br>Severity</strong>: =
Low</p><p><strong>Issue summary</strong>: Writing large, newline-free data =
into a BIO chain using the line-buffering filter where the next BIO =
performs short writes can trigger a heap-based out-of-bounds write.=
</p><p><strong>Impact summary:</strong> This out-of-bounds write can cause =
memory corruption which typically results in a crash, leading to Denial of =
Service for an application.</p><p>The line-buffering BIO filter =
(BIO_f_linebuffer) is not used by default in TLS/SSL data paths. In OpenSSL=
command-line applications, it is typically only pushed onto stdout/stderr =
on VMS systems. Third-party applications that explicitly use this filter =
with a BIO chain that can short-write and that write large, newline-free =
data influenced by an attacker would be affected. However, the =
circumstances where this could happen are unlikely to be under attacker =
control, and BIO_f_linebuffer is unlikely to be handling non-curated data =
controlled by an attacker. For that reason the issue was assessed as Low =
severity.</p><p>The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not =
affected by this issue, as the BIO implementation is outside the OpenSSL =
FIPS module boundary.</p><p>OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.=
2 are vulnerable to this issue.<br>OpenSSL 3.6 users should upgrade to =
OpenSSL 3.6.1.<br>OpenSSL 3.5 users should upgrade to OpenSSL 3.5.5.OpenSSL=
3.4 users should upgrade to OpenSSL 3.4.4.<br>OpenSSL 3.3 users should =
upgrade to OpenSSL 3.3.6.<br>OpenSSL 3.0 users should upgrade to OpenSSL 3.=
0.19.<br>OpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1ze (premium =
support customers only).<br>OpenSSL 1.0.2 users should upgrade to OpenSSL 1=
.0.2zn (premium support customers only).</p><p>This issue was reported on =
1st December 2025 by Petr Simecek (Aisle Research) and Stanislav Fort =
(Aisle Research). <br>The fix was developed by Stanislav Fort (Aisle =
Research) and Neil Horman.<br><br></p><h3><a contenteditable=3D"false" =
name=3D"CVE-2025-69418" class=3D"mce-item-anchor" style=3D"color: =
#000000;"></a><strong><span style=3D"text-decoration: underline;" =
data-mce-style=3D"text-decoration: underline;">CVE-2025-69418 =
- Unauthenticated/unencrypted trailing bytes with low-level OCB =
function calls</span></strong></h3><p><strong><em>Link for this security =
advisory: </em><a href=3D"https://api.ourmailsender4.=
com/c/9f69cd8fe76d5073d61f1eeb21d7bf46_63d295777300410d9e134d46a7c31de3?=
sid=3D9df465b02c94538ace6e1dbdac2fe500_bb75162114c0cdc6931c4430f84ff78f&aid=
=3DXp2h" target=3D"_blank" rel=3D"noopener" data-mce-href=3D"https://www.=
openssl.org/news/vulnerabilities.html#CVE-2025-69418" style=3D"color: =
#000000;">CVE-2025-69418</a><br><br>Severity</strong>: =
Low</p><p><strong>Issue summary</strong>: When using the low-level OCB API =
directly with AES-NI or other hardware-accelerated code paths, inputs whose=
length is not a multiple of 16 bytes can leave the final partial block =
unencrypted and unauthenticated.</p><p><strong>Impact summary:</strong> The=
trailing 1-15 bytes of a message may be exposed in cleartext on encryption=
and are not covered by the authentication tag, allowing an attacker to =
read or tamper with those bytes without detection. </p><p>The =
low-level OCB encrypt and decrypt routines in the hardware-accelerated =
stream path process full 16-byte blocks but do not advance the input/output=
pointers. The subsequent tail-handling code then operates on the original =
base pointers, effectively reprocessing the beginning of the buffer while =
leaving the actual trailing bytes unprocessed. The authentication checksum =
also excludes the true tail bytes.</p><p>However, typical OpenSSL consumers=
using EVP are not affected because the higher-level EVP and provider OCB =
implementations split inputs so that full blocks and trailing partial =
blocks are processed in separate calls, avoiding the problematic code path.=
Additionally, TLS does not use OCB ciphersuites. The vulnerability only =
affects applications that call the low-level CRYPTO_ocb128_encrypt() or =
CRYPTO_ocb128_decrypt() functions directly with non-block-aligned lengths =
in a single call on hardware-accelerated builds. For these reasons, the =
issue was assessed as Low severity.</p><p>The FIPS modules in 3.6, 3.5, 3.4=
, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as OCB mode is not =
a FIPS-approved algorithm.</p><p>OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 =
are vulnerable to this issue.<br>OpenSSL 1.0.2 is not affected by this =
issue.<br>OpenSSL 3.6 users should upgrade to OpenSSL 3.6.1.<br>OpenSSL 3.5=
users should upgrade to OpenSSL 3.5.5.<br>OpenSSL 3.4 users should upgrade=
to OpenSSL 3.4.4.<br>OpenSSL 3.3 users should upgrade to OpenSSL 3.3.6.=
<br>OpenSSL 3.0 users should upgrade to OpenSSL 3.0.19.<br>OpenSSL 1.1.1 =
users should upgrade to OpenSSL 1.1.1ze. (premium support customers only).=
</p><p>This issue was reported on 16th December 2025 by Stanislav Fort =
(Aisle Research).<br>The fix was developed by Stanislav Fort (Aisle =
Research).<br><br></p><h3><a contenteditable=3D"false" =
name=3D"CVE-2025-69419" class=3D"mce-item-anchor" style=3D"color: =
#000000;"></a><strong><span style=3D"text-decoration: underline;" =
data-mce-style=3D"text-decoration: underline;">CVE-2025-69419 - Out of=
bounds write in PKCS12_get_friendlyname() UTF-8 conversion</span></strong>=
</h3><p><strong><em>Link for this security advisory: </em><a =
href=3D"https://api.ourmailsender4.com/c/b82f65a8d945e52d0e28e997131576bd_7=
7fa4f17f9c376df689a3b2fdab6d2ff?sid=3D9df465b02c94538ace6e1dbdac2fe500_bb75=
162114c0cdc6931c4430f84ff78f&aid=3DXp2h" target=3D"_blank" rel=3D"noopener"=
data-mce-href=3D"https://www.openssl.org/news/vulnerabilities.=
html#CVE-2025-69419" style=3D"color: #000000;">CVE-2025-69419</a><br><br>Se=
verity</strong>: Moderate</p><p><strong>Issue summary</strong>: Calling =
PKCS12_get_friendlyname() function on a maliciously crafted PKCS#12 file =
with a BMPString (UTF-16BE) friendly name containing non-ASCII BMP code =
points can trigger a write before the allocated buffer.=
</p><p><strong>Impact summary</strong>: The out-of-bounds write can cause a=
memory corruption which can have various consequences including a Denial =
of Service or Execution of attacker-supplied code.</p><p>The =
OPENSSL_uni2utf8() function performs a two-pass conversion of a PKCS#12 =
BMPString (UTF-16BE) to UTF-8. In the second pass, when emitting UTF-8 =
bytes, the helper function bmp_to_utf8() incorrectly forwards the remaining=
UTF-16 source byte count as the destination buffer capacity to UTF8_putc()=
. For BMP code points above U+07FF, UTF-8 requires three bytes, but the =
forwarded capacity can be just two bytes. UTF8_putc() then returns -1, and =
this negative value is added to the output length without validation, =
causing the length to become negative. The subsequent trailing NUL byte is =
then written at a negative offset, causing write outside of heap allocated =
buffer.</p><p>The vulnerability is reachable via the public =
PKCS12_get_friendlyname() API when parsing attacker-controlled PKCS#12 =
files. While PKCS12_parse() uses a different code path that avoids this =
issue, PKCS12_get_friendlyname() directly invokes the vulnerable function. =
Exploitation requires an attacker to provide a malicious PKCS#12 file to be=
parsed by the application. For that reason the issue was assessed as =
Moderate severity according to our Security Policy.</p><p>The FIPS modules =
in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the =
PKCS#12 implementation is outside the OpenSSL FIPS module boundary.=
</p><p>OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this =
issue.<br>OpenSSL 1.0.2 is not affected by this issue.<br>OpenSSL 3.6 users=
should upgrade to OpenSSL 3.6.1.<br>OpenSSL 3.5 users should upgrade to =
OpenSSL 3.5.5.<br>OpenSSL 3.4 users should upgrade to OpenSSL 3.4.4.=
<br>OpenSSL 3.3 users should upgrade to OpenSSL 3.3.6.<br>OpenSSL 3.0 users=
should upgrade to OpenSSL 3.0.19.<br>OpenSSL 1.1.1 users should upgrade to=
OpenSSL 1.1.1ze (premium support customers only).</p><p>This issue was =
reported on 16th December 2025 by Stanislav Fort (Aisle Research).<br>The =
fix was developed by Norbert Pocs.<br><br></p><h3><a =
contenteditable=3D"false" name=3D"CVE-2025-69420" class=3D"mce-item-anchor"=
style=3D"color: #000000;"></a><strong><span style=3D"text-decoration: =
underline;" data-mce-style=3D"text-decoration: underline;">CVE-2025-69420 =
- Missing ASN1_TYPE validation in TS_RESP_verify_response() =
function</span></strong></h3><p><strong><em>Link for this security =
advisory: </em><a href=3D"https://api.ourmailsender4.=
com/c/f1dfeaca505ed8f8a01ab277ac476725_a33128a6f0060b95b9013b7a6ca45fd3?=
sid=3D9df465b02c94538ace6e1dbdac2fe500_bb75162114c0cdc6931c4430f84ff78f&aid=
=3DXp2h" target=3D"_blank" rel=3D"noopener" data-mce-href=3D"https://www.=
openssl.org/news/vulnerabilities.html#CVE-2025-69420" style=3D"color: =
#000000;">CVE-2025-69420</a><br><br>Severity</strong>: =
Low</p><p><strong>Issue summary</strong>: A type confusion vulnerability =
exists in the TimeStamp Response verification code where an ASN1_TYPE union=
member is accessed without first validating the type, causing an invalid =
or NULL pointer dereference when processing a malformed TimeStamp Response =
file.</p><p><strong>Impact summary</strong>: An application calling =
TS_RESP_verify_response() with a malformed TimeStamp Response can be caused=
to dereference an invalid or NULL pointer when reading, resulting in a =
Denial of Service.</p><p>The functions ossl_ess_get_signing_cert() and =
ossl_ess_get_signing_cert_v2() access the signing cert attribute value =
without validating its type. When the type is not V_ASN1_SEQUENCE, this =
results in accessing invalid memory through the ASN1_TYPE union, causing a =
crash.</p><p>Exploiting this vulnerability requires an attacker to provide =
a malformed TimeStamp Response to an application that verifies timestamp =
responses. The TimeStamp protocol (RFC 3161) is not widely used and the =
impact of the exploit is just a Denial of Service. For these reasons the =
issue was assessed as Low severity.</p><p>The FIPS modules in 3.5, 3.4, 3.3=
and 3.0 are not affected by this issue, as the TimeStamp Response =
implementation is outside the OpenSSL FIPS module boundary.</p><p>OpenSSL 3=
.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.<br>OpenSSL 1=
.0.2 is not affected by this issue.<br>OpenSSL 3.6 users should upgrade to =
OpenSSL 3.6.1.<br>OpenSSL 3.5 users should upgrade to OpenSSL 3.5.5.=
<br>OpenSSL 3.4 users should upgrade to OpenSSL 3.4.4.<br>OpenSSL 3.3 users=
should upgrade to OpenSSL 3.3.6.<br>OpenSSL 3.0 users should upgrade to =
OpenSSL 3.0.19.<br>OpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1zn. =
(premium support customers only).</p><p>This issue was reported on 16th =
December 2025 by Luigino Camastra (Aisle Research).<br>The fix was =
developed by Bob Beck.<br><br></p><h3><a contenteditable=3D"false" =
name=3D"CVE-2025-69421" class=3D"mce-item-anchor" style=3D"color: =
#000000;"></a><strong><span style=3D"text-decoration: underline;" =
data-mce-style=3D"text-decoration: underline;">CVE-2025-69421 - NULL =
Pointer Dereference in PKCS12_item_decrypt_d2i_ex function</span></strong><=
/h3><p><strong><em>Link for this security advisory: </em><a =
href=3D"https://api.ourmailsender4.com/c/99c6b58e3f05804cbd044c5a64694974_9=
3de888f90bd93ee121b2a97915e4469?sid=3D9df465b02c94538ace6e1dbdac2fe500_bb75=
162114c0cdc6931c4430f84ff78f&aid=3DXp2h" target=3D"_blank" rel=3D"noopener"=
data-mce-href=3D"https://www.openssl.org/news/vulnerabilities.=
html#CVE-2025-69421" style=3D"color: #000000;">CVE-2025-69421</a><br><br>Se=
verity</strong>: Low</p><p><strong>Issue summary</strong>: Processing a =
malformed PKCS#12 file can trigger a NULL pointer dereference in the =
PKCS12_item_decrypt_d2i_ex() function.</p><p><strong>Impact =
summary</strong>: A NULL pointer dereference can trigger a crash which =
leads to Denial of Service for an application processing PKCS#12 files.=
</p><p>The PKCS12_item_decrypt_d2i_ex() function does not check whether the=
oct parameter is NULL before dereferencing it. When called from =
PKCS12_unpack_p7encdata() with a malformed PKCS#12 file, this parameter can=
be NULL, causing a crash. The vulnerability is limited to Denial of =
Service and cannot be escalated to achieve code execution or memory =
disclosure.</p><p>Exploiting this issue requires an attacker to provide a =
malformed PKCS#12 file to an application that processes it. For that reason=
the issue was assessed as Low severity according to our Security Policy.=
</p><p>The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by =
this issue, as the PKCS#12 implementation is outside the OpenSSL FIPS =
module boundary.</p><p>OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are=
vulnerable to this issue.<br>OpenSSL 3.6 users should upgrade to OpenSSL 3=
.6.1.<br>OpenSSL 3.5 users should upgrade to OpenSSL 3.5.5.<br>OpenSSL 3.4 =
users should upgrade to OpenSSL 3.4.4.<br>OpenSSL 3.3 users should upgrade =
to OpenSSL 3.3.6.<br>OpenSSL 3.0 users should upgrade to OpenSSL 3.0.19.=
<br>OpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1ze (premium support =
customers only).<br>OpenSSL 1.0.2 users should upgrade to OpenSSL 1.0.2zn =
(premium support customers only).</p><p>This issue was reported on 21st =
December 2025 by Luigino Camastra (Aisle Research). <br>The fix was =
developed by Luigino Camastra (Aisle Research).</p><p><br></p><h3><a =
contenteditable=3D"false" name=3D"CVE-2026-22795" class=3D"mce-item-anchor"=
style=3D"color: #000000;"></a><strong><span style=3D"text-decoration: =
underline;" data-mce-style=3D"text-decoration: underline;">CVE-2026-22795 -=
Missing ASN1_TYPE validation in PKCS#12 parsing</span></strong></h3><p><st=
rong><em>Link for this security advisory: </em><a href=3D"https://api.=
ourmailsender4.com/c/7fea32674a28e11da5831b252b51af97_ad887e1e892d16352a941=
437100de4dc?sid=3D9df465b02c94538ace6e1dbdac2fe500_bb75162114c0cdc6931c4430=
f84ff78f&aid=3DXp2h" target=3D"_blank" rel=3D"noopener" =
data-mce-href=3D"https://www.openssl.org/news/vulnerabilities.=
html#CVE-2026-22795" style=3D"color: #000000;">CVE-2026-22795</a></strong><=
br><strong><br>Severity</strong>: Low<br><br><strong>Issue =
summary</strong>: An invalid or NULL pointer dereference can happen =
in<br>an application processing a malformed PKCS#12 file.=
<br><br><strong>Impact summary</strong>: An application processing a =
malformed PKCS#12 file can be caused to dereference an invalid or NULL =
pointer on memory read, resulting in a Denial of Service.<br><br>A type =
confusion vulnerability exists in PKCS#12 parsing code where an ASN1_TYPE =
union member is accessed without first validating the type, causing an =
invalid pointer read.<br><br>The location is constrained to a 1-byte =
address space, meaning any attempted pointer manipulation can only target =
addresses between 0x00 and 0xFF. This range corresponds to the zero page, =
which is unmapped on most modern operating systems and will reliably result=
in a crash, leading only to a Denial of Service. Exploiting this =
issue also requires a user or application<br>to process a maliciously =
crafted PKCS#12 file. It is uncommon to accept untrusted PKCS#12 files in =
applications as they are usually used to store private keys which are =
trusted by definition. For these reasons, the issue was assessed as Low =
severity.<br><br>The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected=
by this issue, as the PKCS12 implementation is outside the OpenSSL FIPS =
module boundary.<br><br>OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are =
vulnerable to this issue.<br>OpenSSL 1.0.2 is not affected by this issue.=
<br>OpenSSL 3.6 users should upgrade to OpenSSL 3.6.1.<br>OpenSSL 3.5 users=
should upgrade to OpenSSL 3.5.5.<br>OpenSSL 3.4 users should upgrade to =
OpenSSL 3.4.4.<br>OpenSSL 3.3 users should upgrade to OpenSSL 3.3.6.=
<br>OpenSSL 3.0 users should upgrade to OpenSSL 3.0.19.<br>OpenSSL 1.1.1 =
users should upgrade to OpenSSL 1.1.1ze. (premium support customers only).=
<br><br>This issue was reported on 8th January 2026 by Luigino Camastra =
(Aisle Research).<br>The fix was developed by Bob Beck.<br><br></p><h3><a =
contenteditable=3D"false" name=3D"CVE-2026-22796" class=3D"mce-item-anchor"=
style=3D"color: #000000;"></a><strong><span style=3D"text-decoration: =
underline;" data-mce-style=3D"text-decoration: underline;">CVE-2026-22796 -=
ASN1_TYPE Type Confusion in the PKCS7_digest_from_attributes() =
function</span></strong></h3><p><strong><em>Link for this security =
advisory: </em><a href=3D"https://api.ourmailsender4.=
com/c/4ff122af4d102dfad41cb0c7eede6ad0_b143229bccf789fc46655a4df99d6a71?=
sid=3D9df465b02c94538ace6e1dbdac2fe500_bb75162114c0cdc6931c4430f84ff78f&aid=
=3DXp2h" target=3D"_blank" rel=3D"noopener" data-mce-href=3D"https://www.=
openssl.org/news/vulnerabilities.html#CVE-2026-22796" style=3D"color: =
#000000;">CVE-2026-22796</a><br><br>Severity</strong>: =
Low<br><br><strong>Issue summary</strong>: A type confusion vulnerability =
exists in the signature verification of signed PKCS#7 data where an =
ASN1_TYPE union member is accessed without first validating the type, =
causing an invalid or NULL pointer dereference when processing malformed =
PKCS#7 data.<br><br><strong>Impact summary</strong>: An application =
performing signature verification of PKCS#7 data or calling directly the =
PKCS7_digest_from_attributes() function can be caused to dereference an =
invalid or NULL pointer when reading, resulting in a Denial of Service.=
<br><br>The function PKCS7_digest_from_attributes() accesses the message =
digest attribute value without validating its type. When the type is =
not V_ASN1_OCTET_STRING, this results in accessing invalid memory through =
the ASN1_TYPE union, causing a crash.<br><br>Exploiting this =
vulnerability requires an attacker to provide a malformed signed =
PKCS#7 to an application that verifies it. The impact of the exploit =
is just a Denial of Service, the PKCS7 API is legacy and =
applications should be using the CMS API instead. For these reasons =
the issue was assessed as Low severity.<br><br>The FIPS modules in 3.5=
, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS#7 =
parsing implementation is outside the OpenSSL FIPS module boundary.=
<br><br>OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to =
this issue.<br>OpenSSL 3.6 users should upgrade to OpenSSL 3.6.1.=
<br>OpenSSL 3.5 users should upgrade to OpenSSL 3.5.5.<br>OpenSSL 3.4 users=
should upgrade to OpenSSL 3.4.4.<br>OpenSSL 3.3 users should upgrade to =
OpenSSL 3.3.6.<br>OpenSSL 3.0 users should upgrade to OpenSSL 3.0.19.=
<br>OpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1ze. (premium =
support customers only).<br>OpenSSL 1.0.2 users should upgrade to OpenSSL 1=
.0.2zn. (premium support customers only).<br><br>This issue was =
reported on 8th January 2026 by Luigino Camastra (Aisle Research). <br>The =
fix was developed by Bob Beck.<br><br><br><span style=3D"font-family: =
Roboto, sans-serif;" data-mce-style=3D"font-family: Roboto, =
sans-serif;">General Advisory Notes</span></p><p><br><span =
style=3D"font-family: Roboto, sans-serif;" data-mce-style=3D"font-family: =
Roboto, sans-serif;">URL for this Security Advisory:</span><br><span =
style=3D"font-family: Roboto, sans-serif;" data-mce-style=3D"font-family: =
Roboto, sans-serif;"><a href=3D"https://api.ourmailsender4.=
com/c/b303262f2e72452922eb579d0b38f119_418593abac7dd7c8f2f3b0994246e640?=
sid=3D9df465b02c94538ace6e1dbdac2fe500_bb75162114c0cdc6931c4430f84ff78f&aid=
=3DXp2h" target=3D"_blank" rel=3D"noopener" data-mce-href=3D"https://openss=
l-library.org/news/secadv/20260127.txt" style=3D"color: =
#000000;">https://openssl-library.org/news/secadv/20260127.=
txt</a></span><br><br><span style=3D"font-family: Roboto, sans-serif;" =
data-mce-style=3D"font-family: Roboto, sans-serif;">Note: the online =
version of the advisory may be updated with additional details over =
time.</span><br><br><span style=3D"font-family: Roboto, sans-serif;" =
data-mce-style=3D"font-family: Roboto, sans-serif;">For details of OpenSSL =
severity classifications, please see:</span><br><span style=3D"font-family:=
Roboto, sans-serif;" data-mce-style=3D"font-family: Roboto, =
sans-serif;"><a href=3D"https://api.ourmailsender4.com/c/973a0ac54f6826aa14=
65a8a679ecf357_084bf7ac1742e62953356d30919e1977?sid=3D9df465b02c94538ace6e1=
dbdac2fe500_bb75162114c0cdc6931c4430f84ff78f&aid=3DXp2h" =
data-mce-href=3D"https://openssl-library.org/policies/general/security-poli=
cy/" style=3D"color: #000000;">https://openssl-library.=
org/policies/general/security-policy/</a></span></p></div></td></tr></table=
></td></tr></table><table align=3D"center" class=3D"" style=3D"max-width: =
100%; min-width: 100%; " width=3D"100%" cellPadding=3D"0" =
cellSpacing=3D"0"><tr><td align=3D"center" style=3D"padding-top: 0px; =
padding-left: 0px; padding-right: 0px; padding-bottom: 20px; =
background-color: transparent; " width=3D"100%" valign=3D"top"><table =
align=3D"center" style=3D"min-width: 100%; border-collapse: collapse; =
border-top-color: #f4f4f4; border-top-style: solid; border-top-width: 2px; =
mso-table-lspace: 0pt; mso-table-rspace: 0pt; -ms-text-size-adjust: 100%; =
-webkit-text-size-adjust: 100%; " width=3D"100%" cellPadding=3D"0" =
cellSpacing=3D"0"><tr><td style=3D"-ms-text-size-adjust: 100%; =
mso-line-height-rule: exactly; -webkit-text-size-adjust: 100%; =
"><span/></td></tr></table></td></tr></table><table align=3D"center" =
class=3D"" style=3D"max-width: 100%; min-width: 100%; " width=3D"100%" =
cellPadding=3D"0" cellSpacing=3D"0"><tr><td style=3D"padding-top: 0; =
padding-left: 0; padding-right: 0; padding-bottom: 0; " =
width=3D"100%"><table align=3D"center" style=3D"max-width: 100%; " =
width=3D"100%" cellPadding=3D"0" cellSpacing=3D"0"><tr><td =
style=3D"padding-top: 0px; border-width: 0; padding-left: 0px; =
padding-right: 0px; padding-bottom: 10px; background-color: transparent; " =
width=3D"100%"><div style=3D"color: #000000; position: relative; font-size:=
14px; textAlign: left; word-break: break-word; font-family: arial; =
font-weight: normal; mso-line-height-rule: exactly; line-height: =
normal;letter-spacing: normal; "><div style=3D"text-align: center;" =
data-mce-style=3D"text-align: center;"><a href=3D"https://api.=
ourmailsender4.com/c/1261b1974af541f09cc207b48e9b1297_dee93e7a0a415ee1dc489=
e7202e427cc?sid=3D9df465b02c94538ace6e1dbdac2fe500_bb75162114c0cdc6931c4430=
f84ff78f&aid=3DXp2h" target=3D"_blank" rel=3D"noopener" =
data-mce-href=3D"https://openssl-corporation.org" style=3D"color: =
#000000;">OpenSSL Corporation</a>, Inc. 40 East Main Street, Newark, =
<br>New Castle County, 19711, USA</div></div></td></tr></table></td></tr></=
table><table align=3D"center" class=3D"" style=3D"max-width: 100%; =
min-width: 100%; " width=3D"100%" cellPadding=3D"0" =
cellSpacing=3D"0"><tr><td style=3D"padding-top: 0px; padding-left: 0px; =
padding-right: 0px; padding-bottom: 0px; " width=3D"100%"><table =
align=3D"center" style=3D"max-width: 100%; " width=3D"100%" =
cellPadding=3D"0" cellSpacing=3D"0"><tr><td style=3D"padding-top: 0px; =
padding-left: 0px; padding-right: 0px; padding-bottom: 10px; =
background-color: transparent; " width=3D"100%"><div style=3D"color: =
#000000; position: relative; font-size: 14px; textAlign: left; word-break: =
break-word; font-family: arial; font-weight: normal; mso-line-height-rule: =
exactly; line-height: normal;letter-spacing: normal; "><div =
style=3D"text-align: center;" data-mce-style=3D"text-align: center;"><span =
style=3D"background-color: transparent;" data-mce-style=3D"background-color=
: transparent;"><a href=3D"https://api.ourmailsender4.com/api/unsubscribe?=
key=3D710ed089fecca3a5033a34a86de10e1ef0c6dab67673de9f20329c6b51ef15c65cf77=
baeca94ddc37976060fb5d387c5_1f76734a29e0b75efdc418d5169ca8ba" =
data-mce-href=3D"https://api.ourmailsender4.com/api/unsubscribe?=
key=3D710ed089fecca3a5033a34a86de10e1ef0c6dab67673de9f20329c6b51ef15c65cf77=
baeca94ddc37976060fb5d387c5_1f76734a29e0b75efdc418d5169ca8ba" =
style=3D"color: #000000;">Unsubscribe</a> | <a =
href=3D"https://api.ourmailsender4.com/api/update?key=3D710ed089fecca3a5033=
a34a86de10e1ef0c6dab67673de9f20329c6b51ef15c65cf77baeca94ddc37976060fb5d387=
c5_1f76734a29e0b75efdc418d5169ca8ba" data-mce-href=3D"https://api.=
ourmailsender4.com/api/update?key=3D710ed089fecca3a5033a34a86de10e1ef0c6dab=
67673de9f20329c6b51ef15c65cf77baeca94ddc37976060fb5d387c5_1f76734a29e0b75ef=
dc418d5169ca8ba" style=3D"color: #000000;">Update Profile</a> | <=
a href=3D"https://api.ourmailsender4.com/api/junk?key=3D710ed089fecca3a5033=
a34a86de10e1ef0c6dab67673de9f20329c6b51ef15c65cf77baeca94ddc37976060fb5d387=
c5_1f76734a29e0b75efdc418d5169ca8ba" data-mce-href=3D"https://api.=
ourmailsender4.com/api/junk?key=3D710ed089fecca3a5033a34a86de10e1ef0c6dab67=
673de9f20329c6b51ef15c65cf77baeca94ddc37976060fb5d387c5_1f76734a29e0b75efdc=
418d5169ca8ba" data-mce-selected=3D"inline-boundary" style=3D"color: =
#000000;">Report Junk</a></span></div></div></td></tr></table></td></tr></t=
able><table align=3D"center" class=3D"" style=3D"max-width: 100%; =
min-width: 100%; " width=3D"100%" cellPadding=3D"0" =
cellSpacing=3D"0"><tr><td style=3D"padding-top: 0; padding-left: 0; =
padding-right: 0; padding-bottom: 0; " width=3D"100%"><table =
align=3D"center" style=3D"max-width: 100%; " width=3D"100%" =
cellPadding=3D"0" cellSpacing=3D"0"><tr><td style=3D"padding-top: 0px; =
border-width: 0; padding-left: 0px; padding-right: 0px; padding-bottom: =
20px; background-color: transparent; " width=3D"100%"><div style=3D"color: =
#000000; position: relative; font-size: 14px; textAlign: left; word-break: =
break-word; font-family: arial; font-weight: normal; mso-line-height-rule: =
exactly; line-height: normal;letter-spacing: normal; "><div =
style=3D"text-align: center;"><a href=3D"https://api.ourmailsender4.=
com/templatePreview?key=3D710ed089fecca3a5033a34a86de10e1ef0c6dab67673de9f2=
0329c6b51ef15c65cf77baeca94ddc37976060fb5d387c5_1f76734a29e0b75efdc418d5169=
ca8ba&html=3Dtrue" target=3D"_blank" rel=3D"noopener" style=3D"color: =
#000000;">View this email in your browser</a></div></div></td></tr></table>=
</td></tr></table></td></tr></table></td></tr></table></td></tr></table></t=
d></tr></table></body></html>
----_NmP-1b607504ee83647a-Part_1--