According to the versions of the openssl packages installed, the EulerOS Virtualization installation on the remote host is affected by the following vulnerabilities :

    Issue summary: Use of the low-level GF(2^m) elliptic curve APIs with untrusted explicit values for the     field polynomial can lead to out-of-bounds memory reads or writes. Impact summary: Out of bound memory     writes can lead to an application crash or even a possibility of a remote code execution, however, in all     the protocols involving Elliptic Curve Cryptography that we're aware of, either only 'named curves' are     supported, or, if explicit curve parameters are supported, they specify an X9.62 encoding of binary     (GF(2^m)) curves that can't represent problematic input values. Thus the likelihood of existence of a     vulnerable application is low. In particular, the X9.62 encoding is used for ECC keys in X.509     certificates, so problematic inputs cannot occur in the context of processing X.509 certificates. Any     problematic use-cases would have to be using an 'exotic' curve encoding. The affected APIs include:
    EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params(), and various supporting BN_GF2m_*() functions.
    Applications working with 'exotic' explicit binary (GF(2^m)) curve parameters, that make it possible to     represent invalid field polynomials with a zero constant term, via the above or similar APIs, may     terminate abruptly as a result of reading or writing outside of array bounds. Remote code execution cannot     easily be ruled out. The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this     issue.(CVE-2024-9143)

    Issue summary: A timing side-channel which could potentially allow recovering the private key exists in     the ECDSA signature computation. Impact summary: A timing side-channel in ECDSA signature computations     could allow recovering the private key by an attacker. However, measuring the timing would require either     local access to the signing application or a very fast network connection with low latency. There is a     timing signal of around 300 nanoseconds when the top word of the inverted ECDSA nonce value is zero. This     can happen with significant probability only for some of the supported elliptic curves. In particular the     NIST P-521 curve is affected. To be able to measure this leak, the attacker process must either be located     in the same physical computer or must have a very fast network connection with low latency. For that     reason the severity of this vulnerability is Low.(CVE-2024-13176)

    Issue summary: An application trying to decrypt CMS messages encrypted using password based encryption can     trigger an out-of-bounds read and write.Impact summary: This out-of-bounds read may trigger a crash which     leads to Denial of Service for an application. 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.Although the consequences of a successful exploit of this vulnerability could be severe, the     probability that the attacker would be able to perform it is low. Besides, password based (PWRI)     encryption support in CMS messages is very rarely used. For that reason the issue was assessed as Moderate     severity according to our Security Policy.The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not     affected by this issue, as the CMS implementation is outside the OpenSSL FIPS module     boundary.(CVE-2025-9230)

    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 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 and the attacker can just trigger a one     zero byte write before the allocated buffer.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 and 1.1.1 are vulnerable to this issue.OpenSSL 1.0.2 is not affected by this     issue.(CVE-2025-69419)

    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.(CVE-2025-69421)

    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.(CVE-2025-69420)

    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.(CVE-2026-22796)

    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.(CVE-2025-68160)

    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.(CVE-2026-22795)

    Issue summary: When using the low-level OCB API directly with AES-NI orbrother hardware-accelerated     code paths, inputs whose length is not a multiplebrof 16 bytes can leave the final partial block     unencrypted and unauthenticated.brbrImpact summary: The trailing 1-15 bytes of a message may     be exposed inbrcleartext on encryption and are not covered by the authentication     tag,brallowing an attacker to read or tamper with those bytes without detection.brbrThe     low-level OCB encrypt and decrypt routines in the hardware-acceleratedbrstream path process full     16-byte blocks but do not advance the input/outputbrpointers. The subsequent tail-handling code then     operates on the originalbrbase pointers, effectively reprocessing the beginning of the buffer     whilebrleaving the actual trailing bytes unprocessed. The authentication checksumbralso     excludes the true tail bytes.brbrHowever, typical OpenSSL consumers using EVP are not affected     because thebrhigher-level EVP and provider OCB implementations split inputs so that     fullbrblocks and trailing partial blocks are processed in separate calls, avoidingbrthe     problematic code path. Additionally, TLS does not use OCB ciphersuites.brThe vulnerability only     affects applications that call the low-levelbrCRYPTO_ocb128_encrypt() or CRYPTO_ocb128_decrypt()     functions directly withbrnon-block-aligned lengths in a single call on hardware-accelerated     builds.brFor these reasons the issue was assessed as Low severity.brbrThe FIPS modules     in 3.6, 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affectedbrby this issue, as OCB mode is not a FIPS-     approved algorithm.brbrOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this     issue.brbrOpenSSL 1.0.2 is not affected by this issue.(CVE-2025-69418)

    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 the X509_V_FLAG_USE_DELTAS flag to be enabled in the verification context, the certificate being     verified to contain a freshestCRL extension or the base CRL to have the EXFLAG_FRESHEST flag set, and an     attacker to provide a malformed CRL to an application that processes it.The vulnerability is limited to     Denial of Service and cannot be escalated to achieve code execution or memory disclosure. 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 affected code is outside the OpenSSL FIPS module     boundary.(CVE-2026-28388)

    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/MIME processing or CMS-based protocols) are vulnerable.The FIPS modules in 3.6, 3.5, 3.4,     3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module     boundary.(CVE-2026-28389)

    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_decrypt() on untrusted input (e.g., S/MIME processing or CMS-based protocols) are     vulnerable.The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected     code is outside the OpenSSL FIPS module boundary.(CVE-2026-28390)

    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 as 'unusable' any TLSA records that have the PKIX certificate usages.  These SMTP (or     other similar) clients are not vulnerable to this issue.  Conversely, any clients that support only the     PKIX usages, and ignore the DANE-TA(2) usage are also not vulnerable.The client would also need to be     communicating with a server that publishes a TLSA RRset with both types of TLSA records.No FIPS modules     are affected by this issue, the problem code is outside the FIPS module boundary.(CVE-2026-28387)

Tenable has extracted the preceding description block directly from the EulerOS Virtualization openssl security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

Detections

Analytics

EulerOS Virtualization 2.11.1 : openssl (EulerOS-SA-2026-3448)

high Nessus Plugin ID 347127

Version 1.2

Version 1.1

Version 1.2 Sep 21, 2026, 3:50 PM CVSS metrics ("CVSSv2 score" set to 7.6) CVSS metrics ("CVSSv2 vector" set to "CVSS2#AV:N/AC:H/Au:N/C:C/I:C/A:C") CVSS metrics ("CVSSv3 score" set to 8.1) CVSS metrics ("CVSSv3 vector" set to "CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H") CVSSv2 score source (changed from "CVE-2024-9143" to "CVE-2026-28387") CVSSv2 severity (based on CVE-2026-28387, severity increased from "Medium" to "High") CVSSv3 severity (based on None, severity increased from "Medium" to "High") Plugin Feed: 202609211550
Version 1.1 Sep 18, 2026, 2:17 PM New Plugin Feed: 202609181417