CVE-2026-100698

MEDIUMPre-NVD 5.85.8
EchelonGraph scoreMEDIUM confidence

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

Score 5.8 from GitHub Security Advisory published 2026-09-26. A secondary CVSS source baseline 5.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-87671 (ENISA EUVD) · GHSA-wrf7-8p9h-xp6p (GitHub Security Advisories)Source: ENISA EUVD

5.8EG
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.3%CVSS: 5.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Adminer 5.5.1 through 6.0.1 improperly parses the login 'server' string in the host_port() function in adminer/include/functions.inc.php. The port capture group requires pure digits anchored to the end of the string, so any server value with a non-digit tail fails the regex and falls back to returning the whole string as the host with an empty port. Because the privileged-port restriction in adminer/include/auth.inc.php inspects only the parsed port, the check is skipped, and the mysqli/mysqlnd client subsequently re-parses host:port from the host string and opens a TCP connection. A remote, unauthenticated attacker who can reach the Adminer login page can submit a crafted value such as 127.0.0.1:80/x to make the server initiate TCP connections to arbitrary internal hosts and privileged ports before credentials are validated, enabling server-side request forgery and blind internal port scanning (connection refused vs. handshake vs. timeout acts as a liveness oracle). This is a regression that re-opens the bypass fixed in 5.5.0 (GHSA-58cq-mgw2-38m5). Fixed in 6.0.2.

CVSS v3
5.8
EG Score
5.8MEDIUMmedium confidence
EG Risk
57
EG Risk 57/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)
Severity58% × 45%
Impact severity (EG Severity): CVSS 5.8 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.3%
EPSS %ILE
28th
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 (5.8): severity, escalated by confirmed exploitation. This CVE's 5.8 is its impact severity (EG Severity), not escalated.

EG Severity
5.8 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). 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 before 6.0.2 Privileged-Port SSRF via host_port Regex | Advisories | VulnCheck

https://www.vulncheck.com/advisories/adminer-before-6.0.2-privileged-port-ssrf-via-host-port-regex
GitHub advisoryMentions a patch (unverified)

Privileged-port SSRF via host_port regex non-match · Advisory · vrana/adminer · GitHub

https://github.com/vrana/adminer/security/advisories/GHSA-rwxg-xph9-82cj

Vendor Advisories for CVE-2026-100698(1)

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

Affected Packages

(1 across 1 ecosystem)
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 9× in last 7d / 56× 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.

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. 2 repeat rows among the latest 84 are merged into the row they repeat.

  1. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  2. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  3. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  4. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  5. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  6. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  7. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  8. 2026-10-26 15:33 UTCEG score recompute
  9. 2026-10-26 15:33 UTCGHSA enrichmentGHSA-wrf7-8p9h-xp6p · GitHub CVSS 5.8
  10. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  11. 2026-10-25 15:58 UTCEG score recompute
  12. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  13. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  14. 2026-10-23 09:53 UTCEG score recompute
  15. 2026-10-23 09:53 UTCGHSA enrichmentGHSA-wrf7-8p9h-xp6p · GitHub CVSS 5.8
  16. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  17. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  18. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  19. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  20. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  21. 2026-10-18 05:11 UTCEG score recompute
  22. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  23. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  24. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  25. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.3% · 18th percentile
Show 57 more
  1. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  2. 2026-10-12 16:41 UTCEG score recompute
  3. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  4. 2026-10-11 20:16 UTCEG score recompute
  5. 2026-10-11 18:29 UTCEG score recompute
  6. 2026-10-11 14:06 UTCEG score recompute
  7. 2026-10-11 14:06 UTCGHSA enrichmentGHSA-wrf7-8p9h-xp6p · GitHub CVSS 5.8
  8. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  9. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  10. 2026-10-10 16:19 UTCEG score recompute
  11. 2026-10-10 16:19 UTCGHSA enrichmentGHSA-wrf7-8p9h-xp6p · GitHub CVSS 5.8
  12. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  13. 2026-10-09 18:32 UTCGHSA enrichmentGHSA-wrf7-8p9h-xp6p · GitHub CVSS 5.8
  14. 2026-10-08 20:39 UTCEG score recompute
  15. 2026-10-08 20:39 UTCGHSA enrichmentGHSA-wrf7-8p9h-xp6p · GitHub CVSS 5.8
  16. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  17. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  18. 2026-10-07 22:53 UTCGHSA enrichmentGHSA-wrf7-8p9h-xp6p · GitHub CVSS 5.8
  19. 2026-10-07 01:06 UTCEG score recompute
  20. 2026-10-07 01:06 UTCGHSA enrichmentGHSA-wrf7-8p9h-xp6p · GitHub CVSS 5.8
  21. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  22. 2026-10-06 03:19 UTCGHSA enrichmentGHSA-wrf7-8p9h-xp6p · GitHub CVSS 5.8
  23. 2026-10-06 03:19 UTCEG score recompute
  24. 2026-10-06 03:19 UTCGHSA enrichmentGHSA-wrf7-8p9h-xp6p · GitHub CVSS 5.8
  25. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  26. 2026-10-05 05:32 UTCEG score recompute
  27. 2026-10-05 05:32 UTCGHSA enrichmentGHSA-wrf7-8p9h-xp6p · GitHub CVSS 5.8
  28. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  29. 2026-10-04 07:45 UTCEG score recompute
  30. 2026-10-04 07:45 UTCGHSA enrichmentGHSA-wrf7-8p9h-xp6p · GitHub CVSS 5.8
  31. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  32. 2026-10-03 09:58 UTCEG score recompute
  33. 2026-10-03 09:58 UTCGHSA enrichmentGHSA-wrf7-8p9h-xp6p · GitHub CVSS 5.8
  34. 2026-10-02 12:02 UTCEG score recompute
  35. 2026-10-02 12:02 UTCGHSA enrichmentGHSA-wrf7-8p9h-xp6p · GitHub CVSS 5.8
  36. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  37. 2026-10-01 14:13 UTCGHSA enrichmentGHSA-wrf7-8p9h-xp6p · GitHub CVSS 5.8
  38. 2026-09-30 16:27 UTCEG score recompute
  39. 2026-09-30 16:27 UTCGHSA enrichmentGHSA-wrf7-8p9h-xp6p · GitHub CVSS 5.8
  40. 2026-09-30 15:31 UTCEG score recompute
  41. 2026-09-30 15:31 UTCGHSA enrichmentGHSA-wrf7-8p9h-xp6p · GitHub CVSS 5.8
  42. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  43. 2026-09-30 12:33 UTCEG score recompute
  44. 2026-09-30 12:33 UTCGHSA enrichmentGHSA-wrf7-8p9h-xp6p · GitHub CVSS 5.8
  45. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  46. 2026-09-29 14:46 UTCEG score recompute
  47. 2026-09-29 14:46 UTCGHSA enrichmentGHSA-wrf7-8p9h-xp6p · GitHub CVSS 5.8
  48. 2026-09-28 16:58 UTCEG score recompute
  49. 2026-09-28 16:57 UTCGHSA enrichmentGHSA-wrf7-8p9h-xp6p · GitHub CVSS 5.8
  50. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  51. 2026-09-28 10:03 UTCEG score recompute
  52. 2026-09-28 10:03 UTCGHSA enrichmentGHSA-wrf7-8p9h-xp6p · GitHub CVSS 5.8
  53. 2026-09-27 12:15 UTCEG score recompute
  54. 2026-09-27 12:15 UTCGHSA enrichmentGHSA-wrf7-8p9h-xp6p · GitHub CVSS 5.8
  55. 2026-09-26 14:29 UTCEG score recompute
  56. 2026-09-26 13:34 UTCEG score recomputeFirst assessed: 5.8 MEDIUM
  57. 2026-09-26 13:30 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-100698?
CVE-2026-100698 is a medium-severity vulnerability; its CVE record was published on September 26, 2026. Adminer 5.5.1 through 6.0.1 improperly parses the login 'server' string in the host_port() function in adminer/include/functions.inc.php. The port capture group requires pure digits anchored to the end of the string, so any server value with a non-digit tail fails the regex and falls back to…
When was CVE-2026-100698 made public?
CVE-2026-100698 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-100698 actively exploited?
CVE-2026-100698 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (28th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-100698?
CVE-2026-100698 has a CVSS base score of 5.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-100698?
A fix for CVE-2026-100698 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-100698 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-100698

Explore →

Is Your Infrastructure Affected by CVE-2026-100698?

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