Actively exploited CVSS 9.8 Security news

ArangoDB authentication flaw hands unauthenticated attackers superuser rights – CVE-2026-126755 reports exploitation since September

ArangoDB, the graph database, lets an attacker with no password reach its system APIs with superuser rights in every release up to 3.12.10.1 – all it takes is URL-encoding a single character. The fix in 3.12.11 shipped back in late August 2026 and the vendor described the bug on 6 September. On 18 November 2026 it was finally assigned CVE-2026-126755, and VulnCheck's record says it has been exploited since 16 September. Anyone who has not upgraded should assume the database is exposed.

Kyberkit editorial team · · event date · reading time 4 minutes · For admins and analysts

Actively exploited: ArangoDB, CVE-2026-126755, CVSS 9.8

Key points

  • Who is affected: anyone running the ArangoDB graph and document database up to 3.12.10.1 – single servers and cluster coordinators alike.
  • The bug: the authentication check reads the raw request path while routing uses the decoded one. An encoded underscore (%5f) slips past the check yet lands in the protected /_api interface (CWE-288).
  • Impact: read, modify and delete every document in every database, including the _users collection with password hashes. Chained with a second flaw (GHSA-rvhw-4hpw-9vrx), it leads to code execution on the host.
  • Exploitation: according to VulnCheck's CVE record, the Shadowserver Foundation first observed attacks on 16 Sep 2026. A public chain has been available since 13 Sep.

Vulnerabilities: CVE-2026-126755

What happened

On 18 November 2026 NVD published CVE-2026-126755 for an authentication flaw in the ArangoDB graph database. The record was issued by VulnCheck and states that the Shadowserver Foundation first observed exploitation on 16 September 2026. It does not say who is behind the attacks or how many servers were hit.

The bug itself is not new. ArangoDB fixed it in 3.12.11 (GitHub release from late August) and documented it on 6 September 2026 in advisory GHSA-rrgq-978q-36mq – without a CVE number at the time. According to the advisory, a public chain combining it with a second flaw (GHSA-rvhw-4hpw-9vrx) to achieve code execution on the server has been available since 13 September.

Technical details

The details come from ArangoDB's advisory and the NVD record. We do not publish exploitation instructions.

  • Component: the HTTP layer of arangod, specifically system routes that start with an underscore (/_api, /_admin).
  • Bug class: authentication bypass using an alternate path (CWE-288). The authentication decision is made on the raw path, while the action lookup uses the decoded path. If the leading underscore is encoded as %5f, the check does not recognise the route as a system route, and the router then delivers it to the protected API – with superuser rights.
  • Preconditions: --server.authentication-system-only enabled (the default), single server or coordinator role, network access to the database port (8529 by default).
  • Impact: read, modify and delete any document in any database, including the _users collection with password hashes (weak SHA-256, per the vendor) and the ability to take over accounts. The second flaw in the same releases lets a user with write access run a task with the full privileges of the process – root in the official Docker image.
How an attacker exploits CVE-2026-126755 in ArangoDB1. Unauthenticated attacker sends a request with an encoded underscore in the path; 2. The authentication check does not see a system route and lets it through; 3. After decoding, the request reaches /_api with superuser rights; 4. Attacker reads and alters data, or chains the second flaw to run code on the host1Unauthenticated attacker sendsa request with an encoded underscorein the path2The authentication check does not seea system route and lets it through3After decoding, the request reaches/_api with superuser rights4Attacker reads and alters data, orchains the second flaw to run code onthe host
Simplified attack flow against an unpatched ArangoDB (based on the vendor advisory)

Who is affected

ArangoDB version Status
3.12.10.1 and earlier vulnerable (advisory and NVD)
3.12.11 and later fixed

The advisory says nothing about older branches (3.11) or the ArangoGraph cloud service. Servers whose port is reachable from the internet or an untrusted network are most at risk.

How to tell if you were compromised

Neither the vendor nor VulnCheck has published indicators of compromise. What we recommend checking (our own advice):

  • Request logs from ArangoDB or your reverse proxy: paths containing an encoded underscore, %5f or %5F (for example /_db/<name>/%5fapi/…) – legitimate clients never send these.
  • The _users collection: new users, changed passwords or permissions nobody on your team made.
  • Tasks (/_api/tasks) and Foxx services you did not create.
  • The host: child processes of arangod, new files outside the data directory, and outbound connections.

You can break down the CVSS vector in our CVSS calculator.

What to do

  1. Upgrade to ArangoDB 3.12.11 or later. The fix blocks both steps of the chain.
  2. If you cannot upgrade right away: start the server with --server.authentication-system-only false so authentication is required on every path, including Foxx. The second flaw can be disabled temporarily with --javascript.tasks false.
  3. Close port 8529 to the internet; only your applications should reach the database.
  4. After patching: if an unpatched server was reachable from an untrusted network, change the root and other user passwords, rotate the JWT secret or keyfile on every server and restart. Treat the data in the database as leaked.

Timeline

Timeline of the ArangoDB authentication flawlate Aug 2026: ArangoDB releases 3.12.11 with the fix; 6 Sep 2026: Advisories GHSA-rrgq-978q-36mq and GHSA-rvhw-4hpw-9vrx, no CVE; 13 Sep 2026: Public chain of both flaws, per the advisory; 16 Sep 2026: Shadowserver first observes exploitation (per VulnCheck); 18 Nov 2026: CVE-2026-126755 published in NVDlate Aug 2026ArangoDB releases 3.12.11with the fix6 Sep 2026AdvisoriesGHSA-rrgq-978q-36mq andGHSA-rvhw-4hpw-9vrx, no CVE13 Sep 2026Public chain of both flaws,per the advisory16 Sep 2026Shadowserver first observesexploitation (per VulnCheck)18 Nov 2026CVE-2026-126755 published inNVD
Fix, advisory, exploitation and CVE (ArangoDB, VulnCheck, NVD)

Updates

  • 18 Nov 2026 – first version of this article.

FAQ

Why cover an August bug now?

The vendor fixed and documented it on GitHub without a CVE number, so CVE-driven vulnerability scanners have not been flagging it. CVE-2026-126755 was published on 18 Nov 2026 along with the note that it has been exploited since September. That is the cue to check versions now – and to assume data loss if a server ran unpatched.

Is upgrading enough?

No. The vendor points out that upgrading does not invalidate credentials an attacker may already have read. After the upgrade, change the root and other database user passwords, rotate the JWT secret or keyfile on every server and restart them.

Does it affect ArangoDB in the cloud (ArangoGraph)?

The advisory does not mention the managed service and only lists server versions up to 3.12.10.1. If you use ArangoGraph, check the version in the service console or ask support.

Sources

  1. ArangoDB – GHSA-rrgq-978q-36mq: Unauthenticated superuser access to all data (advisory, 6 Sep 2026)
  2. ArangoDB – GHSA-rvhw-4hpw-9vrx: Missing authorization on the isSystem task flag (advisory, 6 Sep 2026)
  3. NVD – CVE-2026-126755 (CVSS 3.1 9.8, CVSS 4.0 9.3, CWE-288)
  4. VulnCheck – ArangoDB < 3.12.11 Authentication Bypass via URL-Encoded Underscore (18 Nov 2026)
  5. GitHub arangodb/arangodb – v3.12.11 release

Spotted a mistake? Let us know and we will correct it openly.