CVE-2018-8007

HIGHNVD 7.27.2
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 7.2 from GitHub Security Advisory (severity: HIGH) published 2022-05-14. NVD baseline CVSS 7.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated
7.2EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 12%CVSS: 7.2Exploit: No code on recordExposed services: Not assessed

The CVE record names the fixed release — apply it.

Apache CouchDB administrative users can configure the database server via HTTP(S). Due to insufficient validation of administrator-supplied configuration settings via the HTTP API, it is possible for a CouchDB administrator user to escalate their privileges to that of the operating system's user that CouchDB runs under, by bypassing the blacklist of configuration settings that are not allowed to be modified via the HTTP API. This privilege escalation effectively allows an existing CouchDB admin user to gain arbitrary remote code execution, bypassing already disclosed CVE-2017-12636. Mitigation: All users should upgrade to CouchDB releases 1.7.2 or 2.1.2.

CVSS v3
7.2
EG Score
7.2HIGHmedium confidence
EG Risk
48
EG Risk 48/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity72% × 45%
The EG Score, 7.2 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The CVE record names the fixed release. Apply it within your standard update timelines.
EPSS PROB
12%
EPSS %ILE
96th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

The CVE record names the fixed release. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 11, 2018

Last Modified

November 21, 2024

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 27× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 89 of 151 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 11 repeat rows among the latest 100 are merged into the row they repeat. The 62 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-12 20:07 UTCEG score recompute
  2. 2026-10-12 16:28 UTCEPSS rescoreEPSS 12% · 96th percentile
  3. 2026-10-12 00:31 UTCEG score recompute
  4. 2026-10-11 13:41 UTCEPSS rescoreEPSS 12% · 95th percentile
  5. 2026-10-10 19:55 UTCEPSS rescoreEPSS 12% · 95th percentile
  6. 2026-10-09 20:03 UTCEPSS rescoreEPSS 12% · 95th percentile
  7. 2026-10-08 16:37 UTCEPSS rescoreEPSS 12% · 95th percentile
  8. 2026-10-07 23:42 UTCEPSS rescoreEPSS 12% · 95th percentile
  9. 2026-10-06 15:12 UTCEPSS rescoreEPSS 12% · 95th percentile
  10. 2026-10-05 17:39 UTCEPSS rescoreEPSS 12% · 95th percentile
  11. 2026-10-03 14:21 UTCEPSS rescoreEPSS 12% · 95th percentile
  12. 2026-10-01 19:44 UTCEPSS rescoreEPSS 12% · 95th percentile
  13. 2026-09-30 14:59 UTCEPSS rescoreEPSS 12% · 95th percentile
  14. 2026-09-30 10:05 UTCEG score recompute
  15. 2026-09-29 15:12 UTCEPSS rescoreEPSS 12% · 95th percentile
  16. 2026-09-28 23:08 UTCOSV refresh
  17. 2026-09-28 13:46 UTCEPSS rescoreEPSS 12% · 95th percentile
  18. 2026-09-27 13:40 UTCEPSS rescoreEPSS 12% · 95th percentile
  19. 2026-09-26 15:53 UTCEPSS rescoreEPSS 12% · 95th percentile
  20. 2026-09-24 13:59 UTCEPSS rescoreEPSS 12% · 95th percentile
  21. 2026-09-23 13:42 UTCEPSS rescoreEPSS 12% · 95th percentile
  22. 2026-09-21 20:27 UTCEPSS rescoreEPSS 11% · 95th percentile
  23. 2026-09-19 15:36 UTCEPSS rescoreEPSS 12% · 95th percentile
  24. 2026-09-18 19:22 UTCEPSS rescoreEPSS 12% · 95th percentile
  25. 2026-09-17 19:22 UTCEPSS rescoreEPSS 12% · 95th percentile
Show 64 more
  1. 2026-09-15 03:05 UTCEPSS rescoreEPSS 12% · 95th percentile
  2. 2026-09-13 16:42 UTCEPSS rescoreEPSS 12% · 95th percentile
  3. 2026-09-11 14:48 UTCEPSS rescoreEPSS 12% · 95th percentile
  4. 2026-09-11 09:32 UTCEPSS rescoreEPSS 12% · 95th percentile
  5. 2026-09-09 04:16 UTCOSV refresh
  6. 2026-09-06 13:44 UTCEPSS rescoreEPSS 12% · 95th percentile
  7. 2026-09-04 13:56 UTCEPSS rescoreEPSS 12% · 95th percentile
  8. 2026-09-04 05:02 UTCEPSS rescoreEPSS 12% · 95th percentile
  9. 2026-09-02 14:07 UTCEPSS rescoreEPSS 12% · 95th percentile
  10. 2026-09-01 03:32 UTCEPSS rescoreEPSS 12% · 95th percentile
  11. 2026-08-30 19:13 UTCEPSS rescoreEPSS 12% · 95th percentile
  12. 2026-08-30 01:18 UTCEPSS rescoreEPSS 11% · 95th percentile
  13. 2026-08-28 21:36 UTCEPSS rescoreEPSS 11% · 95th percentile
  14. 2026-08-27 14:21 UTCEPSS rescoreEPSS 12% · 95th percentile
  15. 2026-08-26 14:42 UTCEPSS rescoreEPSS 12% · 95th percentile
  16. 2026-08-25 13:45 UTCEPSS rescoreEPSS 12% · 95th percentile
  17. 2026-08-24 14:11 UTCEPSS rescoreEPSS 12% · 95th percentile
  18. 2026-08-22 12:37 UTCOSV refresh
  19. 2026-08-21 23:45 UTCEPSS rescoreEPSS 12% · 95th percentile
  20. 2026-08-20 22:51 UTCEPSS rescoreEPSS 12% · 95th percentile
  21. 2026-08-19 17:00 UTCEPSS rescoreEPSS 12% · 95th percentile
  22. 2026-08-18 13:44 UTCEPSS rescoreEPSS 12% · 95th percentile
  23. 2026-08-16 14:52 UTCEPSS rescoreEPSS 12% · 95th percentile
  24. 2026-08-16 02:10 UTCEPSS rescoreEPSS 12% · 95th percentile
  25. 2026-08-15 01:26 UTCEPSS rescoreEPSS 12% · 95th percentile
  26. 2026-08-13 21:56 UTCEPSS rescoreEPSS 12% · 95th percentile
  27. 2026-08-12 13:47 UTCEPSS rescoreEPSS 12% · 95th percentile
  28. 2026-08-09 13:43 UTCEPSS rescoreEPSS 12% · 95th percentile
  29. 2026-08-08 16:32 UTCEPSS rescoreEPSS 12% · 95th percentile
  30. 2026-08-07 16:23 UTCEPSS rescoreEPSS 12% · 95th percentile
  31. 2026-08-06 15:44 UTCOSV refresh
  32. 2026-08-06 13:42 UTCEPSS rescoreEPSS 12% · 95th percentile
  33. 2026-08-04 15:05 UTCEPSS rescoreEPSS 12% · 95th percentile
  34. 2026-08-02 02:23 UTCEPSS rescoreEPSS 12% · 95th percentile
  35. 2026-08-01 04:12 UTCEPSS rescoreEPSS 12% · 95th percentile
  36. 2026-07-30 16:24 UTCEPSS rescoreEPSS 12% · 95th percentile
  37. 2026-07-30 01:27 UTCEPSS rescoreEPSS 12% · 95th percentile
  38. 2026-07-28 15:32 UTCEPSS rescoreEPSS 12% · 95th percentile
  39. 2026-07-26 14:51 UTCEPSS rescoreEPSS 12% · 95th percentile
  40. 2026-07-25 14:14 UTCEPSS rescoreEPSS 12% · 95th percentile
  41. 2026-07-24 14:14 UTCEPSS rescoreEPSS 12% · 95th percentile
  42. 2026-07-23 14:15 UTCEPSS rescoreEPSS 12% · 95th percentile
  43. 2026-07-23 01:37 UTCEG score recompute
  44. 2026-07-22 22:17 UTCEG score recompute
  45. 2026-07-22 14:05 UTCEPSS rescoreEPSS 12% · 95th percentile
  46. 2026-07-21 15:22 UTCEPSS rescoreEPSS 12% · 95th percentile
  47. 2026-07-21 08:48 UTCOSV refresh
  48. 2026-07-20 17:04 UTCEPSS rescoreEPSS 12% · 95th percentile
  49. 2026-07-19 14:28 UTCEPSS rescoreEPSS 12% · 95th percentile
  50. 2026-07-19 02:26 UTCEPSS rescoreEPSS 12% · 95th percentile
  51. 2026-07-16 16:59 UTCEPSS rescoreEPSS 12% · 95th percentile
  52. 2026-07-15 16:55 UTCEPSS rescoreEPSS 12% · 95th percentile
  53. 2026-07-15 01:56 UTCEPSS rescoreEPSS 12% · 95th percentile
  54. 2026-07-13 22:27 UTCEPSS rescoreEPSS 12% · 95th percentile
  55. 2026-07-13 06:10 UTCEPSS rescoreEPSS 12% · 95th percentile
  56. 2026-07-12 05:43 UTCEPSS rescoreEPSS 12% · 95th percentile
  57. 2026-07-09 19:06 UTCEPSS rescoreEPSS 12% · 95th percentile
  58. 2026-07-08 15:11 UTCEPSS rescoreEPSS 12% · 95th percentile
  59. 2026-07-07 13:42 UTCEPSS rescoreEPSS 12% · 95th percentile
  60. 2026-07-06 16:24 UTCEPSS rescoreEPSS 12% · 95th percentile
  61. 2026-07-06 02:20 UTCEPSS rescoreEPSS 12% · 95th percentile
  62. 2026-07-05 02:27 UTCEPSS rescoreEPSS 12% · 95th percentile
  63. 2026-07-04 04:26 UTCOSV refresh
  64. 2026-07-01 15:03 UTCEPSS rescoreEPSS 12% · 95th percentile

Frequently asked(5)

What is CVE-2018-8007?
CVE-2018-8007 is a high-severity vulnerability; its CVE record was published on July 11, 2018. Apache CouchDB administrative users can configure the database server via HTTP(S). Due to insufficient validation of administrator-supplied configuration settings via the HTTP API, it is possible for a CouchDB administrator user to escalate their privileges to that of the operating system's user…
When was CVE-2018-8007 made public?
CVE-2018-8007 was made public on July 10, 2018: that is the date its CVE record's CNA, Apache Software Foundation, gives for when the vulnerability was made public. The CVE record itself was published on July 11, 2018. EchelonGraph's copy of the record carries a last-modified date of November 21, 2024; the record at its source may have been updated since.
Is CVE-2018-8007 actively exploited?
CVE-2018-8007 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 12% probability of exploitation in the next 30 days (96th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2018-8007?
CVE-2018-8007 has a CVSS v3 base score of 7.2 (NVD).
How do I remediate CVE-2018-8007?
The CVE record for CVE-2018-8007 names the fix: "Mitigation: All users should upgrade to CouchDB releases 1.7.2 or 2.1.2."

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2018-8007

Explore →

Is Your Infrastructure Affected by CVE-2018-8007?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.