Skip to main content

MarkLogic Server CVE-2026-85970

| EUVDEUVD-2026-97565 HIGH
Improper Restriction of XML External Entity Reference (CWE-611)
2026-10-12 ProgressSoftware GHSA-vg67-rxc2-5jm6
7.1
CVSS 3.1 · Vendor: ProgressSoftware
View

Attack ChainAIDerived

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

  1. Access
    Authenticate to MarkLogic server path
  2. Delivery
    Submit crafted XML with external entity
  3. Exploit
    XXE parser resolves external entity
  4. Execution
    Read local file or trigger internal SSRF
  5. Impact
    Exfiltrate disclosed file contents

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A02:2025 - Security Misconfiguration
ASVS 5.0
V13 - Configuration XML external entity prevention
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Collection

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

Exploitation Conditions

Exploitation requires that an attacker can submit XML to one of the affected MarkLogic Server request paths that parse XML with external entity (XXE) processing enabled by default - a behavior present in default configurations of the vulnerable 11.x (<11.3.7) and 12.x (<12.1.0) releases, so no special non-default setting is needed to reach the parser. The primary limiting factor is authentication: the CVSS vector specifies PR:L, so the attacker must hold at least low-privileged valid credentials or an existing authenticated session on the server; this is not a fully unauthenticated flaw. No user interaction is required (UI:N). Impact is bounded to confidentiality (local file read / SSRF response disclosure) and minor availability effects; it does not permit data modification (I:N). Upgrading to 11.3.7 or 12.1.0, which disable default external entity processing, removes the condition.

Impact

This is a moderate, authentication-gated information-disclosure/SSRF flaw rather than a top-tier emergency. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L, base 7.1 High) indicates a network-reachable, low-complexity attack that nonetheless requires at least low-level privileges (PR:L) - i.e. an authenticated session - and yields high confidentiality impact (local file disclosure) with only low availability impact (SSRF-driven request generation) and no integrity impact. No EPSS score, CISA KEV listing, SSVC decision data, or POC was provided in the input, so there is no signal of active or probable exploitation to elevate priority; per the precision rules this is 'no public exploit identified at time of analysis.' A notable signal conflict exists: the sole vendor reference is titled 'Critical Security Alert Bulletin' yet the assigned CVSS is 7.1 (High, not Critical) - verify severity framing with Progress, as the vendor's 'Critical' labeling may reflect bulletin-level urgency rather than this specific CVE's base score. Net: real and worth patching on normal cadence for exposed MarkLogic instances, but the authentication requirement and absence of exploitation evidence argue against treating it as an emergency.

Exploit ScenarioDerived

An attacker holding low-privileged credentials (or who has compromised an application account) to a MarkLogic Server sends crafted XML to one of the server paths that parse XML with external entity processing enabled by default. The malicious entity forces the server to read a local file (e.g. configuration or credential material) or issue a server-side request to an internal host, returning that data to the attacker. No public proof-of-concept was identified in the provided data, and exploitation requires an authenticated foothold.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.3% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Oct 12, 2026

XML external entity (XXE) processing is enabled by default across multiple request paths in Progress MarkLogic Server 11.x before 11.3.7 and 12.x before 12.1.0, allowing an attacker who submits crafted XML to trigger server-side requests or read local files. The vulnerability is rated CVSS 7.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L), meaning exploitation requires at least low-privileged credentials or an existing authenticated session - it is not an unauthenticated flaw - and the impact is limited to confidentiality loss and minor availability effects, with no integrity impact. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, so exposure is currently a matter of unpatched, authenticated attack surface rather than active exploitation. Progress has published a security advisory and fixed releases that disable default external entity processing.

RemediationAI

Vendor-released patches are available: upgrade to Progress MarkLogic Server 11.3.7 (for the 11.x train) or 12.1.0 (for the 12.x train), which disable external entity processing by default and remove the vulnerable condition; consult the advisory at https://community.progress.com/s/article/Marklogic-Critical-Security-Alert-Bulletin-October-2026 for download locations and any interim backports. If upgrading cannot be completed immediately, apply targeted compensating controls rather than generic hardening. First, since the flaw requires at least low-privileged credentials (PR:L), tightly restrict and audit which accounts can submit XML to HTTP/REST-style ingestion and query endpoints, rotate credentials for any broadly shared low-privilege accounts, and disable unused XML-accepting endpoints - the trade-off is reduced functionality for legitimate XML-based workflows and administrative overhead in credential management. Second, constrain the blast radius of SSRF by blocking outbound network egress from MarkLogic hosts to internal address ranges and link-local/cloud metadata endpoints (e.g. 169.254.169.254); this does not stop local file disclosure but prevents the server being used as an internal request proxy, at the cost of potentially breaking legitimate outbound integrations. Third, run the MarkLogic service under a least-privilege OS account with no read access to sensitive files (configuration, key material, backups) so that any file-read primitive yields little - expect possible breakage of features that legitimately read from local paths. Finally, enable verbose logging on the affected XML-parsing paths and alert on anomalous outbound requests or unexpected file-path strings in submitted XML, which can provide detection coverage while patching proceeds.

Affected VersionsENISA

MarkLogic Server 11.0.0 <11.3.7
MarkLogic Server 12.0.0 <12.1.0

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

The root cause is CWE-611 (Improper Restriction of XML External Entity Reference). MarkLogic Server parses XML in a number of internal server paths - content ingestion, query, and administrative or REST-style interfaces - and those parsers are configured to resolve external entities by default in the affected releases. When an attacker can supply an XML document that reaches one of these parsers, the parser will dereference DOCTYPE-declared external entities, which can be used either to read files reachable by the MarkLogic service account and return their contents in the parsed result, or to make the server issue outbound HTTP/FTP requests to attacker-chosen destinations (SSRF), potentially reaching internal-only services or cloud metadata endpoints. The CPE string cpe:2.3:a:progress_software_corporation:marklogic_server:*:*:*:*:*:*:*:* confirms the affected component is the MarkLogic Server product line as published by Progress Software Corporation, with all versions in the wildcard set covered until the fixed thresholds of 11.3.7 and 12.1.0. Because the permissive parser behavior ships as the default configuration, no non-default setting is required to reach the vulnerable code path; the practical gate is the PR:L requirement, i.e. valid low-privileged credentials. The CVSS scope is Unchanged with I:N, so the flaw does not permit modification of data or server state.

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

Vendor (ProgressSoftware) PRIMARY 7.1 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L
vuln.today AI 7.1 HIGH

Network-reachable XXE in server XML paths (AV:N/AC:L) but gated by an authenticated session (PR:L); high confidentiality from file/SSRF disclosure, no integrity change, minor availability from SSRF (A:L).

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

Primary rating from Vendor (ProgressSoftware).

CVSS VectorVendor: ProgressSoftware

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

Lifecycle Timeline

2
Patch available
Oct 12, 2026 - 18:03 EUVD
CVE Published
Oct 12, 2026 - 16:39 cve.org
HIGH 7.1

DescriptionCVE.org

Progress MarkLogic Server 12.x releases before 12.1.0 and 11.x releases before 11.3.7 enable XML external entity processing by default in multiple server paths, which could allow crafted XML to cause server-side requests or disclosure of local files.

Executive ViewAI

Why It Matters

Progress MarkLogic Server versions 11.x before 11.3.7 and 12.x before 12.1.0 contain an XML external entity (XXE) vulnerability that requires authenticated access but could allow attackers to read local files or make server-side requests, potentially exposing sensitive data. This affects organizations using these versions for data management, and while no public exploit has been identified, the high confidentiality impact means a data breach could occur if credentials are compromised. Leadership should prioritize patching to mitigate potential data leakage and ensure compliance with data protection requirements.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.3%
Top 82% exploitable
Prevalence
Medium
specialized enterprise/government multi-model database, notable but not ubiquitous
Social Media
1
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 HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
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

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

Attack Technique

XML External Entity (XXE) attacks exploit XML parsers that process Document Type Definitions (DTDs) without proper restrictions.

CVE-2026-85948 CRITICAL
9.9 Oct 12

Authenticated XQuery injection in Progress MarkLogic Server 11.x before 11.3.7 and 12.x before 12.1.0 allows a remote at

CVE-2026-85947 CRITICAL
9.9 Oct 12

An authenticated privilege-escalation flaw in Progress MarkLogic Server lets an attacker who already holds forest-manage

CVE-2026-7329 CRITICAL
9.9 Aug 05

Privilege escalation in Progress MarkLogic Server before 11.3.6 and 12.0.3 lets an authenticated user holding only a low

CVE-2026-9193 CRITICAL
9.9 Aug 05

Privilege escalation in Progress MarkLogic Server (versions before 11.3.6 and 12.0.3) lets an authenticated user holding

CVE-2026-8709 CRITICAL
9.9 Aug 05

Privilege escalation in Progress MarkLogic Server before 11.3.6 and 12.0.3 allows an authenticated user holding only a l

CVE-2026-9192 CRITICAL
9.8 Aug 05

Authentication bypass in the ODBC App Server of Progress MarkLogic Server (before 11.3.6 and 12.0.3) lets an unauthentic

CVE-2026-9191 CRITICAL
9.6 Oct 12

Insufficient isolation in Progress MarkLogic Server 12.x before 12.1.0 and 11.x before 11.3.7 allows code executed throu

CVE-2026-9195 CRITICAL
9.3 Aug 05

Stored/reflected cross-site scripting in the Query Console of Progress MarkLogic Server (versions before 11.3.6 and 12.0

CVE-2026-9190 CRITICAL
9.1 Aug 05

HTTP request smuggling in Progress MarkLogic Server's HTTP App Server (versions before 11.3.6 and 12.0.3) lets a remote

CVE-2026-7557 CRITICAL
9.1 Aug 05

Authentication bypass in Progress MarkLogic Server (versions before 11.3.6 and 12.0.3) lets an unauthenticated remote at

CVE-2026-7326 HIGH
8.8 Aug 05

Cross-site request forgery in the Progress MarkLogic Server Admin UI allows a remote attacker to perform privileged admi

CVE-2026-9203 HIGH
8.5 Aug 05

Server-side request forgery in Progress MarkLogic Server before 11.3.6 and 12.0.3 enables authenticated low-privileged u

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