CVE-2026-56703

HIGHPre-NVD 7.27.2
EchelonGraph scoreMEDIUM confidence

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

Score 7.2 from GitHub Security Advisory (severity: HIGH) published 2026-08-25. A secondary CVSS source baseline 7.2; 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
7.2EG
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: 1.2%CVSS: 7.2Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Adminer before 5.4.3 contains a remote code execution vulnerability in SQLite query handling where VACUUM INTO is not blocked despite ATTACH restrictions. Authenticated attackers can execute VACUUM INTO to write PHP code to arbitrary file paths and execute commands on the server.

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 SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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
1.2%
EPSS %ILE
66th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

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 no (CISA Vulnrichment) · Technical impact total (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; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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

August 25, 2026

Last Modified

October 12, 2026

Advisory Details (2)

Auto-updated Aug 25, 2026
Patch available. Sources: github.
Web page

Adminer before 5.4.3 Remote Code Execution via SQLite VACUUM INTO | Advisories | VulnCheck

https://www.vulncheck.com/advisories/adminer-before-remote-code-execution-via-sqlite-vacuum-into
GitHub advisoryMentions a patch (unverified)

RCE via SQLite VACUUM INTO (ATTACH Blocklist Bypass) · Advisory · vrana/adminer · GitHub

https://github.com/vrana/adminer/security/advisories/GHSA-gmx3-g29w-77wf

Vendor Advisories for CVE-2026-56703(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, 5.3.0+dfsg-1, 5.4.0+dfsg-1, 5.4.1+dfsg-1, 5.4.2+dfsg-1
  • every version up to 5.4.3+dfsg-1: fixed in 5.4.3+dfsg-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 18× in last 7d / 102× 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 100 of 184 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. None are among the latest 100 rows. The 84 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-56703?
CVE-2026-56703 is a high-severity vulnerability; its CVE record was published on August 25, 2026. Adminer before 5.4.3 contains a remote code execution vulnerability in SQLite query handling where VACUUM INTO is not blocked despite ATTACH restrictions. Authenticated attackers can execute VACUUM INTO to write PHP code to arbitrary file paths and execute commands on the server.
When was CVE-2026-56703 made public?
CVE-2026-56703 was made public on July 9, 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 August 25, 2026. EchelonGraph's copy of the record carries a last-modified date of October 12, 2026; the record at its source may have been updated since.
Is CVE-2026-56703 actively exploited?
CVE-2026-56703 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.2% probability of exploitation in the next 30 days (66th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-56703?
CVE-2026-56703 has a CVSS base score of 7.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-56703?
A fix for CVE-2026-56703 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-56703 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-56703

Explore →

Is Your Infrastructure Affected by CVE-2026-56703?

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

Book a Demo →Browse All CVEs