CVE-2026-126755

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-11-18. A secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-129001 (ENISA EUVD) · GHSA-pvg4-7m6q-pqg3 (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan mitigationNo fix is confirmed yet: check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's CNA (VulnCheck) lists ArangoDB versions before 3.12.11 as affected. No release containing a fix is confirmed on record.

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.

CVSS v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
75
EG Risk 75/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
44th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 18, 2026

Last Modified

November 18, 2026

Advisory Details (4)

Auto-updated Nov 18, 2026
🔬 Proof of concept available. No fix on record yet. Sources: github.
Web page

ArangoDB < 3.12.11 Authentication Bypass via URL-Encoded Underscore | Advisories | VulnCheck

https://www.vulncheck.com/advisories/arangodb-3.12.11-authentication-bypass-via-url-encoded-underscore
Web page🟡 PoC Available

REPRO-2026-00355: ArangoDB full-chain: unauthenticated %5f URL auth bypass...

https://www.pruva.dev/reproductions/REPRO-2026-00355
Web page

nuclei-templates/http/vulnerabilities/arangodb/arangodb-auth-bypass.yaml at main · projectdiscovery/nuclei-templates · GitHub

https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/arangodb/arangodb-auth-bypass.yaml
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Unauthenticated superuser access to all data · Advisory · arangodb/arangodb · GitHub

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

Vendor Advisories for CVE-2026-126755(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 10× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 19:31 UTCEchelonGraph re-scored
  2. 2026-11-21 19:31 UTCGHSA enrichmentGHSA-pvg4-7m6q-pqg3 · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  4. 2026-11-20 21:19 UTCEchelonGraph re-scored
  5. 2026-11-20 21:19 UTCGHSA enrichmentGHSA-pvg4-7m6q-pqg3 · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  7. 2026-11-19 23:16 UTCGHSA enrichmentGHSA-pvg4-7m6q-pqg3 · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-11-19 17:03 UTCEchelonGraph re-scored
  9. 2026-11-19 17:03 UTCGHSA enrichmentGHSA-pvg4-7m6q-pqg3 · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  11. 2026-11-18 18:42 UTCEchelonGraph re-scored
  12. 2026-11-18 18:42 UTCGHSA enrichmentGHSA-pvg4-7m6q-pqg3 · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-11-18 18:28 UTCEchelonGraph re-scored
  14. 2026-11-18 17:53 UTCEchelonGraph re-scored
  15. 2026-11-18 17:03 UTCENISA EUVD ID recordedEUVD-2026-129001 · Source: ENISA EUVD
  16. 2026-11-18 16:28 UTCEchelonGraph re-scored
  17. 2026-11-18 15:43 UTCEchelonGraph re-scoredFirst assessed: 9.8 CRITICAL
  18. 2026-11-18 15:42 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-126755?
CVE-2026-126755 is a critical-severity vulnerability; its CVE record was published on November 18, 2026. 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…
When was CVE-2026-126755 made public?
CVE-2026-126755 was made public on September 6, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on November 18, 2026. EchelonGraph's copy of the record carries a last-modified date of November 18, 2026; the record at its source may have been updated since.
Is CVE-2026-126755 actively exploited?
CVE-2026-126755 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-126755?
CVE-2026-126755 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-126755?
No fix for CVE-2026-126755 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (VulnCheck) lists ArangoDB versions before 3.12.11 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-126755 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-126755

Explore →

Is Your Infrastructure Affected by CVE-2026-126755?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.