Skip to main content
Menu
CVEs

CVE

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.

CVE-2026-126755EUVD-2026-129001Published Updated Summary written by a model

9.3CriticalCNA
Exploited
Proof of concept public, per CISA
Fix
Fixed in 3.12.11
Who is exposed
Default setups

Do first: Check every install: default setups are affected.

Summary

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.

Who should check

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

“Affects every deployment reachable over HTTP with the default authentication-system-only=true”

github.com

cve.now Index

50Pcve.now Index 50 of 100 · methodology v3 · provisional
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure25/25Default setups, CISA rates it automatable
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity10/10CVSS 9.3, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active

What to do

  • Check every install: default setups are affected.

  • Upgrade to a fixed version: 3.12.11.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

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"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now
  4. CISA SSVC assessment

    Exploitation: poc · Automatable: yes · Technical impact: total

  5. Record last updated

Affected versions

  • ArangoDB ArangoDB

    fixed in 3.12.11

Evidence 7

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-126755

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: cve.now feed data

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: github.com

Which versions are affected by CVE-2026-126755?

ArangoDB: before 3.12.11.Source: cve.now feed data

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: github.com

How do I fix CVE-2026-126755?

Upgrade to ArangoDB 3.12.11 or later, which is the fixed version.Source: github.com

More CVEs