Skip to main content
VulnerabilityPublished

CVE-2026-126755: ArangoDB · Authentication Bypass Using an Alternate Path or Channel

Affects ArangoDBSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.3 Critical : upgrade to 3.12.11 as a priority.

Data as of 18 Nov 2026, 15:54 UTC

CVSS 4.0 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.09.3
CNA (VulnCheck)CVSS 3.19.8
Patch
Available – fixed in 3.12.11
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 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 17 Nov 2026.

What to do

Upgrade ArangoDB to 3.12.11.

Affected software

ProductAffectedFixed in
ArangoDBArangoDBAffected
  • <3.12.11
Fixed in
  • 3.12.11

AI-suggested

Upgrade ArangoDB to version 3.12.11 or later, where this authentication bypass vulnerability is fixed. No other mitigations are indicated by the vendor advisory. Systems running affected versions should be patched promptly to prevent exploitation.

Description

ArangoDB versions before 3.12.11 have an authentication bypass vulnerability due to inconsistent parsing between the raw path authentication gate and URL-decoded dispatch logic. Attackers can exploit this by sending requests with a %5f-encoded leading underscore to access privileged API endpoints as a superuser without authentication. This vulnerability was publicly disclosed with a CVSS score of 9.3 and was first observed in exploitation attempts on 2026-09-16. A fix is available in version 3.12.11.

References

Community reviews

Loading reviews…