SecPod

Learn Search

Search across all Learn content

← Back to Security Research
ArangoDB Authentication Bypass: CVE-2026-126755 Enables Unauthenticated Superuser Access

ArangoDB Authentication Bypass: CVE-2026-126755 Enables Unauthenticated Superuser Access

CVE-2026-126755 is a critical ArangoDB authentication bypass vulnerability affecting versions before 3.12.11. Learn how inconsistent URL parsing can enable unauthenticated superuser access, its security impact, and recommended detection and remediation measures.

Nov 18, 2026By Rithika Shetty8 min read

SecPod Security Research | Critical Vulnerability Analysis

CVE-2026-126755: Critical ArangoDB Authentication Bypass Enables Unauthenticated Superuser Access

19 November 2026 | ArangoDB | Cross-platform | Critical

CVE-2026-126755 is a critical authentication bypass vulnerability affecting ArangoDB versions before 3.12.11. Inconsistent URL interpretation between authentication checks and request routing can allow remote, unauthenticated attackers to access privileged database operations. Public reproduction material and reported exploitation evidence make timely remediation essential.

1. Executive Summary

ArangoDB is a multi-model database platform supporting document, graph, and key-value data models. CVE-2026-126755 affects the authentication boundary in its HTTP request-processing layer, potentially allowing unauthenticated requests to reach protected database operations with superuser privileges.

The vulnerability occurs because authentication decisions and downstream action routing interpret encoded request paths differently. An attacker with network access to a vulnerable ArangoDB HTTP interface may exploit this discrepancy without valid credentials or user interaction.

ArangoDB 3.12.11, released on August 27, 2026, contains the fix. The vendor published its security advisory on September 6, 2026, and CVE-2026-126755 was published on November 18, 2026. The CVE record attributes the first observed exploitation evidence to September 16, 2026.

CVSS v3.1 9.8 Critical
CVSS v4.0 9.3 Critical
Affected Versions < 3.12.11 ArangoDB
Fixed Version 3.12.11 Released August 27, 2026

2. Vulnerability Overview

Attribute Details
CVE IDCVE-2026-126755
VendorArangoDB
ProductArangoDB Database Server
SeverityCritical
CVSS v3.19.8
CVSS v4.09.3
Primary Weakness CWE-288: Authentication Bypass Using an Alternate Path or Channel
Related Weaknesses CWE-173, CWE-436, CWE-863
Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
Affected VersionsBefore 3.12.11
Fixed Version3.12.11
Vendor Advisory GHSA-rrgq-978q-36mq
Fixed Release Date August 27, 2026
Vendor Advisory Date September 6, 2026
CVE Publication Date November 18, 2026
PlatformCross-platform

3. Technical Root Cause

CVE-2026-126755 originates from inconsistent URL interpretation in ArangoDB's HTTP layer. The authentication component examines a raw request path, while the downstream action dispatcher uses a decoded representation of the same path.

Certain internal database API routes require authentication and elevated privileges. When the authorization check and request dispatcher disagree about whether a route is protected, an unauthenticated request may be classified as permitted before being routed to a privileged internal operation.

Vulnerability Mechanism
Raw request path → Incorrect authentication decision → Decoded internal API route → Privileged database operation

Authentication Boundary Failure

The affected implementation can permit requests that appear to target public routes during the authentication check, even when their decoded paths resolve to protected actions. Under the documented vulnerable configuration, this can result in operations executing with database superuser rights.

This is an authentication and authorization failure rather than a limited information-disclosure issue. Authorization decisions and request routing must use the same canonical interpretation of a request to maintain security boundaries.

4. Attack Surface and Exploitation Preconditions

Exploitation requires network access to an affected ArangoDB HTTP interface. The documented authentication bypass does not require valid database credentials or victim interaction.

Internet-Accessible Instances

Publicly reachable database interfaces present elevated exposure because untrusted remote clients can interact with the vulnerable request-processing component.

Standalone Servers

Vulnerable single-server deployments may expose protected database operations under affected authentication configurations.

Cluster Coordinators

Coordinator endpoints may also be affected. Security teams should assess every externally reachable database entry point.

Authentication Configuration

The documented bypass is associated with authentication-system-only behavior when server authentication is enabled.

5. Security Impact

Successful exploitation can compromise the confidentiality, integrity, and availability of database contents. The vendor describes unauthorized access to privileged operations involving sensitive application data and database-user records.

Confidentiality

Attackers may read sensitive business records, application data, and database-user credential material.

Integrity

Unauthorized modification of database documents may compromise application data and business processes.

Availability

Deletion or corruption of important database content may disrupt dependent applications and services.

Account Security

Exposure or alteration of database-user records may create opportunities for credential compromise, unauthorized access, and persistence.

Impact Distinction: CVE-2026-126755 provides an authentication bypass with privileged database access. Host-level remote code execution is not an inherent capability of this CVE alone; the publicly documented chain involves a separate vulnerability.

6. Disclosure, Exploitation and Patch Timeline

August 27, 2026

ArangoDB 3.12.11 was released, containing the fix for CVE-2026-126755.

September 6, 2026

ArangoDB published security advisory GHSA-rrgq-978q-36mq, describing the authentication bypass and its security impact.

September 16, 2026

The CVE record attributes the first observed exploitation evidence to this date. This observation does not establish when exploitation originally began.

November 18, 2026

CVE-2026-126755 was published, formally identifying the vulnerability.

November 19, 2026

Organizations reviewing the newly published CVE should verify patch status and investigate historical exposure on vulnerable deployments.

7. Exploit Maturity Assessment

Exploit Maturity Publicly Reproducible

Vendor demonstration material and public reproduction reporting support technical reproducibility.

Exploitation Evidence Reported

The CVE record attributes first observed exploitation evidence to September 16, 2026.

Threat Actor Attribution Not Established

No named threat actor has been established from the reviewed evidence.

Affected Organizations Unknown

The number of organizations affected by exploitation has not been established.

Public reproduction material supports the technical exploitability of the vulnerability. It does not independently establish widespread exploitation or identify a responsible attacker.

8. Active Exploitation Assessment

The CVE record reports exploitation evidence first observed on September 16, 2026. This supports treating CVE-2026-126755 as a vulnerability with reported exploitation activity rather than a purely theoretical security issue.

The reviewed evidence does not establish the precise start date of exploitation, the total number of successful compromises, the number of affected organizations, or the identity of a responsible threat actor.

Evidence Qualification: September 16, 2026 represents the first reported observation, not proof that exploitation began on that date or that attacks remain ongoing against every exposed deployment.

9. Proof of Concept Availability and Reproducibility

Public proof-of-concept information exists for CVE-2026-126755. The vendor's September 6 security advisory includes demonstration material describing the authentication bypass and the underlying request-processing discrepancy.

Public reproduction material also documents a vulnerability chain combining CVE-2026-126755 with a separate ArangoDB security weakness. This demonstrates the potential for additional impact when the authentication bypass is combined with another vulnerability.

Assessment Finding
Public PoC Availability Yes; documented in the vendor advisory
Reproducibility Demonstrated on an affected ArangoDB release
Chained Exploit Reproduction Public reproduction reported; exact publication date not established
Authentication Requirement None for the documented bypass
Independent Validation Not performed as part of this article

This analysis does not include exploit payloads, executable reproduction commands, or links to third-party exploit implementations.

10. Time-to-Exploit Analysis

The exploitation timeline shows that the first reported observation occurred 20 days after the release of ArangoDB 3.12.11 and 10 days after publication of the vendor security advisory.

Fixed Release to First Observation 20 days August 27 → September 16, 2026
Vendor Advisory to First Observation 10 days September 6 → September 16, 2026

These intervals measure the time between documented public milestones and the first reported exploitation observation on September 16, 2026. They do not establish when exploitation actually began or how long attackers required to develop a working exploit.

11. Vulnerability Chaining Opportunities

A publicly reproduced exploit chain combines CVE-2026-126755 with a separate ArangoDB vulnerability, GHSA-rvhw-4hpw-9vrx.

CVE-2026-126755 provides the authentication bypass and permits privileged database access. The separate vulnerability involves improper authorization of privileged task behavior and may enable host-level code execution under affected deployment conditions.

01 CVE-2026-126755

Unauthenticated access to privileged database operations

↓
02 GHSA-rvhw-4hpw-9vrx

Separate privileged-task authorization weakness

↓
03 Potential Host-Level Impact

Remote code execution in affected configurations

Attribution Boundary: The combined chain may result in host-level remote code execution. This outcome must not be attributed to CVE-2026-126755 alone; the second vulnerability and relevant deployment conditions are necessary.

12. MITRE ATT&CK Mapping

The following table considers all 15 Enterprise ATT&CK tactics. Mappings represent documented vulnerability capabilities and conditional analytical possibilities, not a reconstruction of an observed attack.

Tactic Tactic ID Technique / Mapping Assessment
Reconnaissance TA0043 N/A No CVE-specific reconnaissance procedure established
Resource Development TA0042 N/A No supporting evidence
Initial Access TA0001 T1190: Exploit Public-Facing Application Conditional mapping for publicly accessible deployments; not proof of an observed procedure
Execution TA0002 N/A Host-level execution requires separate chaining; not established for this CVE alone
Persistence TA0003 N/A Potential account-based persistence is not an observed technique
Privilege Escalation TA0004 N/A Database superuser access is documented, but no separate ATT&CK technique is established
Stealth TA0005 N/A No concealment procedure established
Defense Impairment TA0112 N/A No impairment of security controls established
Credential Access TA0006 N/A Credential material may be exposed; specific attacker technique not established
Discovery TA0007 N/A No observed discovery procedure established
Lateral Movement TA0008 N/A No evidence of lateral movement
Collection TA0009 N/A Data-reading capability exists; specific collection activity not established
Command and Control TA0011 N/A No command-and-control infrastructure identified
Exfiltration TA0010 N/A Data exposure is possible; confirmed exfiltration not established
Impact TA0040 N/A Unauthorized modification or deletion is possible; observed impact technique not established

T1190 is a conditional Initial Access mapping. N/A indicates insufficient evidence to assign a specific ATT&CK technique.

13. Indicators of Compromise

No validated CVE-specific malicious IP addresses, domains, or file hashes were established in the reviewed sources. This analysis therefore does not publish unverified indicators of compromise.

Security teams should investigate unusual HTTP request-path encoding, unexpected access to protected database operations, changes to database-user records, and unexplained modification or deletion of documents.

Detection Distinction: These are behavioral investigation leads, not confirmed indicators uniquely associated with a specific attacker or intrusion campaign.

14. Post-Exploitation Assessment

Successful exploitation can provide access to privileged database functionality. Potential follow-on actions include reading database-user records, altering credentials, modifying or deleting application data, and attempting to preserve unauthorized access.

Exposure of credential material may create additional account-compromise risks. Unauthorized changes to database-user records could potentially support database-level persistence. A separate vulnerability chain may extend impact to the underlying host.

These capabilities must be distinguished from confirmed post-exploitation activity. The reviewed evidence does not establish that a named attacker performed credential theft, persistence, lateral movement, data exfiltration, or host compromise in a documented victim environment.

15. Affected Versions and Patch Availability

Version Status Recommended Action
Before 3.12.11 Affected Upgrade to a vendor-supported fixed release
3.12.11 Fixed Verify installation and deployment coverage
Later supported versions Outside the reported affected range Maintain current security updates

ArangoDB 3.12.11 contains the vendor-confirmed fix for CVE-2026-126755. Administrators should verify installed and running versions across all relevant standalone servers and cluster coordinators.

16. Detection and Investigation Guidance

Identify Vulnerable Assets

  • Inventory standalone ArangoDB servers and cluster coordinators.
  • Identify installations running versions before 3.12.11.
  • Review database interfaces reachable from untrusted networks.
  • Assess authentication and routing configurations.
  • Review container images and application deployments containing ArangoDB.

Investigate Suspicious Activity

  • Examine HTTP and reverse-proxy logs for unusual encoded paths targeting database APIs.
  • Review unexpected access to sensitive database collections.
  • Investigate changes to database users, permissions, and authentication settings.
  • Look for unexplained document modifications or deletions.
  • Correlate database events with available network and host telemetry.

The absence of suspicious logs does not conclusively rule out compromise. Request normalization, incomplete logging, and retention limits may reduce visibility into historical exploitation.

17. Remediation and Mitigation Recommendations

Priority 1: Upgrade to a Fixed Release

Upgrade affected ArangoDB deployments to version 3.12.11 or a later vendor-supported release. Verify that all applicable cluster components have been updated.

Priority 2: Restrict Database Exposure

Limit database HTTP access to trusted application and administration networks. Review firewalls, ingress rules, and reverse-proxy restrictions.

Priority 3: Apply the Qualified Temporary Mitigation

Where immediate upgrading is not possible, the vendor documents disabling authentication-system-only behavior. The workaround requires both settings:

--server.authentication=true --server.authentication-system-only=false

The first setting enables server authentication. The second requires authentication for routes otherwise treated as public. If authentication is disabled globally, changing the authentication-system-only setting does not enforce authentication.

Test compatibility with applications and Foxx routes before deployment. Installing a fixed release remains the preferred remediation.

Priority 4: Rotate Potentially Exposed Credentials

If an affected instance was accessible to untrusted clients, rotate root and other database-user passwords. Rotate the JWT secret or keyfile on relevant servers according to vendor guidance and restart services as required.

Priority 5: Investigate Historical Exposure

Review available telemetry for suspicious database access, unexpected user changes, and unauthorized document operations during the period of exposure.

Priority 6: Verify Remediation

Confirm the running version, authentication behavior, network restrictions, credential rotation, and completed remediation records.

18. Enterprise Risk and Prioritization

CVE-2026-126755 warrants urgent attention because it combines remote accessibility, no credential requirement, critical severity, public reproduction material, and reported exploitation evidence.

Highest-priority assets include unpatched database services exposed to untrusted networks, systems storing sensitive information, and business-critical database clusters.

Priority Assessment: Critical

Organizations should prioritize affected, externally reachable ArangoDB services for patching and historical compromise assessment.

19. Key Security Lessons

  • Use consistent URL canonicalization. Authentication and routing decisions must evaluate the same normalized request representation.
  • Monitor vendor advisories. Security fixes may be available before a CVE identifier is formally published.
  • Reduce exposed attack surfaces. Database interfaces should be accessible only to necessary and trusted systems.
  • Assess exploit chains. Multiple vulnerabilities can combine to create impacts greater than either weakness alone.
  • Verify recovery beyond patching. Credential rotation, investigation, and validation are important when sensitive database information may have been exposed.

20. References

21. Conclusion

CVE-2026-126755 demonstrates how inconsistent HTTP path processing can undermine authentication boundaries and expose privileged database operations to unauthenticated attackers.

Public reproduction material and reported exploitation evidence increase the urgency of remediation. Although ArangoDB 3.12.11 contains the fix, organizations must verify that affected deployments have been updated and investigate possible historical exposure.

Effective response requires patching, network access restrictions, credential rotation where warranted, and validation that the underlying risk has been removed.

Strengthen Vulnerability Management with SecPod Saner

Critical vulnerabilities such as CVE-2026-126755 highlight the need for continuous asset visibility, vulnerability assessment, risk-based prioritization, and timely remediation.

SecPod Saner helps organizations strengthen vulnerability and exposure management through integrated visibility, prioritization, and remediation workflows across supported assets. Specific ArangoDB CVE detection coverage should be verified against deployed product content.

Instantly Fix Risks in Endpoints & Cloud with Saner

Saner is a continuous and integrated vulnerability and exposure management platform that helps organizations identify, prioritize, and remediate security risks.

Schedule a Demo

Featured Posts

Open Critical Apache Roller RCE Vulnerability CVE-2026-129448 Exploited in Active Attacks
threat intelligenceCritical Apache Roller RCE Vulnerability CVE-2026-129448 Exploited in Active Attacks

CVE Research

Critical Apache Roller RCE Vulnerability CVE-2026-129448 Exploited in Active Attacks

Apache Roller CVE-2026-129448, a critical vulnerability with a CVSS score of 9.8, is under active exploitation. The flaw allows unauthenticated remote code execution through insecure XML-RPC deserialization, affecting Apache Roller versions 4.0.0 through 6.1.5. Explore the technical details, exploitation risks, and recommended fixes.

Nov 19, 2026

Open BO Team Weaponizes Log4Shell to Turn VMware Infrastructure Into a Supply Chain Launchpad
BO Team Weaponizes Log4Shell to Turn VMware Infrastructure Into a Supply Chain Launchpad

CVE Research

BO Team Weaponizes Log4Shell to Turn VMware Infrastructure Into a Supply Chain Launchpad

Nov 19, 2026

Open Six Critical F5 BIG-IP Vulnerabilities Expose Systems to Remote Code Execution and DoS Attacks
vulnerability researchSix Critical F5 BIG-IP Vulnerabilities Expose Systems to Remote Code Execution and DoS Attacks

CVE Research

Six Critical F5 BIG-IP Vulnerabilities Expose Systems to Remote Code Execution and DoS Attacks

F5 has disclosed six critical BIG-IP vulnerabilities, each rated CVSS 9.8, that could allow unauthenticated attackers to crash the Traffic Management Microkernel (TMM) and potentially execute remote code. Learn about the affected products, exploitation conditions, security risks, and available engineering hotfixes.

Nov 19, 2026

Open Critical PHP RCE Flaw Highlights Risks in Session Upload Progress Handling
vulnerability researchCritical PHP RCE Flaw Highlights Risks in Session Upload Progress Handling

CVE Research

Critical PHP RCE Flaw Highlights Risks in Session Upload Progress Handling

CVE-2026-115560 is a critical PHP session handling vulnerability that could allow remote code execution through deserialization confusion. Explore the root cause, affected configurations, exploitation risks, and recommended mitigations.

Nov 19, 2026