CVE-2026-54077

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (38th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-78786 (ENISA EUVD) · GHSA-8w86-m9h8-hvqg (GitHub Security Advisories)Source: ENISA EUVD

7.1EG
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: 0.4%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

ArcadeDB is a Multi-Model DBMS. Prior to 26.6.1, the IMPORT DATABASE statement in engine/src/main/java/com/arcadedb/query/sql/parser/ImportDatabaseStatement.java did not require administrative privileges and passed its source to integration/src/main/java/com/arcadedb/integration/importer/SourceDiscovery.java without validation. An authenticated user with SQL command access through /api/v1/command or /api/v1/query can supply HTTP or HTTPS destinations to make server-side requests to internal services, or file:// paths to read files accessible to the server process and ingest the results as queryable records. The XML importer also permits DTD processing and external entities, enabling entity expansion. The root-only /api/v1/server administration endpoint is not affected. The fix requires updateSecurity permission, blocks local-network import destinations by default through arcadedb.server.security.importBlockLocalNetworks, supports the arcadedb.server.security.importAllowedLocalPaths file allow-list, and disables XML DTD processing and external entities. This issue is fixed in version 26.6.1.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/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)
Severity71% × 45%
Impact severity (EG Severity): CVSS 7.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.4%
EPSS %ILE
38th
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 (7.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.

EG Severity
7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). 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 every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (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)60 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 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

July 16, 2026

Last Modified

September 30, 2026

Advisory Details (4)

Auto-updated Sep 15, 2026
Patch available. Sources: github_pr, github_commit, github_release, github.
GitHub release Patch Available

26.6.1

Patch available: ArcadeData/arcadedb 26.6.1

https://github.com/ArcadeData/arcadedb/releases/tag/26.6.1
GitHub commit

commit bdc414cbdeda (ArcadeData/arcadedb)

Fix landed in ArcadeData/arcadedb commit bdc414cbdeda — awaiting tagged release

https://github.com/ArcadeData/arcadedb/commit/bdc414cbdeda094cf8c20637cdc937335a3a19ee
GitHub pull request

Harden IMPORT DATABASE source validation and require admin privilege

Fix merged in ArcadeData/arcadedb PR #4422 on 2026-05-30 — awaiting tagged release

https://github.com/ArcadeData/arcadedb/pull/4422
GitHub advisoryMentions a patch (unverified)

IMPORT DATABASE allows SSRF and arbitrary local file read by authenticated users · Advisory · ArcadeData/arcadedb · GitHub

https://github.com/ArcadeData/arcadedb/security/advisories/GHSA-8w86-m9h8-hvqg

Vendor Advisories for CVE-2026-54077(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)
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
com.arcadedb:arcadedb-engine21.10.1 ... 26.5.1 (56 versions)
  • every version up to 26.6.1: fixed in 26.6.1
—

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 40× 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.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-54077?
CVE-2026-54077 is a high-severity vulnerability; its CVE record was published on July 16, 2026. ArcadeDB is a Multi-Model DBMS. Prior to 26.6.1, the IMPORT DATABASE statement in engine/src/main/java/com/arcadedb/query/sql/parser/ImportDatabaseStatement.java did not require administrative privileges and passed its source to…
When was the CVE record for CVE-2026-54077 published?
The CVE record for CVE-2026-54077 was published on July 16, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. 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-54077 actively exploited?
CVE-2026-54077 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (38th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54077?
CVE-2026-54077 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54077?
A fix for CVE-2026-54077 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54077 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-54077

Explore →

Is Your Infrastructure Affected by CVE-2026-54077?

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

Book a Demo →Browse All CVEs