p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in openssl · Seite 3

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für openssl: 14. Davon im KEV-Katalog: 0.

RSS ↗
Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 141

  1. CVE-2026-34180

    Hoch · CVSS 7.5EPSS 1,03%Korrektur verfügbar

    Heap Buffer Over-read in ASN.1 Content Parsing

    Issue summary: Parsing a crafted DER-encoded ASN.1 structure with a primitive element whose content exceeds 2 gigabytes in length may cause a heap buffer over-read on 64-bit Unix and Unix-like platforms. Impact summary: The heap buffer over-read may crash the application (Denial of Service) or to load into the decoded ASN.1 object contents of memory beyond the end of the input buffer. More typically such ASN.1 elements would instead be truncated. An integer truncation in OpenSSL's ASN.1 decoder causes the content length of an ASN.1 primitive element to be mishandled when it exceeds 2 gigabytes. In the worst case the truncated length is tre

    • Auf 1.0.2zq aktualisieren
    • Auf 1.1.1zh aktualisieren
    • Auf 3.0.21 aktualisieren
    • Auf 3.4.6 aktualisieren
    • Auf 3.5.7 aktualisieren
    • Auf 3.6.3 aktualisieren
    • Auf 4.0.1 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2026-9076

    Hoch · CVSS 7.5EPSS 0,71%Korrektur verfügbar

    Out-of-Bounds Read in CMS Password-Based Decryption

    Issue summary: When CMS password-based decryption (RFC 3211 / PWRI key unwrap) processes attacker-supplied CMS data, an attacker-chosen stream-mode KEK cipher can trigger a heap out-of-bounds read in kek_unwrap_key(). Impact summary: A heap buffer over-read may trigger a crash which leads to Denial of Service for an application if the input buffer ends at a memory page boundary and the following page is unmapped. There is no information disclosure as the over-read bytes are not revealed to the attacker. The key unwrapping function performs a check-byte test as specified in the RFC that reads 7 bytes from a heap allocation that is based on t

    • Auf 1.0.2zq aktualisieren
    • Auf 1.1.1zh aktualisieren
    • Auf 3.0.21 aktualisieren
    • Auf 3.4.6 aktualisieren
    • Auf 3.5.7 aktualisieren
    • Auf 3.6.3 aktualisieren
    • Auf 4.0.1 aktualisieren
    Veröffentlicht Aktualisiert
  3. CVE-2026-7383

    Hoch · CVSS 8.1EPSS 0,8%Korrektur verfügbar

    Possible Heap Buffer Overflow in ASN.1 Multibyte String Conversion

    Issue summary: A signed integer overflow when sizing the destination buffer for Unicode output in ASN1_mbstring_ncopy() can lead to a heap buffer overflow. Impact summary: A heap buffer overflow may lead to a crash or possibly attacker controlled code execution or other undefined behaviour. In ASN1_mbstring_copy() and ASN1_mbstring_ncopy() the destination size for Unicode output is computed in a signed int: by left shift of the input character count for BMPSTRING (UTF-16) and UNIVERSALSTRING (UTF-32), and by summing per-character byte counts for UTF8STRING. The calculation overflows when the input reaches around 2^30 characters. In the wors

    • Auf 1.0.2zq aktualisieren
    • Auf 1.1.1zh aktualisieren
    • Auf 3.0.21 aktualisieren
    • Auf 3.4.6 aktualisieren
    • Auf 3.5.7 aktualisieren
    • Auf 3.6.3 aktualisieren
    • Auf 4.0.1 aktualisieren
    Veröffentlicht Aktualisiert
  4. CVE-2026-31790

    Hoch · CVSS 7.5EPSS 1,03%Korrektur verfügbar

    Incorrect Failure Handling in RSA KEM RSASVE Encapsulation

    Issue summary: Applications using RSASVE key encapsulation to establish a secret encryption key can send contents of an uninitialized memory buffer to a malicious peer. Impact summary: The uninitialized buffer might contain sensitive data from the previous execution of the application process which leads to sensitive data leakage to an attacker. RSA_public_encrypt() returns the number of bytes written on success and -1 on error. The affected code tests only whether the return value is non-zero. As a result, if RSA encryption fails, encapsulation can still return success to the caller, set the output lengths, and leave the caller to use the

    • Auf 3.0.20 aktualisieren
    • Auf 3.3.7 aktualisieren
    • Auf 3.4.5 aktualisieren
    • Auf 3.5.6 aktualisieren
    • Auf 3.6.2 aktualisieren
    Veröffentlicht Aktualisiert
  5. CVE-2026-31789

    Mittel · CVSS 5.8EPSS 0,24%Korrektur verfügbar

    Heap Buffer Overflow in Hexadecimal Conversion

    Issue summary: Converting an excessively large OCTET STRING value to a hexadecimal string leads to a heap buffer overflow on 32 bit platforms. Impact summary: A heap buffer overflow may lead to a crash or possibly an attacker controlled code execution or other undefined behavior. If an attacker can supply a crafted X.509 certificate with an excessively large OCTET STRING value in extensions such as the Subject Key Identifier (SKID) or Authority Key Identifier (AKID) which are being converted to hex, the size of the buffer needed for the result is calculated as multiplication of the input length by 3. On 32 bit platforms, this multiplication

    • Auf 3.0.20 aktualisieren
    • Auf 3.3.7 aktualisieren
    • Auf 3.4.5 aktualisieren
    • Auf 3.5.6 aktualisieren
    • Auf 3.6.2 aktualisieren
    Veröffentlicht Aktualisiert
  6. CVE-2026-28390

    Hoch · CVSS 7.5EPSS 0,8%Korrektur verfügbar

    Possible NULL Dereference When Processing CMS KeyTransportRecipientInfo

    Issue summary: During processing of a crafted CMS EnvelopedData message with KeyTransportRecipientInfo a NULL pointer dereference can happen. Impact summary: Applications that process attacker-controlled CMS data may crash before authentication or cryptographic operations occur resulting in Denial of Service. When a CMS EnvelopedData message that uses KeyTransportRecipientInfo with RSA-OAEP encryption is processed, the optional parameters field of RSA-OAEP SourceFunc algorithm identifier is examined without checking for its presence. This results in a NULL pointer dereference if the field is missing. Applications and services that call CMS

    • Auf 1.0.2zp aktualisieren
    • Auf 1.1.1zg aktualisieren
    • Auf 3.0.20 aktualisieren
    • Auf 3.3.7 aktualisieren
    • Auf 3.4.5 aktualisieren
    • Auf 3.5.6 aktualisieren
    • Auf 3.6.2 aktualisieren
    Veröffentlicht Aktualisiert
  7. CVE-2026-28389

    Hoch · CVSS 7.5EPSS 0,8%Korrektur verfügbar

    Possible NULL Dereference When Processing CMS KeyAgreeRecipientInfo

    Issue summary: During processing of a crafted CMS EnvelopedData message with KeyAgreeRecipientInfo a NULL pointer dereference can happen. Impact summary: Applications that process attacker-controlled CMS data may crash before authentication or cryptographic operations occur resulting in Denial of Service. When a CMS EnvelopedData message that uses KeyAgreeRecipientInfo is processed, the optional parameters field of KeyEncryptionAlgorithmIdentifier is examined without checking for its presence. This results in a NULL pointer dereference if the field is missing. Applications and services that call CMS_decrypt() on untrusted input (e.g., S/MI

    • Auf 1.0.2zp aktualisieren
    • Auf 1.1.1zg aktualisieren
    • Auf 3.0.20 aktualisieren
    • Auf 3.3.7 aktualisieren
    • Auf 3.4.5 aktualisieren
    • Auf 3.5.6 aktualisieren
    • Auf 3.6.2 aktualisieren
    Veröffentlicht Aktualisiert
  8. CVE-2026-28388

    Hoch · CVSS 7.5EPSS 0,89%Korrektur verfügbar

    NULL Pointer Dereference When Processing a Delta CRL

    Issue summary: When a delta CRL that contains a Delta CRL Indicator extension is processed a NULL pointer dereference might happen if the required CRL Number extension is missing. Impact summary: A NULL pointer dereference can trigger a crash which leads to a Denial of Service for an application. When CRL processing and delta CRL processing is enabled during X.509 certificate verification, the delta CRL processing does not check whether the CRL Number extension is NULL before dereferencing it. When a malformed delta CRL file is being processed, this parameter can be NULL, causing a NULL pointer dereference. Exploiting this issue requires t

    • Auf 1.0.2zp aktualisieren
    • Auf 1.1.1zg aktualisieren
    • Auf 3.0.20 aktualisieren
    • Auf 3.3.7 aktualisieren
    • Auf 3.4.5 aktualisieren
    • Auf 3.5.6 aktualisieren
    • Auf 3.6.2 aktualisieren
    Veröffentlicht Aktualisiert
  9. CVE-2026-28387

    Hoch · CVSS 8.1EPSS 0,67%Korrektur verfügbar

    Potential Use-after-free in DANE Client Code

    Issue summary: An uncommon configuration of clients performing DANE TLSA-based server authentication, when paired with uncommon server DANE TLSA records, may result in a use-after-free and/or double-free on the client side. Impact summary: A use after free can have a range of potential consequences such as the corruption of valid data, crashes or execution of arbitrary code. However, the issue only affects clients that make use of TLSA records with both the PKIX-TA(0/PKIX-EE(1) certificate usages and the DANE-TA(2) certificate usage. By far the most common deployment of DANE is in SMTP MTAs for which RFC7672 recommends that clients treat a

    • Auf 1.1.1zg aktualisieren
    • Auf 3.0.20 aktualisieren
    • Auf 3.3.7 aktualisieren
    • Auf 3.4.5 aktualisieren
    • Auf 3.5.6 aktualisieren
    • Auf 3.6.2 aktualisieren
    Veröffentlicht Aktualisiert
  10. CVE-2026-28386

    Kritisch · CVSS 9.1EPSS 0,33%Korrektur verfügbar

    Out-of-bounds Read in AES-CFB-128 on X86-64 with AVX-512 Support

    Issue summary: Applications using AES-CFB128 encryption or decryption on systems with AVX-512 and VAES support can trigger an out-of-bounds read of up to 15 bytes when processing partial cipher blocks. Impact summary: This out-of-bounds read may trigger a crash which leads to Denial of Service for an application if the input buffer ends at a memory page boundary and the following page is unmapped. There is no information disclosure as the over-read bytes are not written to output. The vulnerable code path is only reached when processing partial blocks (when a previous call left an incomplete block and the current call provides fewer bytes t

    • Auf 3.6.2 aktualisieren
    Veröffentlicht Aktualisiert
  11. CVE-2026-2673

    Mittel · CVSS 6.5EPSS 0,51%Korrektur verfügbar

    OpenSSL TLS 1.3 server may choose unexpected key agreement group

    Issue summary: An OpenSSL TLS 1.3 server may fail to negotiate the expected preferred key exchange group when its key exchange group configuration includes the default by using the 'DEFAULT' keyword. Impact summary: A less preferred key exchange may be used even when a more preferred group is supported by both client and server, if the group was not included among the client's initial predicated keyshares. This will sometimes be the case with the new hybrid post-quantum groups, if the client chooses to defer their use until specifically requested by the server. If an OpenSSL TLS 1.3 server's configuration uses the 'DEFAULT' keyword to inter

    • Auf 3.5.6 aktualisieren
    • Auf 3.6.2 aktualisieren
    Veröffentlicht Aktualisiert
  12. CVE-2026-22796

    Mittel · CVSS 5.3EPSS 0,59%Korrektur verfügbar

    ASN1_TYPE Type Confusion in the PKCS7_digest_from_attributes() function

    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

    • Auf 1.0.2zn aktualisieren
    • Auf 1.1.1ze aktualisieren
    • Auf 3.0.19 aktualisieren
    • Auf 3.3.6 aktualisieren
    • Auf 3.4.4 aktualisieren
    • Auf 3.5.5 aktualisieren
    • Auf 3.6.1 aktualisieren
    Veröffentlicht Aktualisiert
  13. CVE-2026-22795

    Mittel · CVSS 5.5EPSS 0,17%Korrektur verfügbar

    Missing ASN1_TYPE validation in PKCS#12 parsing

    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 zer

    • Auf 1.1.1ze aktualisieren
    • Auf 3.0.19 aktualisieren
    • Auf 3.3.6 aktualisieren
    • Auf 3.4.4 aktualisieren
    • Auf 3.5.5 aktualisieren
    • Auf 3.6.1 aktualisieren
    Veröffentlicht Aktualisiert
  14. CVE-2025-69421

    Hoch · CVSS 7.5EPSS 0,94%Korrektur verfügbar

    NULL Pointer Dereference in PKCS12_item_decrypt_d2i_ex function

    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 th

    • Auf 1.0.2zn aktualisieren
    • Auf 1.1.1ze aktualisieren
    • Auf 3.0.19 aktualisieren
    • Auf 3.3.6 aktualisieren
    • Auf 3.4.4 aktualisieren
    • Auf 3.5.5 aktualisieren
    • Auf 3.6.1 aktualisieren
    Veröffentlicht Aktualisiert
  15. CVE-2025-69420

    Hoch · CVSS 7.5EPSS 0,92%Korrektur verfügbar

    Missing ASN1_TYPE validation in TS_RESP_verify_response() function

    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

    • Auf 1.1.1ze aktualisieren
    • Auf 3.0.19 aktualisieren
    • Auf 3.3.6 aktualisieren
    • Auf 3.4.4 aktualisieren
    • Auf 3.5.5 aktualisieren
    • Auf 3.6.1 aktualisieren
    Veröffentlicht Aktualisiert
  16. CVE-2025-69419

    Hoch · CVSS 7.4EPSS 0,61%Korrektur verfügbar

    Out of bounds write in PKCS12_get_friendlyname() UTF-8 conversion

    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 point can trigger a one byte 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. 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 capac

    • Auf 1.1.1ze aktualisieren
    • Auf 3.0.19 aktualisieren
    • Auf 3.3.6 aktualisieren
    • Auf 3.4.4 aktualisieren
    • Auf 3.5.5 aktualisieren
    • Auf 3.6.1 aktualisieren
    Veröffentlicht Aktualisiert
  17. CVE-2025-69418

    Mittel · CVSS 4EPSS 0,13%Korrektur verfügbar

    Unauthenticated/unencrypted trailing bytes with low-level OCB function calls

    Issue summary: When using the low-level OCB API directly with AES-NI or<br>other hardware-accelerated code paths, inputs whose length is not a multiple<br>of 16 bytes can leave the final partial block unencrypted and unauthenticated.<br><br>Impact summary: The trailing 1-15 bytes of a message may be exposed in<br>cleartext on encryption and are not covered by the authentication tag,<br>allowing an attacker to read or tamper with those bytes without detection.<br><br>The low-level OCB encrypt and decrypt routines in the hardware-accelerated<br>stream path process full 16-byte blocks but do not advance the input/output<br>pointers. The subseque

    • Auf 1.1.1ze aktualisieren
    • Auf 3.0.19 aktualisieren
    • Auf 3.3.6 aktualisieren
    • Auf 3.4.4 aktualisieren
    • Auf 3.5.5 aktualisieren
    • Auf 3.6.1 aktualisieren
    Veröffentlicht Aktualisiert
  18. CVE-2025-68160

    Mittel · CVSS 4.7EPSS 0,18%Korrektur verfügbar

    Heap out-of-bounds write in BIO_f_linebuffer on short writes

    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 larg

    • Auf 1.0.2zn aktualisieren
    • Auf 1.1.1ze aktualisieren
    • Auf 3.0.19 aktualisieren
    • Auf 3.3.6 aktualisieren
    • Auf 3.4.4 aktualisieren
    • Auf 3.5.5 aktualisieren
    • Auf 3.6.1 aktualisieren
    Veröffentlicht Aktualisiert
  19. CVE-2025-66199

    Mittel · CVSS 5.9EPSS 0,46%Korrektur verfügbar

    TLS 1.3 CompressedCertificate excessive memory allocation

    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 const

    • Auf 3.3.6 aktualisieren
    • Auf 3.4.4 aktualisieren
    • Auf 3.5.5 aktualisieren
    • Auf 3.6.1 aktualisieren
    Veröffentlicht Aktualisiert
  20. CVE-2025-15469

    Mittel · CVSS 5.5EPSS 0,21%Korrektur verfügbar

    'openssl dgst' one-shot codepath silently truncates inputs >16MB

    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 t

    • Auf 3.5.5 aktualisieren
    • Auf 3.6.1 aktualisieren
    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →