Skip to main content

MarkLogic Server EUVDEUVD-2026-97517

| CVE-2026-85955 CRITICAL
Improper Privilege Management (CWE-269)
2026-10-12 security@progress.com GHSA-m226-3jxq-59vc
9.9
CVSS 3.1 · Vendor: progress
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain low-privilege query-execution access
  2. Delivery
    Submit crafted XQuery evaluation call
  3. Exploit
    Bypass missing evaluation-privilege check
  4. Execution
    Execute code server-side with elevated permissions
  5. Impact
    Full compromise of MarkLogic host data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Least privilege enforcement
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires an existing authenticated account with query-execution access to MarkLogic Server (per CVSS PR:L and the description); it is not reachable by a fully anonymous attacker. The specific trigger is invoking an XQuery evaluation function (e.g., dynamic eval functionality) that fails to enforce the additional required evaluation privilege, allowing a user lacking that privilege to have the query evaluated with elevated permissions. Affected deployments are MarkLogic Server 12.x before 12.1.0 and 11.x before 11.3.7; versions 12.1.0 and 11.3.7 and later are not affected. Limiting factors: the attacker must be able to submit queries to the server, so instances that restrict query access to trusted operators or isolate MarkLogic from untrusted networks substantially reduce exposure; no user interaction is required and attack complexity is low once query access is held.

Impact

This is a genuine high-priority issue rather than a CVSS-inflated one, though some caveats apply. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:C) describes a network-reachable, low-complexity flaw requiring only low privileges and no user interaction, with a scope change and High confidentiality/integrity/availability impact - consistent with the description of an authenticated query-executor escalating to server-side code execution with elevated permissions. The 9.9 score is credible because the scope change plus full CIA impact reflects a privilege-boundary break (CWE-269). However, several key risk signals are MISSING from the input: there is no EPSS score, no CISA KEV listing, no SSVC decision data, and no public exploit (POC) reference, so exploitation likelihood cannot be quantified. Exploitation status is therefore 'no public exploit identified at time of analysis.' The flaw is NOT fully unauthenticated - PR:L means an attacker must already hold query-execution access, which meaningfully limits the attacker population to users or compromised accounts that can submit queries. Reported by the vendor (security@progress.com) and classed as Privilege Escalation/RCE, this warrants prompt patching for any internet- or multi-tenant-exposed MarkLogic instance, but absent EPSS/KEV evidence it should be treated as high-severity-but-not-yet-known-exploited.

Exploit ScenarioDerived

An attacker who already holds a low-privilege MarkLogic account with query-execution access (for example, a limited application or analyst account, or a compromised credential) submits a crafted request invoking an XQuery evaluation function without holding the additional evaluation privilege that should gate it. Because the privilege check is bypassed, the query is evaluated server-side with elevated permissions, yielding arbitrary code execution. No public exploit code was identified in the provided data, and no user interaction is required.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
Patch available 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 12, 2026

Authenticated privilege escalation in Progress MarkLogic Server lets an attacker who already holds query-execution access invoke an XQuery evaluation function without the additional evaluation privilege that function requires, so the query is evaluated with elevated permissions and can lead to server-side code execution in the server's security context. Affected deployments are 12.x releases before 12.1.0 and 11.x releases before 11.3.7; the vulnerability is rated CVSS 9.9 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H), with the scope change and full confidentiality, integrity, and availability impact reflecting what is possible once the missing privilege check is bypassed. Exploitation requires a pre-existing account with query-execution access rather than anonymous reachability, and no public exploit code has been identified at time of analysis; there is no confirmed active exploitation (CISA KEV) reported for this issue.

RemediationAI

Vendor-released patch: upgrade to MarkLogic Server 12.1.0 (for the 12.x line) or 11.3.7 (for the 11.x line), the exact fixed versions named in the vendor advisory at https://community.progress.com/s/article/Marklogic-Critical-Security-Alert-Bulletin-October-2026; no separate standalone hotfix or workaround is documented in the supplied data, so patching is the primary action. Where immediate upgrade is not possible, compensating controls should focus on the PR:L precondition, because the flaw is only reachable by a principal that can already execute queries: audit and strip query-execution privileges and any overly broad amps from accounts and roles that do not genuinely need to submit arbitrary queries, accepting that this will break legitimate application, ETL, or integration workloads that rely on those identities; and restrict network reachability to MarkLogic query and application server ports with firewall rules or allowlists so that only trusted operators and application tiers can submit queries at all, with the trade-off that remote clients and distributed clusters outside those ranges will lose access. Because a valid low-privilege account is the entry requirement, also review credentials and access paths for query-capable accounts, rotate secrets that may have leaked, and monitor query and audit logs for unexpected invocations of dynamic evaluation functions by users that do not hold the evaluation privilege; these monitoring measures are detective rather than preventive and will not stop exploitation on their own. Note that CVSS 9.9 with PR:L means these access restrictions are the controls most likely to materially reduce risk while the upgrade is scheduled.

Affected VersionsENISA

MarkLogic Server 12.0.0 <12.1.0
MarkLogic Server 11.0.0 <11.3.7

Affected Packages

euvd marklogic_server fix: 11.3.7, 12.1.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

MarkLogic Server is a multi-model (document/NoSQL) database whose primary programmatic interface is XQuery, with JavaScript and REST/HTTP layers built on the same engine. The engine enforces authorization through a role-based privilege model: sensitive operations such as dynamic query evaluation are gated behind a dedicated evaluation privilege so that only trusted users or privileged amps can have arbitrary query text parsed and executed inside the server process. CVE-2026-85955 is classified as CWE-269 (Improper Privilege Management): the evaluation function does not enforce that additional required privilege, so a caller who can already submit queries has its input evaluated under elevated permissions instead of being rejected. Because the evaluated code runs server-side within the MarkLogic process, the practical consequence is arbitrary server-side code execution with the privileges of the server, which is why the CVSS vector shows S:C with C:H/I:H/A:H despite the PR:L precondition. The affected surface is the XQuery evaluation path reachable by any principal holding query-execution rights; instances that expose query endpoints only to trusted networks or tightly scoped operators are materially less exposed.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (progress) PRIMARY 9.9 CRITICAL
AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
vuln.today AI 9.9 CRITICAL

Network-reachable with low complexity; PR:L because query-execution access is required but not admin; scope change (S:C) as the eval-privilege bypass escalates beyond the authorized security boundary to code execution with full CIA impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Primary rating from Vendor (progress).

CVSS VectorVendor: progress

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Patch available
Oct 12, 2026 - 17:18 EUVD
CVE Published
Oct 12, 2026 - 16:17 cve.org
CRITICAL 9.9

DescriptionCVE.org

Progress MarkLogic Server 12.x releases before 12.1.0 and 11.x releases before 11.3.7 allow a remote attacker with query-execution access to invoke an XQuery evaluation function without the additional required evaluation privilege, which could result in server-side code execution with elevated permissions.

Executive ViewAI

Why It Matters

A critical privilege-escalation flaw in Progress MarkLogic Server allows someone who already holds a query-execution account to run queries with elevated permissions, potentially achieving code execution with the database server's own privileges. Because MarkLogic typically stores regulated, proprietary, or customer data and often runs with broad access to connected systems, a successful exploit by an insider, a compromised application account, or a stolen credential could expose or corrupt that data and disrupt dependent business services. No public exploit code or confirmed active exploitation has been reported, so this is a patch-planning and access-governance priority rather than an emergency incident.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis; interim mitigations include minimizing and auditing accounts with query-execution access, enforcing least privilege on XQuery evaluation functions, removing shared or standing privileged credentials, monitoring query and audit logs for anomalous evaluation calls, terminating unauthorized sessions, and restricting network access and administrative interfaces to trusted hosts.

Threat Intelligence Overview

EPSS Score
0.4%
Top 63% exploitable
Prevalence
Low
niche enterprise/government NoSQL database, limited overall deployment footprint
Social Media
3
Sightings
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.4%
Patch available Yes
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
High

Priority Score

50
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +50
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy