SSRF (Server-Side Request Forgery) in Adminer (CVE-2026-100696)
Summary
SSRF in Adminer (CVE-2026-100696). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 6.0.2 or later.
Original description
The description as published by the source.
Adminer 4.16.0 through 6.0.1 contain a pre-authentication Server-Side Request Forgery (SSRF) vulnerability in the optional Elasticsearch driver (plugins/drivers/elastic.php), fixed in 6.0.2. Because adminer/include/auth.inc.php invokes Driver::connect() before the login result is validated, an unauthenticated attacker who submits crafted auth[server], auth[username], and auth[password] parameters can cause the Adminer server to issue an HTTP GET request (via get_url()/file_get_contents()) to an arbitrary reachable host and port. The driver validates only general server syntax and does not block loopback, private, link-local, or other reserved addresses; if no port is given it appends the default 9200, and Adminer's generic port check rejects ports below 1024. Selected JSON error fields from non-2xx Elasticsearch-style responses, as well as connection failures, are rendered on the login page, providing a port-scanning oracle and enabling internal network reconnaissance and service fingerprinting. Exploitation requires that the optional Elasticsearch driver be explicitly deployed (e.g., via the adminer/elastic.php template or an adminer_object() configuration; it is not loaded in a default build) and that PHP allow_url_fopen be enabled.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-100696 has been found in Adminer.
Risk of unauthorized operations or information disclosure. CVSS score: 5.8/10.
What to do: upgrade Adminer to 6.0.2 or later.
If unsure, ask your IT team or search "Adminer CVE-2026-100696" on the vendor's site.
CVE-2026-100696 (Adminer) — CWE-918 / CVSS v3 5.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 6.0.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SSRF (CWE-918) exists in Adminer.
Check the vendor advisory for the affected versions of Adminer.
Severity: Medium (CVSS 5.8/10). Risk of unauthorized operations or information disclosure.
Update to 6.0.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Adminer' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Adminer' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Adminerを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Adminer to 6.0.2ステージング環境で 6.0.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-100696 adminer
- Ubuntu UBUNTU-CVE-2026-100696 adminer
References
- web github.com
- web vulncheck.com
- web nvd.nist.gov
- web github.com