CVE-2026-76225: ArcadeData arcadedb · Server-Side Request Forgery (SSRF)
Affects ArcadeData arcadedbSource CVE Database V5
Not known to be exploited · CVSS 8.3 High : upgrade to 26.8.1 soon.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 26.8.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade arcadedb and arcadedata/arcadedb to 26.8.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ArcadeDataarcadedb | Affected
| Fixed in
|
GitHubarcadedata/arcadedbpkg:github/arcadedata/arcadedbOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in ArcadeDB version 26.8.1. Users should upgrade to version 26.8.1 or later to remediate this vulnerability. No vendor advisory content was provided to indicate alternative mitigations or temporary workarounds.
Description
ArcadeDB versions before 26.8.1 contain a server-side request forgery (SSRF) vulnerability in the OpenCypher LOAD CSV feature. This flaw allows authenticated attackers to craft queries that cause the server to fetch data from internal network addresses or cloud metadata endpoints, potentially exposing sensitive information. The vulnerability arises because the implementation does not properly validate HTTP/HTTPS URLs in LOAD CSV commands.