CVE-2026-71889 is a vulnerability in Bouncy Castle for Java before version 1.86 and certain LTS and FIPS releases, where improper certificate validation occurs due to failure to apply X.509 name constraints to the end-entity certificate. This flaw allows a certificate chain with a leaf certificate violating the NameConstraints extension imposed by its issuing CA to be incorrectly validated as trusted by the PKIXCertPathReviewer classes. The issue has been fixed in versions 1.86, 2.73.13, 2.1.13, 2.0.13, and 1.0.13.
CVE-2026-85087 is a medium severity vulnerability in Apache Thrift's Python bindings involving improper certificate validation and incorrect status code returns. This flaw affects versions before 0.25.0. The issue is resolved in Apache Thrift version 0.25.0. Users are advised to upgrade to this fixed version to mitigate the vulnerability.
CVE-2026-85086 is a medium severity vulnerability in Apache Thrift's Perl bindings involving improper certificate validation and insecure default resource initialization. It affects versions before 0.25.0. The issue is fixed in version 0.25.0, and users are advised to upgrade to this version to remediate the vulnerability.
Improper Validation of Certificate with Host Mismatch in the C++ and D libraries of Apache Thrift.
Both libraries install a default access manager for client sockets — TSSLSocketFactory does so in C++, and the accessManager property does so in D — which compares the peer certificate against the host
name that was connected to. That comparison walks the subjectAltName dNSName entries first and consults the certificate Common Name afterwards. A name that does not match yields a "skip" result rather than
a rejection, so a certificate whose subjectAltName entries are all present and all non-matching falls through to the Common Name, which can then satisfy the check.
RFC 6125 section 6.4.4, and RFC 9525 section 2, require that the Common Name is not consulted when a dNSName subjectAltName is present. A certificate carrying subjectAltName entries for one name and a
Common Name for another is therefore accepted for a connection to the second name.
Exploitation requires an attacker positioned on the network path who holds a certificate that chains to a certificate authority in the client's trust store and whose Common Name matches the connected host
name. Public certificate authorities have not issued on Common Name alone for many years, so this is principally a concern for deployments using a private or enterprise public-key infrastructure.
This issue affects the C++ library of Apache Thrift from 0.7.0 through 0.24.0 and the D library from 0.9.0 through 0.24.0. Users should upgrade to 0.25.0.
CVE-2026-80443 is an improper certificate validation vulnerability in HAVELSAN Inc.'s Sef - AI Chatbot Platform versions before 2.1. This flaw allows an adversary to perform Adversary in the Middle (AiTM) attacks by exploiting the failure to properly validate certificates. The product is no longer supported by the vendor. A fix is available in version 2.1.
Improper certificate validation in PkixNameConstraintValidator in Legion of the Bouncy Castle Inc. bc-csharp before 2.7.0 allows an attacker who controls, or can obtain certificates from, a name-constrained intermediate CA to have certificates accepted during PKIX certification path validation for email addresses, DNS names or URI hosts that lie within excluded subtrees applying to that CA, via an rfc822Name, dNSName or uniformResourceIdentifier name whose host ends with a dot, because names and constraints were compared without first removing the RFC 1034 root-label trailing dot, so a fully qualified host name did not match an excluded subtree for the same host written without the dot.
CVE-2026-63577 is a high-severity vulnerability in Legion of the Bouncy Castle Inc.'s bc-csharp library before version 2.7.0. It involves improper certificate validation in the directoryName name-constraint check during PKIX path validation. An attacker controlling or having certificates issued by a name-constrained intermediate CA can bypass constraints by manipulating the subject distinguished name or directoryName subjectAltName. This occurs because the validation incorrectly searches for the constraint's first RDN anywhere in the name rather than requiring it as an initial prefix, violating RFC 5280 requirements. The issue is fixed in version 2.7.0.
CVE-2026-63576 is a high-severity vulnerability in Legion of the Bouncy Castle Inc.'s bc-csharp library before version 2.7.0. It involves improper certificate validation in the PkixNameConstraintValidator component, specifically in the ExtractHostFromURL function. The flaw allows a name-constrained subordinate CA or an attacker with certificates containing crafted subjectAltName URIs to bypass URI name constraints during certification path validation. This occurs because the host extraction logic uses string slicing without properly isolating the RFC 3986 authority component, leading to incorrect host comparisons when URIs contain characters like '@' or ':'. The issue is fixed in version 2.7.0.
Joyland.ai contains a vulnerability where its app accepts invalid SSL certificates in the invisible advertisement WebView by default. This improper certificate validation is classified under CWE-295. The vulnerability has a medium severity with a CVSS score of 5.3 and does not affect confidentiality or availability but impacts integrity. All versions of Joyland.ai are affected. No patch or remediation guidance is currently provided.
Joyland.ai has a vulnerability (CVE-2026-102668) due to improper TLS certificate validation. The app accepts any TLS certificates from servers without validating them, which can undermine secure communications. This vulnerability has a medium severity with a CVSS score of 6.9. No patch or remediation information is currently available.
CVE-2026-15911 is a high-severity vulnerability in the Confluent Kafka Python client's integration with HashiCorp Vault KMS. It involves improper TLS certificate validation, which could allow a remote attacker to obtain sensitive information. The affected versions include all releases up to and including 2.14.2. No known exploits are reported in the wild, and no patch information is provided in the input data.
GraphQL Tools provides utilities for building, stitching, and mocking GraphQL schemas. Prior to 1.1.35, the executor-legacy-ws buildWSLegacyExecutor() function hardcodes TLS certificate rejection off for Node.js connections to wss:// endpoints. Applications using the executor directly, or url-loader with SubscriptionProtocol.LEGACY_WS, can therefore accept an attacker-controlled certificate when a network-positioned attacker intercepts the connection. Authentication material in connectionParams or headers can be disclosed, and subscription data can be modified. Browser WebSocket clients are unaffected because browsers enforce certificate validation. This issue is fixed in version 1.1.35.
Cato Windows SDP Client before version 6.12.6 contains an arbitrary file disclosure vulnerability. A low-privileged local user can cause the Windows service, running as Local System, to read and disclose arbitrary local files due to improper file path validation and missing TLS certificate enforcement.
Improper Verification of Cryptographic Signature and Improper Certificate Validation in the OPC UA driver of Apache PLC4X (PLC4J) allows an attacker in a network position between client and server to impersonate the OPC UA server and to read, forge or modify secure-channel traffic, including user credential ssent by the client.
The defect manifests differently depending on the version:
- In 0.9.0 through 0.11.0 a failed message-signature check is only logged and never enforced, and there is no mechanism to verify the server certificate: it is taken from the unauthenticated GetEndpoints discovery response and used to encrypt the user's password.
- In 0.12.0 through 0.13.1 the signature check is inverted (valid signatures are rejected, invalid ones accepted), and server certificates are accepted without a trust anchor by default.
- In all affected versions the default security policy is None. Starting with 0.12.0 the driver additionally continues silently at a weaker security policy than the one configured, and starting with 0.13.0 endpoint selection prefers the weakest matching endpoint.
Users checking only for one of these mechanisms may wrongly conclude they are unaffected.
This issue affects Apache PLC4X: from 0.9.0 before 1.0.0.
Users are recommended to upgrade to version 1.0.0, which fixes the issue. Version 1.0.0 verifies message signatures correctly, refuses to connect unless the server certificate can be verified against a configured trust store or pinned certificate, defaults to Basic256Sha256 with SignAndEncrypt, and fails the
connection if the negotiated security policy is weaker than the configured one.
CVE-2026-86131 is a critical code injection vulnerability in WatchGuard Fireware OS affecting the BOVPN Over TLS client configuration. An attacker controlling the remote VPN server can exploit this flaw to execute arbitrary commands with root privileges on the connecting Firebox device. The vulnerability affects multiple versions of Fireware OS prior to fixed releases. A high-severity CVSS score of 9.2 reflects the potential impact of remote, unauthenticated exploitation without user interaction. Fixed versions have been released by WatchGuard.
Dell Secure Connect Gateway (SCG) Policy Manager versions prior to 5.34.00.16 and prior to 5.36 contain an improper certificate validation vulnerability (CWE-295). This flaw allows an unauthenticated attacker with adjacent network access to potentially cause information disclosure, information tampering, and bypass protection mechanisms. The vulnerability has a CVSS 3.1 score of 6.4 (medium severity).
CVE-2026-101916 is a high-severity vulnerability in grpc-node's @grpc/grpc-js library where improper certificate validation occurs. Versions prior to 1.13.6 and between 1.14.0 and before 1.14.5 do not properly distinguish authorized from unauthorized peer certificates when server credentials have requireClientCertificate set to false. This can cause applications to mistakenly treat unauthorized certificates as authorized, leading to improper authentication. The issue also affects @grpc/grpc-js-xds when RBAC authentication is enabled. The vulnerability is fixed in versions 1.13.6 and 1.14.5.
Contrast before 1.16.0 is susceptible to remote attestation relay attacks. Contrast accepted any TEE attestation report that verified correctly and contained the expected firmware patch levels and software measurements, regardless of which machine produced it, so attestation was not bound to specific, physically trusted hardware. An attacker who can both intercept network traffic between the CLI and the Coordinator (or between the Coordinator and an attested component) and forge reports or extract secrets from any single TEE machine under their physical control can relay such a report to impersonate a Contrast Coordinator or a Contrast workload, defeating identity verification in Contrast's attested TLS (aTLS).
CVE-2026-93291 is a critical vulnerability in the Eufy Omni C20 device caused by improper certificate validation. This flaw allows an attacker to perform a man-in-the-middle (MitM) attack, potentially enabling arbitrary code execution on the device. Versions prior to 1.4.6 are affected. A fix is available in version 1.4.6.