Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-85970 Overview
CVE-2026-85970 is an XML External Entity (XXE) vulnerability in Progress MarkLogic Server. The flaw affects 12.x releases before 12.1.0 and 11.x releases before 11.3.7. Multiple server paths enable XML external entity processing by default. Attackers who can submit crafted XML to the server can trigger server-side requests or read local files from the host. The weakness is tracked under CWE-611: Improper Restriction of XML External Entity Reference.
Critical Impact
Authenticated attackers can disclose local files or force the MarkLogic Server to issue server-side requests to internal network destinations.
Affected Products
- Progress MarkLogic Server 12.x releases before 12.1.0
- Progress MarkLogic Server 11.x releases before 11.3.7
- Deployments exposing XML-processing server paths to authenticated users
Discovery Timeline
- 2026-10-12 - CVE-2026-85970 published to the National Vulnerability Database
- 2026-10-15 - Last updated in NVD database
- October 2026 - Progress releases the MarkLogic Critical Security Alert Bulletin (Progress Security Alert Bulletin)
Technical Details for CVE-2026-85970
Vulnerability Analysis
MarkLogic Server parses XML input across multiple server paths. These parsers resolve external entity references by default. An attacker who submits a document containing a crafted DOCTYPE declaration can force the parser to dereference an external entity. The parser then reads the referenced resource and returns its contents to the attacker or embeds them in a response. The vulnerability requires network access and low-privilege authentication but no user interaction. Successful exploitation leads to confidentiality loss and limited availability impact as the server performs unintended I/O operations.
Root Cause
The root cause is insecure default configuration of the XML parsers used by MarkLogic Server. External entity resolution and DTD processing are enabled on code paths that accept user-controlled XML. The parsers do not disable ENTITY_RESOLVER behavior or restrict entity sources before processing untrusted input, which is the condition described by CWE-611.
Attack Vector
Exploitation requires an authenticated user who can post XML to an affected endpoint. The attacker crafts a document that declares an external entity pointing to a file:// URI for local file disclosure or an http:// URI for server-side request forgery (SSRF). When MarkLogic parses the document, it fetches the referenced resource using the server's identity and network position. This enables access to internal services, cloud metadata endpoints, and files readable by the MarkLogic process. See the Progress Security Alert Bulletin for vendor technical details.
Detection Methods for CVE-2026-85970
Indicators of Compromise
- Inbound XML payloads containing <!DOCTYPE> declarations with SYSTEM or PUBLIC entity references
- MarkLogic access logs showing outbound requests to internal IP ranges, loopback addresses, or cloud metadata services (169.254.169.254)
- Unexpected read access by the MarkLogic process to files such as /etc/passwd, /etc/shadow, or application configuration files
- HTTP responses from MarkLogic endpoints containing fragments of local file contents
Detection Strategies
- Inspect HTTP request bodies destined for MarkLogic for inline DTDs and external entity declarations
- Correlate authenticated XML POST requests with outbound network connections initiated by the MarkLogic process
- Alert on MarkLogic processes opening files outside their expected data directories
Monitoring Recommendations
- Forward MarkLogic access and error logs to a centralized SIEM for query analysis
- Monitor egress traffic from database servers and flag connections to metadata services or internal management interfaces
- Track MarkLogic version strings across hosts to identify unpatched instances
How to Mitigate CVE-2026-85970
Immediate Actions Required
- Upgrade MarkLogic Server 12.x deployments to 12.1.0 or later
- Upgrade MarkLogic Server 11.x deployments to 11.3.7 or later
- Audit account privileges and restrict XML-posting capability to trusted roles
- Review network egress policies for MarkLogic hosts and block unnecessary outbound destinations
Patch Information
Progress has released fixed versions 12.1.0 and 11.3.7. Refer to the Progress Security Alert Bulletin for the complete list of patched releases and upgrade guidance.
Workarounds
- Restrict network access to MarkLogic application servers so only approved clients can submit XML
- Place a reverse proxy or WAF in front of MarkLogic to strip DOCTYPE declarations from inbound XML
- Apply egress filtering on MarkLogic hosts to block file:// schemes and connections to cloud metadata endpoints
- Reduce authenticated user privileges on endpoints that accept XML until patches are deployed
# Example egress restriction using iptables to block metadata service access
iptables -A OUTPUT -d 169.254.169.254 -j DROP
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

