Eclipse Ditto's Node.js JavaScript client versions from 2.0.0 up to but not including 3.8.1, versions 3.9.0 up to but not including 3.9.1, and the predecessor package from 1.0.0 through 2.1.0 have a vulnerability where TLS certificate validation is disabled for WebSocket connections. This allows an attacker who can intercept the connection to present any certificate, bypass validation, and potentially read or alter sensitive protocol messages. Other clients and transports of Eclipse Ditto are not affected.
Dell Secure Connect Gateway (SCG) 5.0 Appliance and Application versions prior to 5.36.00.16 and 5.36.00.00 respectively contain an improper certificate validation vulnerability. This flaw could allow an unauthenticated remote attacker to gain unauthorized access. The vulnerability is identified as CWE-295 and has a high severity with a CVSS score of 7.6. No official patch or remediation details are provided in the input data.
Dell SCG 5.0 Appliance versions prior to 5.36.00.16 and Dell SCG 5.0 Application versions prior to 5.36.00.00, contains an Improper Certificate Validation vulnerability. An unauthenticated attacker with remote access could potentially exploit this vulnerability, leading to unauthorized access.
Dell Secure Connect Gateway (SCG) 5.0 Application versions prior to 5.36.00.00 and Appliance versions prior to 5.36.00.16 contain an improper certificate validation vulnerability. This flaw allows a low privileged attacker with local access to potentially exploit server-side request forgery. The vulnerability is identified as CWE-295 and has a CVSS 3.1 score of 5.5, indicating medium severity. No official patch or remediation details are provided in the available data.
Dell SCG 5.0 Appliance versions prior to 5.36.00.16 and Dell SCG 5.0 Application versions prior to 5.36.00.00, contains an Improper Certificate Validation vulnerability. An unauthenticated attacker with remote access could potentially exploit this vulnerability, leading to unauthorized access.
Dell Secure Connect Gateway (SCG) 5.0 versions prior to 5.36.00.16 for the appliance and prior to 5.36.00.00 for the application contain an improper certificate validation vulnerability. This flaw allows an unauthenticated remote attacker to potentially bypass protection mechanisms. The vulnerability is identified as CWE-295 and has a CVSS 3.1 base score of 7.3, indicating high severity. No official patch links are provided in the available data.
Dell Secure Connect Gateway (SCG) 5.0 Appliance and Application versions prior to 5.36.00.16 and 5.36.00.00 respectively contain an improper certificate validation vulnerability. This flaw allows an unauthenticated remote attacker to potentially gain unauthorized access. The vulnerability is identified as CWE-295 and has a high severity with a CVSS score of 7.4. No explicit patch or remediation details are provided in the available data.
Dell Secure Connect Gateway (SCG) 5.0 Appliance and Application versions prior to 5.36.00.16 and 5.36.00.00 respectively contain an improper certificate validation vulnerability. This flaw allows an unauthenticated remote attacker to potentially bypass protection mechanisms. The vulnerability is identified as CWE-295 and has a medium severity with a CVSS score of 5.9. No known exploits are reported in the wild. Patch information is not provided in the source data.
Dell Secure Connect Gateway (SCG) 5.0 Appliance and Application versions prior to 5.36.00.16 and 5.36.00.00 respectively contain an improper certificate validation vulnerability. This flaw could allow an unauthenticated remote attacker to gain unauthorized access. The vulnerability is rated high severity with a CVSS score of 7.4. No official patch or vendor advisory details are provided in the input data.
CVE-2026-20500 is a vulnerability in MediaTek chipsets caused by improper certificate validation in the modem component. This flaw can lead to a system crash resulting in a local denial of service. Exploitation requires user execution privileges and user interaction. A patch identified as MOLY01810811 addresses this issue.
Improper certificate validation in Checkmk <2.5.0p10 allows a relay and a push agent that share the same UUID to reuse each other's mTLS certificate to authenticate against agent receiver endpoints in either direction, because the endpoints do not verify that the certificate was issued by their own root certificate.
IBM Netezza Software 11.3.0.3 through Interim Fix 002 does not validate or improperly validates TLS certificate validation, which could allow an attacker to obtain sensitive information using man in the middle techniques.
In the current development version of Eclipse aeriOS, for which no official release has yet been published, the Federator component disables TLS certificate validation for outbound HTTPS connections by default. When the TLS_CERTIFICATE_VALIDATION environment variable is unset or set to false, the component configures its HTTP transport to skip TLS certificate verification.
As a result, an attacker able to intercept network communications between the Federator and external services could impersonate those services and intercept sensitive information transmitted over HTTPS, including OAuth client credentials and bearer tokens.
The issue has been addressed by enabling TLS certificate validation by default. The TLS_CERTIFICATE_VALIDATION environment variable is now set to true in the default configuration provided by the Helm chart and Docker Compose deployment.
In Eclipse Arrowhead versions from 5.0.0 to 5.2.1 when the MQTT API is enabled with the certificate authentication policy, CertificateMqttFilter parses an X.509 certificate that the client sends inside the MQTT message payload (the authentication field of MqttRequestTemplate) and treats its Subject DN as the authenticated identity. The certificate is decoded with CertificateFactory.generateCertificate() but its signature is never verified and its issuer chain is never validated against any trust store. Authorisation is reduced to two string comparisons on attacker-supplied data: the DN-qualifier must equal "sy" or "op", and the cloud-name part of the CN must match the server's. Both values are public (the cloud name is in the server's own TLS certificate). An attacker who can publish to the MQTT broker can therefore mint a self-signed certificate with CN=Sysop.<cloud>.<org>.arrowhead.eu, dnQualifier=op, send it as the authentication field, and be authenticated as the cloud's system operator with isSysOp == true. This passes the downstream ManagementServiceMqttFilter (request.isSysOp() → allowed) and gives full management access over MQTT. The HTTP CertificateFilter is not affected — it reads the certificate from jakarta.servlet.request.X509Certificate, which Tomcat populates only after a successful mTLS handshake against the configured trust store.
In the current development version of Eclipse aeriOS, which has not yet had an official release, the KrakenD instance included in the API Gateway component had the disable_jwk_security parameter hard-coded to true, with no option to override it through the Helm chart configuration. This setting disables TLS certificate verification when KrakenD retrieves the JSON Web Key Set (JWKS) used to validate bearer tokens, potentially allowing an attacker with the ability to intercept this communication to provide a malicious JWKS and compromise token validation.
The issue has been addressed by making the parameter configurable through the boolean Helm value krakend.config.disableJwkSecurity and setting its default value to false, ensuring that TLS certificate verification is enabled by default.
CVE-2026-41012 is a vulnerability in the Cloud Foundry bosh-vsphere-cpi-release component that allows an attacker intercepting traffic between BOSH Director and vCenter to impersonate the vCenter REST API. This impersonation enables the attacker to capture administrator credentials transmitted via HTTP Basic authentication, leading to full control over the virtualization infrastructure managed by vCenter. The root cause is improper certificate validation, allowing successful man-in-the-middle attacks despite HTTPS usage. This affects all CPI calls and cannot be mitigated by supplying a CA certificate alone.
IBM Concert versions 1.0.0 through 2.3.1 contain an improper certificate validation vulnerability that could allow a remote attacker to perform unauthorized actions via man-in-the-middle techniques. The vulnerability is identified as CWE-295 and has a medium severity with a CVSS score of 5.9. No official patch or remediation guidance is currently available from the vendor. No known exploits are reported in the wild.
IBM Integrated Analytics System versions 1.0.0.0 through 1.0.31.0 contain a vulnerability due to improper TLS certificate validation. This flaw could allow an attacker to intercept sensitive information via man-in-the-middle techniques. The vulnerability is identified as CWE-295 and has a medium severity with a CVSS score of 5.9.
CVE-2026-81518 is a high-severity vulnerability in the MongoDB BI Connector where improper certificate validation occurs. Specifically, when mongosqld is configured with a client certificate authority file, it requests but does not require a client certificate during the TLS handshake. This allows clients without certificates to connect. In environments relying solely on client certificates for user identification, this flaw enables unauthorized remote parties with network access to read MongoDB data exposed through the connector.
MariaDB Connector/Node.js versions prior to 3.3.3, 3.4.6, and 3.5.3 have an improper certificate validation vulnerability. When SSL is enabled without a pinned CA or server certificate, the connector may send credentials before completing certificate fingerprint validation. This allows a man-in-the-middle attacker to present a self-signed certificate, capture the database password, and authenticate directly even though the connection is later closed. The issue is fixed in versions 3.3.3, 3.4.6, and 3.5.3.