Skip to main content
VulnerabilityPublished

CVE-2026-75840: ArcadeData arcadedb · Comparison Using Wrong Factors

Affects ArcadeData arcadedbSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.7 High : upgrade to 26.8.1 soon.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 38% 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:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 16 Nov 2026.

What to do

Upgrade arcadedb and com.arcadedata/arcadedb to 26.8.1.

Affected software

ProductAffectedFixed in
ArcadeDataarcadedbAffected
  • <26.8.1
Fixed in
  • 26.8.1
Mavencom.arcadedata/arcadedbpkg:maven/com.arcadedata/arcadedbOther threatsAffected
  • <26.8.1
Fixed in
  • 26.8.1

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 additional mitigation guidance is provided in the vendor advisory.

Description

ArcadeDB versions prior to 26.8.1 contain a high-severity arbitrary file read vulnerability in the GraalVM JavaScript sandbox allowlist enforcement. The vulnerability arises because unescaped regular expressions are used to validate package names, allowing attackers with trigger creation privileges to exploit Java.type() to access Java classes that can read arbitrary files on the host system.

References

Community reviews

Loading reviews…