Influxdata maintains a focused portfolio centered on time-series database and data collection products—InfluxDB and Telegraf—that are widely embedded in monitoring and observability infrastructure. The vendor's observed exposure clusters around authentication and input-handling issues, including improper authentication mechanisms, cross-site scripting in web interfaces, incorrect default permissions, and missing authentication controls on critical functions, reflecting the security challenges inherent to networked data ingestion and query systems. Current vulnerability severity, exploitation activity, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Influxdata over time
Signals from CVEs in this vendor scope (4 CVEs).
4 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2019-20933CRITICAL InfluxDB before 1.7.6 has an authentication bypass vulnerability in the authenticate function in services/httpd/handler.go because a JWT token may have an empty SharedSecret (aka s | Nov 19, 2020 | 9.8 | 59 | NO | YES |
CVE-2022-36640CRITICAL influxData influxDB before v1.8.10 contains no authentication mechanism or controls, allowing unauthenticated attackers to execute arbitrary commands. NOTE: the CVE ID assignment i | Sep 2, 2022 | 9.8 | 34 | NO | NO |
CVE-2020-35187CRITICAL The official telegraf docker images before 1.9.4-alpine (Alpine specific) contain a blank password for a root user. System using the telegraf docker container deployed by affected | Dec 17, 2020 | 9.8 | 30 | NO | NO |
CVE-2018-17572MEDIUM InfluxDB 0.9.5 has Reflected XSS in the Write Data module. | Mar 2, 2020 | 4.8 | 19 | NO | NO |
Signals from CVEs in this vendor scope (4 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Influxdata.
Media articles that mention a CVE ID that affects a product developed by Influxdata — matched by CVE ID, not by vendor name.