Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate to MarkLogic REST API with admin REST role
-
DeliveryInject crafted documents into document processing pipeline
-
ExploitWait for higher-privileged user to access pipeline content
-
ExecutionPrivilege escalation triggers under higher-privileged context
-
ImpactExfiltrate sensitive server-side 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 the attacker to possess a valid MarkLogic Server account with the administrative REST role assigned - this is a high-privilege role, not a standard user account, making opportunistic exploitation difficult. A second, non-negotiable condition is that a higher-privileged user (e.g., a super-administrator) must interact with or trigger processing of the attacker-controlled documents; this aligns with the UI:R metric in the CVSS vector. The vulnerability resides in the REST API document processing pipeline specifically, so access to that pipeline endpoint is required. What limits exploitation: the PR:H requirement rules out unauthenticated or low-privilege attackers; the UI:R requirement means the attacker cannot independently trigger full impact and must induce a more privileged user to act; no special network position beyond network reachability to the REST API is required (AV:N, AC:L). |
| Impact | The NVD CVSS base score of 8.1 (AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:N) reflects high potential impact but meaningful exploitation prerequisites. PR:H confirms that the attacker must already hold an administrative REST role - a high-privilege position - which substantially raises the bar compared to unauthenticated or low-privilege flaws. UI:R introduces a second gating condition: a higher-privileged user must interact with the attacker-controlled documents before privilege escalation occurs. No EPSS score was provided in source data, and the vulnerability is not listed in CISA KEV, so there is no confirmed in-the-wild exploitation signal. No public proof-of-concept exploit has been identified. In practice, this vulnerability is most dangerous in multi-tenant or multi-team MarkLogic environments where administrative REST roles are distributed to operational or developer users who are not fully trusted super-administrators. The combination of PR:H and UI:R makes opportunistic, broad exploitation unlikely; targeted insider-threat or compromised-admin scenarios represent the realistic threat model. |
| Exploit ScenarioDerived | An attacker who has obtained or been granted an administrative REST role account submits specially crafted documents into the MarkLogic REST API document processing pipeline. When a higher-privileged user - such as a security administrator or super-admin - accesses or processes these documents, the pipeline triggers the privilege escalation flaw, granting the attacker access to sensitive server-side data that their original role should not permit them to read or modify. No public proof-of-concept has been identified, but the attack is conceptually straightforward once the role-level access is established. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 05, 2026
Privilege escalation in Progress MarkLogic Server's REST API document processing pipeline allows an authenticated user holding an administrative REST role to elevate their access to a higher privilege level, resulting in unauthorized disclosure of sensitive server-side data. Affected versions span both the 11.x and 12.x release trains, patched in 11.3.6 and 12.0.3 respectively per the vendor's August 2026 critical security bulletin. No public exploit code has been identified and the vulnerability is not listed in the CISA KEV catalog, though the scope change (S:C) and high confidentiality and integrity impact in the CVSS vector underscore meaningful post-exploitation consequence within the MarkLogic environment.
RemediationAI
The primary remediation is to upgrade MarkLogic Server to version 11.3.6 or 12.0.3, as confirmed by the vendor's Critical Security Alert Bulletin at https://community.progress.com/s/article/Marklogic-Critical-Security-Alert-Bulletin-August-2026. If immediate patching is not feasible, administrators should audit and restrict assignment of the administrative REST role to the minimum necessary set of accounts, reducing the pool of principals capable of exploiting the vulnerability. Additionally, monitoring REST API document processing activity for anomalous submissions by administrative REST role users can serve as a detective control. Note that restricting the REST API endpoint entirely may impact legitimate document ingestion workflows and should be assessed against operational requirements before implementation. Organizations on unsupported or older major release trains should prioritize migration to a supported version.
Affected VersionsENISA
Affected Packages
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 (CPE: cpe:2.3:a:progress_software_corporation:marklogic_server:*) is an enterprise-grade multi-model NoSQL database widely used in government, financial services, and media. Its REST API exposes a document processing pipeline through which clients submit and retrieve documents. The root cause is classified as CWE-269 (Improper Privilege Management): the pipeline fails to enforce adequate privilege boundaries when handling requests from users holding the administrative REST role, allowing those users to craft interactions that are subsequently processed under a higher-privilege security context. The CVSS scope change indicator (S:C) confirms that the exploitable component - the document processing pipeline - can affect resources that are normally outside the attacker's authorization boundary. The UI:R metric reflects that exploitation depends on a higher-privileged user accessing or triggering the processing of attacker-controlled content.
Know when Marklogic Server gets its next vulnerability
- 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
AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:N
PR:H confirmed by requirement for administrative REST role; UI:R reflects mandatory higher-privileged user interaction; S:C and C:H/I:H reflect cross-privilege-boundary data access; A:N as no availability impact is described.
Primary rating from Vendor (ProgressSoftware).
CVSS VectorVendor: ProgressSoftware
Lifecycle Timeline
2DescriptionCVE.org
An improper privilege management vulnerability in the REST API document processing pipeline of Progress MarkLogic Server before 11.3.6 and 12.0.3 allows an authenticated user with an administrative REST role to escalate privileges. This can result in unauthorized disclosure of sensitive server-side data when it is accessed by a higher-privileged user.
Executive ViewAI
Progress MarkLogic Server (versions 11.x and 12.x) contains a privilege escalation vulnerability enabling unauthorized access to sensitive data through the REST API, with risk limited to authenticated administrator-level accounts. The vulnerability creates insider threat and administrative credential compromise risks, potentially exposing sensitive data repositories. Immediate patching is required to close this access pathway and maintain data protection compliance.
Apply vendor patch: version 11.3.6 (11.x releases) and 12.0.3 (12.x releases) per August 2026 security bulletin.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
More in Marklogic Server
View allAuthenticated XQuery injection in Progress MarkLogic Server 11.x before 11.3.7 and 12.x before 12.1.0 allows a remote at
An authenticated privilege-escalation flaw in Progress MarkLogic Server lets an attacker who already holds forest-manage
Privilege escalation in Progress MarkLogic Server before 11.3.6 and 12.0.3 lets an authenticated user holding only a low
Privilege escalation in Progress MarkLogic Server (versions before 11.3.6 and 12.0.3) lets an authenticated user holding
Privilege escalation in Progress MarkLogic Server before 11.3.6 and 12.0.3 allows an authenticated user holding only a l
Authentication bypass in the ODBC App Server of Progress MarkLogic Server (before 11.3.6 and 12.0.3) lets an unauthentic
Insufficient isolation in Progress MarkLogic Server 12.x before 12.1.0 and 11.x before 11.3.7 allows code executed throu
Stored/reflected cross-site scripting in the Query Console of Progress MarkLogic Server (versions before 11.3.6 and 12.0
HTTP request smuggling in Progress MarkLogic Server's HTTP App Server (versions before 11.3.6 and 12.0.3) lets a remote
Authentication bypass in Progress MarkLogic Server (versions before 11.3.6 and 12.0.3) lets an unauthenticated remote at
Cross-site request forgery in the Progress MarkLogic Server Admin UI allows a remote attacker to perform privileged admi
Server-side request forgery in Progress MarkLogic Server before 11.3.6 and 12.0.3 enables authenticated low-privileged u
EUVD-2026-53422
GHSA-xp9q-9vhj-ggp6
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB