CVE-2026-87956: CVE Record
When Private data source connect (PDC) or a secure SOCKS proxy is used, the MQTT data source plugin does not apply TLS to broker connections for the tls, ssl, tcps, mqtts and mqtt+ssl schemes. The configured TLS settings are ignored, and the broker username and password are sent unencrypted on the hop between the proxy and the broker. The server certificate is not verified, and a configured client certificate is not sent.
Event History
Frequently Asked Questions
Which deployments are exposed?
Deployments using the MQTT data source plugin through a Private data source connect (PDC) connection or a secure SOCKS proxy are exposed when the broker URL uses tls, ssl, tcps, mqtts, or mqtt+ssl schemes.
What access would an attacker need to exploit this?
An attacker would need the ability to observe or intercept traffic on the network hop between the proxy and the MQTT broker. On that hop, the broker username and password are sent without encryption.
How can I determine whether TLS protections are actually in effect?
For affected proxy-based connections, configured TLS settings are ignored: the broker certificate is not verified and any configured client certificate is not sent. Review MQTT data source connections using PDC or a secure SOCKS proxy rather than relying on their configured TLS options.