CVE-2026-83926 is a vulnerability in Microsoft Windows 10 Version 1809 related to improper certificate validation in Windows Hello. This flaw allows a local authorized attacker to bypass a security feature. The vulnerability has a medium severity rating with a CVSS score of 4.4. Microsoft has released official fixes for affected versions.
CVE-2026-108185 is a high-severity vulnerability in Zoom Clients involving improper certificate validation in the My Notes feature. This flaw may allow an unauthenticated attacker with network access to disclose sensitive information. The vulnerability does not require user interaction or privileges but has a high attack complexity. No patch or remediation details are provided in the available data.
CVE-2026-108184 is a high-severity vulnerability in certain Zoom Clients for Windows involving improper certificate validation. This flaw may allow an unauthenticated attacker with network access to disclose sensitive information. The vulnerability does not require user interaction and has a high impact on confidentiality. No affected versions or patch information are provided in the available data.
CVE-2026-78556 is a vulnerability in Siemens Industrial Edge App Publisher versions prior to 1.27.9. The software fails to properly validate server certificates during TLS connections, enabling potential Man-in-the-Middle (MitM) attacks where an attacker can intercept or spoof communications. This flaw affects all versions from 0 up to but not including 1.27.9. The vulnerability has a high severity rating with a CVSS score of 7.4.
IBM DataStage on Cloud Pak for Data 5.4.0.0 can allow a man-in-the-middle attacker to present a forged TLS certificate, intercept the connection, and capture the IAM bearer Authorization header automatically attached by the session adapter. The captured token grants full platform-scope tenant API access, enabling the attacker to read and manipulate the victim's DataStage projects, flows, assets, and pipeline definitions. This is client-side SDK code running on the user's own machine, so exploitation requires an external network interceptor rather than a co-tenant in the shared cluster.
FreeRDP versions before 3.32.0, including 3.0.0, have an improper certificate validation vulnerability in the TLS handshake process. This flaw occurs in the freerdp_http_request() function, which completes TLS handshakes without properly verifying the server certificate chain. An on-path attacker could exploit this to impersonate login.microsoftonline.com during the Azure AD authentication flow, potentially capturing OAuth authorization codes and substituting the OpenID discovery document.
CVE-2026-103503 is an improper certificate validation vulnerability in hexpm hex affecting versions from 0.20.2 up to but not including 2.5.2. The issue arises when the software uses a custom CA certificate store (cacerts_path) that excludes a CA present in Hex's bundled CA store. The verification logic incorrectly accepts server certificate chains containing certificates with public keys matching those in the bundled CA store, even if the configured CA store does not trust that CA. Hostname verification remains enforced. This flaw could allow an attacker who intercepts HTTPS connections and possesses a certificate issued by a CA in the bundled store to impersonate a Hex host to users relying on a custom CA store that excludes that CA.
CVE-2026-103502 is an improper certificate validation vulnerability in the hexpm hex_core library affecting versions from 0.1.0 up to but not including 0.20.0. The issue arises because hex_core's default HTTP adapter on Erlang/OTP 24 and OTP 25 (when the OS CA certificates cannot be loaded) does not verify server certificates properly, allowing an attacker who can intercept HTTPS connections to impersonate hex.pm or related repositories. The vulnerability stems from fallback behavior that disables certificate verification without clear documentation or warnings. hex_core 0.11.0 introduced secure SSL defaults for OTP 25+, but earlier versions and certain OTP configurations remain vulnerable. The CVSS 4.0 score is 5.9 (medium severity).
Dell Secure Connect Gateway (SCG) Policy Manager versions prior to 5.34.00.16 have an improper certificate validation vulnerability (CWE-295). This flaw allows an unauthenticated remote attacker to potentially cause denial of service, disclose information, or execute code remotely. The vulnerability has a high severity with a CVSS score of 7.5. No patch information is provided in the input data.
CVE-2026-96207 is a critical vulnerability in Microsoft Partner Center involving improper certificate validation. This flaw allows an unauthorized attacker to elevate privileges over a network, potentially gaining high confidentiality and integrity impact. An official fix is available from Microsoft.
Improper certificate validation in the webmail of Progressive Robot hMailServer 6.3.2 through 6.3.5 allows a remote unauthenticated attacker to have S/MIME-encrypted mail that the account later sends to another correspondent also encrypted to the attacker's key. When its recipient opened a signed message, the webmail kept the signer's certificate for encrypting replies whether or not the server found its chain trusted, under the first e-mail address the certificate listed rather than the message's From address, and beside any certificate already held for that address. Encrypted mail later sent from the webmail to that address was encrypted to every certificate held for it, so a holder of the kept certificate's key who obtains a copy of such a message can read it.
An unauthenticated remote attacker can modify the TLS client trust store in Brocade ASCG versions before 3.5.0. By supplying an unauthorized Certificate Authority (CA) certificate to an unauthenticated management interface, the attacker can cause the system to trust unauthorized certificates, potentially enabling Man-in-the-Middle (MITM) attacks against outbound communications with managed switches and peer nodes.
Docker Engine classifies a registry hostname as insecure using an any-match DNS check. loadInsecureRegistries() injects 127.0.0.0/8 and ::1/128 as insecure CIDRs by default. isCIDRMatch resolves all of the hostname's addresses and returns true if a single address is in the insecure CIDR list. Because the transport re-dials the hostname rather than the CIDR-matching address, a DNS answer set of one loopback IP plus a non-loopback attacker IP disables certificate verification and enables HTTP fallback for the registry connection.
Dell System Update versions prior to 2.3.0.0 contain an improper certificate validation vulnerability (CWE-295). This flaw could allow a highly privileged remote attacker to execute code remotely. The vulnerability is rated high severity with a CVSS score of 7.6. No patch or remediation details are provided in the input data.
Dell Container Storage Modules (CSM) versions prior to 1.18.0 contain an improper certificate validation vulnerability in the proxy-server component. This flaw could allow an unauthenticated attacker on an adjacent network to expose storage backend administrator credentials. The vulnerability is identified as CWE-295 and has a high severity rating with a CVSS score of 8.2.
MsQuic is a cross-platform C implementation of the IETF QUIC protocol exposed to C, C++, C#, and Rust. Prior to 2.4.20, 2.5.11, and 2.6.1, MsQuic clients using the OpenSSL or QuicTLS TLS backend do not properly verify that a server certificate matches the intended target server hostname. An on-path attacker can therefore present a certificate that does not match the intended target hostname and spoof the server in a man-in-the-middle attack. The Schannel backend is not affected. This issue is fixed in versions 2.4.20, 2.5.11, and 2.6.1.
Bouncy Castle for Java versions before 1.86 and certain LTS and FIPS versions contain a vulnerability in the PKIXCertPathReviewer classes where X.509 name constraints were not applied to the end-entity (leaf) certificate. This caused the validation to incorrectly accept certificate chains whose leaf certificates violated name constraints imposed by their issuing CA. The issue affects both the modern and legacy PKIXCertPathReviewer implementations and was fixed by ensuring all certificates in the path, including the leaf, are checked according to RFC 5280 requirements.
CVE-2026-71885 is a critical vulnerability in Bouncy Castle for Java (BC-JAVA) versions before 1.86 affecting the Messaging Layer Security (MLS) implementation. The flaw involves improper certificate validation where the X.509 certificate chain is not properly bound to the LeafNode's signature key, allowing an attacker to impersonate another party's identity within a group. This can lead to unauthorized admission, eviction of legitimate members, and decryption and injection of group messages. The issue is fixed in version 1.86 by enforcing that the end-entity certificate's public key matches the signature key as required by RFC 9420. Deployments using only basic credentials are not affected.