Grafana Mqtt Datasource cleartext credential exposure in broker connections
- Exploited
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Not reported
Summary
The Grafana Mqtt Datasource plugin does not apply TLS to broker connections when Private data source connect or a secure SOCKS proxy is used, so the broker username and password travel unencrypted between the proxy and the broker. An attacker on an adjacent network can read these credentials without logging in and without any user action.
Written by a model
Original description
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.
What to do
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-87956 (CVE-2026-87956 CVE Record), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-87956 (entry last updated 2026-11-19):
Affected:
- Grafana Mqtt Datasource: from 1.3.0, through 1.3.12
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-87956 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-87956 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://grafana.com/security/security-advisories/cve-2026-87956
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-87956
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-87956"}.Affected versions
- Grafana Mqtt DatasourceFrom 1.3.0 · through 1.3.12
cve.now Index
- Exploitation0/40No signal
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.1/10CVSS 6.1
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 33 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | grafana.com · security/security-advisories/cve-2026-87956 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-87956 |
| Record | NVD · CVE-2026-87956 |
Questions about CVE-2026-87956
Is CVE-2026-87956 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-87956?
Mqtt Datasource: from 1.3.0 through 1.3.12.
Source: cve.now feed data
Related
- CVE-2026-103506SSO settings authorization bypass
- CVE-2026-33379Dashboard snapshot permission bypass
- CVE-2026-81938Arbitrary file read via Alertmanager receiver configuration in Grafana Mimir
- CVE-2026-88967Azure Monitor access token disclosure via SSRF
- CVE-2026-106475Elasticsearch data source resource proxy allows arbitrary methods and paths with the data source's credentials
- CVE-2026-102589Cross-instance user impersonation through image renderer JWTs
No corrections so far. Something wrong on this page? Report an error.