Security readout for executives and security teams
Plain-English summary
ArcadeDB’s MongoDB-compatible interface can let an unauthenticated network attacker read, create, change, or delete data across databases. Systems running versions before 26.8.1 are at greatest risk when port 27017 is reachable. Successful abuse could cause data theft, corruption, or service disruption.
Executive priority
Treat as an immediate remediation priority for any reachable affected deployment. The flaw crosses the authentication boundary and can compromise confidentiality, integrity, and availability without credentials. Prioritize internet-exposed systems first, then internally reachable instances, and investigate suspicious activity because upgrading does not address prior compromise.
Technical view
Before version 26.8.1, ArcadeDB’s MongoDB wire-protocol plugin does not enforce SASL authentication for insert, find, update, delete, and create commands. An unauthenticated attacker with network access to port 27017 can execute these commands against any database. The issue is classified as CWE-306 and has CVSS 3.1 score 9.8.
Likely exposure
Exposure is likely where ArcadeDB before 26.8.1 runs the MongoDB wire-protocol plugin and port 27017 is reachable from untrusted networks. Internal-only services remain exposed to attackers who gain network access. The source bundle does not establish whether the plugin is enabled by default.
Exploitation context
The attack requires network connectivity but no credentials or user interaction, with low stated complexity. The source bundle reports no CISA KEV listing and provides no evidence of active exploitation. This absence should not be interpreted as proof that exploitation has not occurred.
Researcher notes
The supplied evidence describes missing authentication enforcement on data commands, not a cryptographic SASL weakness. Scope is ArcadeDB versions before 26.8.1 using the MongoDB wire-protocol plugin. Cross-database impact includes insert, find, update, delete, and create operations. Default plugin state and real-world exploitation are not established in the bundle.
Mitigation direction
- Upgrade affected ArcadeDB deployments to version 26.8.1 or later.
- Restrict port 27017 to explicitly trusted systems until upgrades are complete.
- Disable the MongoDB wire-protocol plugin where it is unnecessary.
- Check the vendor advisory for additional configuration or remediation guidance.
Validation and detection
- Inventory ArcadeDB versions and identify all deployments older than 26.8.1.
- Confirm whether the MongoDB wire-protocol plugin is enabled on each deployment.
- Review firewall and security-group rules governing access to port 27017.
- Inspect database and network logs for unexpected unauthenticated activity or cross-database commands.
- After remediation, verify untrusted clients cannot execute data commands without authentication.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-306: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-75852 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- GitHub Security Advisory (GHSA-fq9c-x968-g278)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: ArcadeDB MongoDB wire protocol authentication bypass cross-databaseCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Authentication for Critical Functionality
Missing Authentication for Critical Functionality represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.