CVE-2026-126755
How to tell if CVE-2026-126755 (ArangoDB login bypass) is reachable in your environment
Reachable if an ArangoDB server before 3.12.11 exposes its HTTP API to untrusted networks with the default authentication setting. No login is needed
If an ArangoDB server on 3.12.10.1 or earlier can be reached over the network, anyone can read, change or delete every database on it without logging in, including the user accounts. ArangoDB fixed this in 3.12.11 on August 31, 2026 and published its advisory on September 6. The CVE number is new as of November 18, so any server that hasn't been upgraded is more than eleven weeks behind on a 9.8 Critical flaw.
ArangoDB says default installs are exposed, because the setting the bypass depends on is on by default. Pruva reproduced the bypass on ArangoDB's official 3.12.10.1 release image, and a public scanner template checks for it.
VulnCheck, which issued the CVE, says "Exploitation evidence was first observed by the Shadowserver Foundation on 2026-09-16." Shadowserver has published no count or detail we can find, and CISA's own review of the CVE record lists exploitation as proof of concept only. It is not on CISA's Known Exploited Vulnerabilities catalog.
Is it reachable for you?
What it is. ArangoDB checks whether a request needs a login by looking at the raw path, then decides what to run after decoding it. A request written in a slightly different form slips past the first check and still reaches the internal API with superuser rights, per ArangoDB and VulnCheck.
Who is most exposed. Any ArangoDB server whose HTTP API, port 8529 by default, can be reached from networks you don't trust. Cloud and container deployments that publish the port directly are the common case.
Checks, in three tiers. The first two decide exposure. The third decides priority. Run these only on systems your organization owns.
- Which version runs? Check the version in the web interface or with arangod --version. Anything at 3.12.10.1 or earlier is affected. Check container image tags too.
- Is the workaround in place? Look for server.authentication-system-only in the server configuration. If it is missing or set to true, which is the default, the server is exposed. Set to false, the bypass is closed, per ArangoDB.
- Who can reach the API? Test whether port 8529 answers from the internet or from networks that shouldn't use the database. Internet-facing servers go first.
Compensating controls (test them, don't assume them)
ArangoDB says to upgrade to 3.12.11. For servers that can't be upgraded right away, ArangoDB gives one workaround.
- Require a login on every path. Start ArangoDB with --server.authentication-system-only false, per ArangoDB. This also requires logins for Foxx service routes, so check that your applications still authenticate.
- Keep the API off untrusted networks. Port 8529 should only be reachable from the applications that use the database.
What to look for in logs
ArangoDB has published no indicators of compromise for CVE-2026-126755. Until it does, upgrade to 3.12.11 or apply ArangoDB's workaround above.
FAQ
Am I exposed to CVE-2026-126755?
You are if an ArangoDB server on 3.12.10.1 or earlier can be reached over the network and still has the default authentication setting. No login is needed.
Is CVE-2026-126755 being exploited?
It has not been confirmed. VulnCheck, which issued the CVE, says Shadowserver first observed exploitation evidence on September 16, 2026. Shadowserver has published no count or detail we can find, CISA's review of the record lists proof of concept only, and it is not on CISA KEV as of the November 17, 2026 catalog.
Why is a CVE from November about a fix from August?
ArangoDB fixed the flaw in 3.12.11 on August 31 and published its advisory on September 6 without a CVE. VulnCheck assigned CVE-2026-126755 on November 18. Scanners that key on CVE numbers may only now start flagging it.
Is there a related flaw?
Yes. ArangoDB's advisory GHSA-rvhw-4hpw-9vrx, fixed in the same 3.12.11 release, lets a user with write access to one database run commands as root. Researchers chained it with this bypass. It has no CVE yet. ArangoDB's workaround for it is --javascript.tasks false.
- Vendor
- ArangoDB
- Product
- ArangoDB, multi-model database
- Affected versions
- ArangoDB 3.12.10.1 and earlier, per ArangoDB's advisory. Fixed in 3.12.11
- Vulnerable component
- HTTP API authentication check on /_api paths (default port 8529)
- CVSS
- 9.8 Critical (VulnCheck as CNA and ArangoDB, CVSS 3.1). VulnCheck also gives 9.3 on CVSS 4.0. NVD has not added its own score
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (VulnCheck and ArangoDB)
- CWE
- CWE-288, Authentication Bypass Using an Alternate Path or Channel (VulnCheck)
- Exploitation
- Not observed
- CISA KEV added
- Patch
- ArangoDB 3.12.11 (August 31, 2026). ArangoDB's advisory has been public since September 6
Updates
Nov 18, 2026. First published. VulnCheck assigned CVE-2026-126755 to the ArangoDB login bypass fixed in 3.12.11 on August 31. VulnCheck cites Shadowserver exploitation evidence; not confirmed by ArangoDB or CISA; not on CISA KEV.
Sources
- ArangoDB advisory GHSA-rrgq-978q-36mq (Sept 6, 2026; affected and fixed versions, default setting, workaround)
- CVE record, CVE-2026-126755 (published by VulnCheck, Nov 18, 2026; Shadowserver statement; CISA review lists proof of concept)
- VulnCheck advisory
- Pruva reproduction REPRO-2026-00355 (official 3.12.10.1 image; read only, not run)
- ArangoDB advisory GHSA-rvhw-4hpw-9vrx (related flaw, fixed in 3.12.11)
- NIST NVD: CVE-2026-126755
- CISA Known Exploited Vulnerabilities catalog (not listed; checked catalog version 2026.11.17)
We publish an advisory when a vulnerability is Critical or on CISA KEV, has one identifiable component to check, and has a public proof of concept or reported exploitation. Advisories are updated as exploitation status changes.