CVE-2026-75839

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreHIGH confidence

Score 4.3 from GitHub Security Advisory published 2026-08-18. a secondary CVSS source baseline 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

ArcadeDB (com.arcadedb:arcadedb-server) versions <= 26.7.3 contain an insecure direct object reference (IDOR) vulnerability in the Raft cluster-info endpoints (GetClusterHandler and PostBootstrapStateHandler), which authenticate but do not authorize access. On an ArcadeDB HA cluster (only reachable when arcadedb.ha.enabled is set and the ha-raft module is loaded), any authenticated user — including one granted access to only one database or none — can enumerate the full server database registry and retrieve per-database metadata such as database names, last transaction IDs, bootstrap fingerprints, and peer/leader cluster topology, resulting in cross-database information disclosure. Fixed in 26.8.1.

CVSS v3
4.3
EG Score
4.3(high)
EG Risk
19(Track)
EG Risk 19/100SSVC: Track

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
Severity43% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
13%
KEV
Not listed

Published

August 18, 2026

Last Modified

August 18, 2026

Advisory Details (2)

Auto-updated Aug 18, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

ArcadeDB before 26.8.1 Information Disclosure via Cluster Endpoints | Advisories | VulnCheck

https://www.vulncheck.com/advisories/arcadedb-before-information-disclosure-via-cluster-endpoints
github Patch Available🟡 PoC Available

Raft cluster-info endpoints leak cross-database metadata to any authenticated user (IDOR) · Advisory · ArcadeData/arcadedb · GitHub

https://github.com/ArcadeData/arcadedb/security/advisories/GHSA-79wq-w74x-74ch

Vendor Advisories for CVE-2026-75839(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 13× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-08-20 22:56 UTCEPSS rescore
  2. 2026-08-20 12:04 UTCEG score recompute
  3. 2026-08-20 12:04 UTCGHSA enrichment
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-19 13:25 UTCGHSA enrichment
  6. 2026-08-18 14:46 UTCEG score recompute
  7. 2026-08-18 14:46 UTCGHSA enrichment
  8. 2026-08-18 13:48 UTCEG score recompute
  9. 2026-08-18 13:48 UTCGHSA enrichment
  10. 2026-08-18 12:34 UTCEG score recompute
  11. 2026-08-18 12:34 UTCGHSA enrichment
  12. 2026-08-18 11:29 UTCEG score recompute
  13. 2026-08-18 11:29 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-75839?
CVE-2026-75839 is a medium vulnerability published on August 18, 2026. ArcadeDB (com.arcadedb:arcadedb-server) versions <= 26.7.3 contain an insecure direct object reference (IDOR) vulnerability in the Raft cluster-info endpoints (GetClusterHandler and PostBootstrapStateHandler), which authenticate but do not authorize access. On an ArcadeDB HA cluster (only reachable…
When was CVE-2026-75839 disclosed?
CVE-2026-75839 was first published in the National Vulnerability Database on August 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-75839 actively exploited?
CVE-2026-75839 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 86.8% of all scored CVEs.
What is the CVSS score of CVE-2026-75839?
CVE-2026-75839 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-75839?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-75839, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-75839

Explore →

Is Your Infrastructure Affected by CVE-2026-75839?

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

Start Free Scan →Browse All CVEs