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-85975 Overview
Progress MarkLogic Server contains a cleartext transmission vulnerability [CWE-319] affecting connections to Amazon Simple Storage Service (S3). Affected versions use unencrypted HTTP transport by default when communicating with S3 endpoints. A network-positioned attacker can intercept data payloads and credentials flowing between MarkLogic Server and S3 buckets. The flaw affects Progress MarkLogic Server 12.x releases before 12.1.0 and 11.x releases before 11.3.7.
Critical Impact
Attackers positioned on the network path between MarkLogic Server and Amazon S3 can intercept sensitive data and AWS credentials transmitted over cleartext connections.
Affected Products
- Progress MarkLogic Server 12.x prior to 12.1.0
- Progress MarkLogic Server 11.x prior to 11.3.7
- Deployments using MarkLogic S3 connectors with default transport settings
Discovery Timeline
- 2026-10-12 - CVE-2026-85975 published to the National Vulnerability Database
- 2026-10-15 - Last updated in NVD database
Technical Details for CVE-2026-85975
Vulnerability Analysis
MarkLogic Server integrates with Amazon S3 for data storage, backup, and forest management operations. The affected releases establish S3 connections over cleartext HTTP rather than HTTPS by default. This exposes all request and response traffic, including object payloads and authentication material, to anyone on the network path.
The weakness maps to [CWE-319] Cleartext Transmission of Sensitive Information. Any adversary with visibility into the traffic can read the data in transit or capture AWS access credentials sent in request headers. The confidentiality impact is high, while integrity and availability are not directly affected.
Root Cause
The root cause is an insecure default configuration in the S3 connector logic. The server does not enforce Transport Layer Security (TLS) when constructing S3 endpoint URLs. Administrators relying on default settings therefore transmit requests through unencrypted channels unless they explicitly configure HTTPS endpoints.
Attack Vector
Exploitation requires network positioning between MarkLogic Server and the Amazon S3 service. Suitable positions include compromised routers, malicious Wi-Fi segments, upstream internet service provider (ISP) taps, or hostile cloud network peers. The attacker performs passive packet capture or active machine-in-the-middle (MITM) interception. No authentication or user interaction on the MarkLogic host is required. Captured credentials can then be replayed to access the backing S3 buckets directly.
See the Progress Security Alert Bulletin for additional technical details.
Detection Methods for CVE-2026-85975
Indicators of Compromise
- Outbound TCP connections from MarkLogic hosts to Amazon S3 endpoints on port 80 instead of port 443
- HTTP requests containing Authorization: AWS4-HMAC-SHA256 headers observed in network captures
- Unexpected access patterns in AWS CloudTrail S3 data events from source IPs that do not match MarkLogic hosts
Detection Strategies
- Inspect MarkLogic configuration for S3 endpoint URLs beginning with http:// rather than https://
- Query running MarkLogic versions and compare against patched releases 12.1.0 and 11.3.7
- Correlate network flow telemetry with S3 service IP ranges to identify unencrypted sessions
Monitoring Recommendations
- Enable AWS CloudTrail data events for S3 buckets accessed by MarkLogic and alert on anomalous GetObject or ListBucket activity
- Deploy network sensors to flag plaintext S3 traffic on port 80 from database infrastructure segments
- Audit AWS Identity and Access Management (IAM) credential usage tied to MarkLogic service accounts for unexpected source addresses
How to Mitigate CVE-2026-85975
Immediate Actions Required
- Upgrade Progress MarkLogic Server 12.x deployments to version 12.1.0 or later
- Upgrade Progress MarkLogic Server 11.x deployments to version 11.3.7 or later
- Rotate any AWS credentials that may have been transmitted over cleartext S3 connections
- Review S3 access logs for the exposure window and investigate anomalous reads
Patch Information
Progress has released fixed builds in MarkLogic Server 12.1.0 and 11.3.7. The updates enforce TLS for S3 connections by default. Refer to the Progress Security Alert Bulletin for download locations and release notes.
Workarounds
- Explicitly configure S3 endpoint URLs to use the https:// scheme in all MarkLogic forest and backup settings
- Restrict outbound traffic from MarkLogic hosts to port 443 only, blocking plaintext HTTP to AWS address ranges
- Route S3 traffic through a VPC endpoint with TLS enforcement to prevent exposure beyond the AWS network boundary
# Configuration example: enforce HTTPS S3 endpoints and block plaintext egress
# 1. Set S3 endpoint to HTTPS in MarkLogic Admin UI or via XQuery
# xdmp:set-server-field("s3-endpoint", "https://s3.amazonaws.com")
# 2. Block cleartext egress to AWS S3 at the host firewall (Linux iptables)
iptables -A OUTPUT -p tcp --dport 80 -d s3.amazonaws.com -j REJECT
iptables -A OUTPUT -p tcp --dport 443 -d s3.amazonaws.com -j ACCEPT
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

