CVE-2026-100697

HIGHPre-NVD 8.68.6
EchelonGraph scoreMEDIUM confidence

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

Score 8.6 from GitHub Security Advisory (severity: MODERATE) published 2026-09-26. A secondary CVSS source baseline 8.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-87670 (ENISA EUVD) · GHSA-9w28-5vwj-mq45 (GitHub Security Advisories)Source: ENISA EUVD

8.6EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.6Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Adminer 6.0.0 through 6.0.1, when the official ClickHouse driver plugin (plugins/drivers/clickhouse.php, rewritten in 6.0.0) is loaded, is vulnerable to pre-authentication server-side request forgery. An unauthenticated attacker can submit auth[driver]=clickhouse with auth[server] set to an arbitrary URL (for example http://127.0.0.1:18089), causing the Adminer server to issue an HTTP POST containing 'SELECT version()' to that host. In rootQuery(), if the target returns a status outside 200-299 (other than 401/403), the raw HTTP response body is assigned to the connection error and rendered on the login page, so the attacker receives the full response body of the internal service. This enables internal network/port reconnaissance and disclosure of sensitive information contained in internal error pages (stack traces, internal hostnames, file paths, configuration identifiers). Fixed in Adminer 6.0.2.

CVSS v3
8.6
EG Score
8.6HIGHmedium confidence
EG Risk
70
EG Risk 70/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity86% × 45%
Impact severity (EG Severity): CVSS 8.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
34th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.6): severity, escalated by confirmed exploitation. This CVE's 8.6 is its impact severity (EG Severity), not escalated.

EG Severity
8.6 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (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; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). 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

September 26, 2026

Last Modified

September 30, 2026

Advisory Details (2)

Auto-updated Sep 26, 2026
Patch available. Sources: github.
Web page

Adminer 6.0.0 Server-Side Request Forgery via ClickHouse driver | Advisories | VulnCheck

https://www.vulncheck.com/advisories/adminer-6.0.0-server-side-request-forgery-via-clickhouse-driver
GitHub advisoryMentions a patch (unverified)

Adminer 6.0.0: ClickHouse driver reflects arbitrary HTTP response body on login error (pre-auth SSRF with full response echo) · Advisory · vrana/adminer · GitHub

Affected: 4.7.9) addressed the old implementation; v5.4.2 does not reflect the body. The re

https://github.com/vrana/adminer/security/advisories/GHSA-77qq-q8fv-x45v

Vendor Advisories for CVE-2026-100697(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
adminer4.8.1-1 ... 6.1.0-1 (15 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
adminer5.2.1+dfsg-1 ... 6.1.0-1 (11 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
adminer5.2.1+dfsg-1 ... 6.0.1-1 (9 versions)
  • every version up to 6.0.2-1: fixed in 6.0.2-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 34× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 115 rows 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. None are among the latest 100 rows. The 15 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  2. 2026-11-11 16:37 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  3. 2026-11-10 23:43 UTCEchelonGraph re-scored
  4. 2026-11-10 23:43 UTCGHSA enrichmentGHSA-9w28-5vwj-mq45 · GitHub severity MODERATE · GitHub CVSS 8.6
  5. 2026-11-10 16:41 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  6. 2026-11-09 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  7. 2026-11-08 16:37 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  8. 2026-11-07 16:37 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  9. 2026-11-06 16:35 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  10. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  11. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  12. 2026-11-03 16:45 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  13. 2026-11-03 06:29 UTCEchelonGraph re-scored
  14. 2026-11-03 06:29 UTCGHSA enrichmentGHSA-9w28-5vwj-mq45 · GitHub severity MODERATE · GitHub CVSS 8.6
  15. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  16. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  17. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  18. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  19. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  20. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  21. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  22. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  23. 2026-10-26 15:32 UTCEchelonGraph re-scored
  24. 2026-10-26 15:32 UTCGHSA enrichmentGHSA-9w28-5vwj-mq45 · GitHub CVSS 8.6
  25. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
Show 75 more
  1. 2026-10-25 15:58 UTCEchelonGraph re-scored
  2. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  3. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  4. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  5. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  6. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  7. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  8. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  9. 2026-10-18 05:11 UTCEchelonGraph re-scored
  10. 2026-10-17 20:11 UTCEchelonGraph re-scored
  11. 2026-10-17 20:11 UTCGHSA enrichmentGHSA-9w28-5vwj-mq45 · GitHub CVSS 8.6
  12. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  13. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  14. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  15. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  16. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  17. 2026-10-12 16:41 UTCEchelonGraph re-scored
  18. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  19. 2026-10-12 05:00 UTCGHSA enrichmentGHSA-9w28-5vwj-mq45 · GitHub CVSS 8.6
  20. 2026-10-11 20:16 UTCEchelonGraph re-scored
  21. 2026-10-11 17:09 UTCEchelonGraph re-scored
  22. 2026-10-11 17:09 UTCGHSA enrichmentGHSA-9w28-5vwj-mq45 · GitHub CVSS 8.6
  23. 2026-10-11 15:02 UTCEchelonGraph re-scored
  24. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  25. 2026-10-11 05:19 UTCEchelonGraph re-scored
  26. 2026-10-11 05:18 UTCGHSA enrichmentGHSA-9w28-5vwj-mq45 · GitHub CVSS 8.6
  27. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  28. 2026-10-10 17:27 UTCGHSA enrichmentGHSA-9w28-5vwj-mq45 · GitHub CVSS 8.6
  29. 2026-10-10 05:34 UTCEchelonGraph re-scored
  30. 2026-10-10 05:34 UTCGHSA enrichmentGHSA-9w28-5vwj-mq45 · GitHub CVSS 8.6
  31. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  32. 2026-10-09 17:41 UTCGHSA enrichmentGHSA-9w28-5vwj-mq45 · GitHub CVSS 8.6
  33. 2026-10-09 05:04 UTCGHSA enrichmentGHSA-9w28-5vwj-mq45 · GitHub CVSS 8.6
  34. 2026-10-08 17:14 UTCEchelonGraph re-scored
  35. 2026-10-08 17:13 UTCGHSA enrichmentGHSA-9w28-5vwj-mq45 · GitHub CVSS 8.6
  36. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  37. 2026-10-08 05:23 UTCEchelonGraph re-scored
  38. 2026-10-08 05:23 UTCGHSA enrichmentGHSA-9w28-5vwj-mq45 · GitHub CVSS 8.6
  39. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  40. 2026-10-07 17:32 UTCGHSA enrichmentGHSA-9w28-5vwj-mq45 · GitHub CVSS 8.6
  41. 2026-10-07 04:39 UTCGHSA enrichmentGHSA-9w28-5vwj-mq45 · GitHub CVSS 8.6
  42. 2026-10-06 16:48 UTCEchelonGraph re-scored
  43. 2026-10-06 16:48 UTCGHSA enrichmentGHSA-9w28-5vwj-mq45 · GitHub CVSS 8.6
  44. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  45. 2026-10-06 04:58 UTCEchelonGraph re-scored
  46. 2026-10-06 04:58 UTCGHSA enrichmentGHSA-9w28-5vwj-mq45 · GitHub CVSS 8.6
  47. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  48. 2026-10-05 17:08 UTCGHSA enrichmentGHSA-9w28-5vwj-mq45 · GitHub CVSS 8.6
  49. 2026-10-05 05:18 UTCEchelonGraph re-scored
  50. 2026-10-05 05:18 UTCGHSA enrichmentGHSA-9w28-5vwj-mq45 · GitHub CVSS 8.6
  51. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  52. 2026-10-04 17:28 UTCGHSA enrichmentGHSA-9w28-5vwj-mq45 · GitHub CVSS 8.6
  53. 2026-10-04 05:37 UTCGHSA enrichmentGHSA-9w28-5vwj-mq45 · GitHub CVSS 8.6
  54. 2026-10-03 17:47 UTCEchelonGraph re-scored
  55. 2026-10-03 17:47 UTCGHSA enrichmentGHSA-9w28-5vwj-mq45 · GitHub CVSS 8.6
  56. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  57. 2026-10-03 05:57 UTCGHSA enrichmentGHSA-9w28-5vwj-mq45 · GitHub CVSS 8.6
  58. 2026-10-02 18:07 UTCEchelonGraph re-scored
  59. 2026-10-02 18:06 UTCGHSA enrichmentGHSA-9w28-5vwj-mq45 · GitHub CVSS 8.6
  60. 2026-10-02 06:13 UTCEchelonGraph re-scored
  61. 2026-10-02 06:13 UTCGHSA enrichmentGHSA-9w28-5vwj-mq45 · GitHub CVSS 8.6
  62. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  63. 2026-10-01 18:23 UTCGHSA enrichmentGHSA-9w28-5vwj-mq45 · GitHub CVSS 8.6
  64. 2026-10-01 06:31 UTCEchelonGraph re-scored
  65. 2026-10-01 06:31 UTCGHSA enrichmentGHSA-9w28-5vwj-mq45 · GitHub CVSS 8.6
  66. 2026-09-30 18:41 UTCEchelonGraph re-scored
  67. 2026-09-30 18:41 UTCGHSA enrichmentGHSA-9w28-5vwj-mq45 · GitHub CVSS 8.6
  68. 2026-09-30 17:55 UTCEchelonGraph re-scored
  69. 2026-09-30 17:55 UTCGHSA enrichmentGHSA-9w28-5vwj-mq45 · GitHub CVSS 8.6
  70. 2026-09-30 16:35 UTCEchelonGraph re-scored
  71. 2026-09-30 16:35 UTCGHSA enrichmentGHSA-9w28-5vwj-mq45 · GitHub CVSS 8.6
  72. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  73. 2026-09-30 04:38 UTCGHSA enrichmentGHSA-9w28-5vwj-mq45 · GitHub CVSS 8.6
  74. 2026-09-29 16:46 UTCEchelonGraph re-scored
  75. 2026-09-29 16:46 UTCGHSA enrichmentGHSA-9w28-5vwj-mq45 · GitHub CVSS 8.6

Frequently asked(5)

What is CVE-2026-100697?
CVE-2026-100697 is a high-severity vulnerability; its CVE record was published on September 26, 2026. Adminer 6.0.0 through 6.0.1, when the official ClickHouse driver plugin (plugins/drivers/clickhouse.php, rewritten in 6.0.0) is loaded, is vulnerable to pre-authentication server-side request forgery. An unauthenticated attacker can submit auth[driver]=clickhouse with auth[server] set to an…
When was CVE-2026-100697 made public?
CVE-2026-100697 was made public on September 7, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on September 26, 2026. EchelonGraph's copy of the record carries a last-modified date of September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-100697 actively exploited?
CVE-2026-100697 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-100697?
CVE-2026-100697 has a CVSS base score of 8.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-100697?
A fix for CVE-2026-100697 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-100697 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-100697

Explore →

Is Your Infrastructure Affected by CVE-2026-100697?

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