CVE-2022-36640 json
influxData influxDB before v1.8.10 contains no authentication mechanism or controls, allowing unauthenticated attackers to execute arbitrar…
published 2022-09-02 4 y ago modified 2026-09-08 2 mo ago also BIT-influxdb-2022-36640 , EUVD-2022-39343
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.6%
- EPSS 2.6% chance of exploitation in 30 days, percentile 85%
- public exploits
- 0
- none known
Summary
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."
Patch / fix
- bitnami influxdb 1.8.0
- influxdata influxdb 1.8.0
Exploit prediction
2.57% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| OSV | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | influxdb | <1.8.0 |
1.8.0 |
Classification
- Weakness
-
- CWE-276 Incorrect Default Permissions
References
-
dl.influxdata.com
/influxdb/releases/influxdb_1.8.10_amd64.deb
patch, vendor-advisory, advisory
-
portal.influxdata.com
/downloads/
patch, product
-
krsecu.com
/CVE/409b5310045bd6b9a984a5fb63bd8786d5c5681a8ad5b1c815c84b2b90002ad7.docx
broken-link, web
-
influxdata.com
/
product, web
-
influxdata.com
web
-
influxdb.com
web
-
nvd.nist.gov
/vuln/detail/CVE-2022-36640
web
Sources
- CVE List CVE-2022-36640
- NVD CVE-2022-36640
- OSV BIT-influxdb-2022-36640
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.