ArcadeDB from 21.12.1 before 26.10.2 GraphQL Schema Replacement via Read-Only Query Endpoint
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 26.10.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
ArcadeDB, a multi-model database, is affected by this flaw, which lets a user with only read permissions replace the shared GraphQL schema through the read-only query endpoint. The result is that query results shown to other users, including administrators, can be altered.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
ArcadeDB from 21.12.1 before 26.10.2 contains an authorization bypass vulnerability that allows users with only readRecord to replace the shared GraphQL schema via the read-only query endpoint. Attackers can send a GraphQL type definition with a crafted @sql directive to /api/v1/query/{database}, altering query results returned to other users including administrators.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- ArcadeData arcadedb
From 21.12.1 · fixed in 26.10.2