Influxdata Influxdb
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in Influxdata Influxdb.
By the Year
In 2026 there have been 0 vulnerabilities in Influxdata Influxdb. Influxdb did not have any published security vulnerabilities last year.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2026 | 0 | 0.00 |
| 2025 | 0 | 0.00 |
| 2024 | 1 | 9.10 |
| 2023 | 0 | 0.00 |
| 2022 | 1 | 9.80 |
| 2021 | 0 | 0.00 |
| 2020 | 2 | 4.80 |
It may take a day or so for new Influxdb vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Influxdata Influxdb Security Vulnerabilities
InfluxDB: Privilege Escalation via Raw Token Retrieval
CVE-2024-30896
9.1 - Critical
- November 21, 2024
InfluxDB OSS 2.x through 2.7.11 stores the administrative operator token under the default organization which allows authorized users with read access to the authorization resource of the default organization to retrieve the operator token. InfluxDB OSS 1.x, Enterprise, Cloud, Cloud Dedicated and Clustered are not affected. NOTE: The researcher states that InfluxDB allows allAccess administrators to retrieve all raw tokens via an "influx auth ls" command. The supplier indicates that the organizations feature is operating as intended and that users may choose to add users to non-default organizations. A future release of InfluxDB 2.x will remove the ability to retrieve tokens from the API. The supplier has stated that InfluxDB 2.8.0 has addressed this issue.
Insecure Storage of Sensitive Information
Unauth Cmd Exec in InfluxDB <1.8.10 (v1.8.9)
CVE-2022-36640
9.8 - Critical
- September 02, 2022
influxData influxDB before v1.8.10 contains no authentication mechanism or controls, allowing unauthenticated attackers to execute arbitrary commands. NOTE: the CVE ID assignment is disputed because the vendor's documentation states "If InfluxDB is being deployed on a publicly accessible endpoint, we strongly recommend authentication be enabled. Otherwise the data will be publicly available to any unauthenticated user. The default settings do NOT enable authentication and authorization.
Incorrect Default Permissions
InfluxDB before 1.7.6 has an authentication bypass vulnerability in the authenticate function in services/httpd/handler.go
CVE-2019-20933
- November 19, 2020
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 shared secret).
InfluxDB 0.9.5 has Reflected XSS in the Write Data module.
CVE-2018-17572
4.8 - Medium
- March 02, 2020
InfluxDB 0.9.5 has Reflected XSS in the Write Data module.
XSS
Stay on top of Security Vulnerabilities
Want an email whenever new vulnerabilities are published for Influxdata Influxdb or by Influxdata? Click the Watch button to subscribe.
