CVE-2022-36640

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.

Published: 2022-09-02 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-36640 is rated High Risk (70.2/100): CVSS Critical severity, with high exploitation likelihood (EPSS 6.79%, 91th percentile). EPSS ranks this CVE among the most likely to be exploited in the near term. High exploitation likelihood—assess exposure and prioritize remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2022-36640

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-04 7.73% 6.79% -0.94%
2 2026-03-01 6.79% 7.73% +0.94%
3 2026-02-26 — 6.79% —

Full EPSS history (50 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-36640

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 [email protected]

Weakness enumeration for CVE-2022-36640

OS Trackers for CVE-2022-36640

vendor priority summary link
debian unimportant CVE-2022-36640 unimportant priority: Debian including 1 source packages (influxdb), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 5. https://security-tracker.debian.org/tracker/CVE-2022-36640
suse — CVE-2022-36640 severity not set: SUSE including 1 source package names (influxdb), 5 product×package rows across 5 product lines (HPE Helion OpenStack 8, SUSE OpenStack Cloud 8, … (5 product lines)): Will Not Fix 5. https://www.suse.com/security/cve/CVE-2022-36640/
ubuntu negligible CVE-2022-36640 negligible priority: Ubuntu including 1 source packages (influxdb), 10 status rows across 10 suites (bionic, focal, jammy, kinetic, lunar, mantic, noble, trusty, upstream, xenial): not-affected 5, ignored 4, needs-triage 1. https://ubuntu.com/security/CVE-2022-36640

Affected software / configurations for CVE-2022-36640

Vendor Product Version Raw CPE
influxdata influxdb < 1.8.0 cpe:2.3:a:influxdata:influxdb:*:*:*:*:*:*:*:*

References for CVE-2022-36640

cvelogic Threat Intelligence