CVE-2026-9203: Progress MarkLogic Server SSRF Vulnerability

CVE-2026-9203 Overview

CVE-2026-9203 is a server-side request forgery (SSRF) vulnerability [CWE-918] in Progress MarkLogic Server before versions 11.3.6 and 12.0.3. The flaw allows an authenticated user with low-privileged roles to bypass protections guarding cloud instance metadata endpoints. An attacker who successfully exploits the vulnerability can retrieve cloud credentials associated with the host instance. These credentials can then be used to compromise cloud resources reachable from the MarkLogic host. The vulnerability affects deployments running in cloud environments such as AWS, Azure, and GCP, where metadata services expose sensitive identity and access data over an internal HTTP endpoint.

Critical Impact
Authenticated low-privileged users can extract cloud instance credentials and pivot to compromise adjacent cloud resources.

Affected Products

Progress MarkLogic Server versions prior to 11.3.6
Progress MarkLogic Server versions prior to 12.0.3
MarkLogic instances deployed on cloud platforms exposing metadata endpoints

Discovery Timeline

2026-08-05 - CVE-2026-9203 published to NVD
2026-08-05 - Last updated in NVD database
August 2026 - Progress publishes MarkLogic Critical Security Alert Bulletin

Technical Details for CVE-2026-9203

Vulnerability Analysis

The vulnerability stems from insufficient validation of outbound HTTP requests initiated by the MarkLogic Server. An authenticated user with low-privileged roles can craft requests that cause the server to fetch attacker-specified URLs. Existing protections that block requests to cloud instance metadata endpoints such as 169.254.169.254 can be bypassed through the affected functionality. Once the metadata endpoint is reached, the server returns credential material scoped to the host instance's IAM role. These credentials frequently grant access to storage buckets, secrets managers, and other cloud services in the deployment account. The scope-changed nature of this issue means impact extends beyond the vulnerable MarkLogic process into the surrounding cloud environment.

Root Cause

The root cause is incomplete filtering of URLs and destination hosts in MarkLogic Server functions that perform server-side HTTP fetches. The metadata endpoint filter can be evaded, permitting SSRF against link-local addresses that expose cloud credentials.

Attack Vector

Exploitation requires network access to the MarkLogic Server and authentication with a low-privileged role. The attacker submits a crafted request that triggers a server-side HTTP fetch to a cloud metadata URL. The response, containing temporary credentials, is then returned to or observable by the attacker. See the Progress Security Alert Bulletin for vendor-supplied technical details.

Detection Methods for CVE-2026-9203

Indicators of Compromise

Outbound HTTP requests from MarkLogic Server processes to 169.254.169.254 or equivalent cloud metadata addresses
Unusual use of low-privileged MarkLogic accounts to invoke HTTP fetch functions or XQuery/JavaScript network APIs
Cloud audit log entries showing IAM role activity from the MarkLogic host to services the application does not normally access
Egress connections from database hosts to unfamiliar external URLs supplied as parameters

Detection Strategies

Enable and review MarkLogic access and audit logs for HTTP client function calls made by non-administrative roles
Correlate MarkLogic host network telemetry with cloud provider metadata service access patterns
Alert on any process on database hosts issuing requests to link-local metadata IPs when not expected by the workload

Monitoring Recommendations

Ingest MarkLogic audit logs and host network flows into a centralized analytics platform for correlation with cloud IAM activity
Baseline legitimate outbound destinations from MarkLogic nodes and alert on deviations, particularly to 169.254.169.254
Monitor cloud provider CloudTrail, Activity Log, or Audit Log entries for use of instance role credentials from unusual source IPs

How to Mitigate CVE-2026-9203

Immediate Actions Required

Upgrade Progress MarkLogic Server to version 11.3.6, 12.0.3, or later
Rotate any IAM credentials and instance role session tokens associated with MarkLogic hosts if exploitation is suspected
Audit low-privileged MarkLogic role assignments and remove unnecessary access to HTTP fetch functionality
Review cloud audit logs for anomalous use of the MarkLogic host instance role

Patch Information

Progress has released fixed versions 11.3.6 and 12.0.3 addressing the SSRF bypass. Refer to the Progress Security Alert Bulletin for full patch details and download locations.

Workarounds

Enforce Instance Metadata Service v2 (IMDSv2) on AWS EC2 hosts to require session tokens for metadata access
Restrict egress from MarkLogic hosts using host firewalls or security groups to block link-local metadata addresses where feasible
Limit permissions attached to the MarkLogic host instance role to the minimum required by the workload
Remove HTTP client function privileges from roles that do not require them

bash

# Configuration example: block link-local metadata access at the host firewall (Linux iptables)
iptables -A OUTPUT -d 169.254.169.254 -m owner ! --uid-owner marklogic-admin -j DROP

# AWS: enforce IMDSv2 on the MarkLogic instance
aws ec2 modify-instance-metadata-options \
  --instance-id i-0123456789abcdef0 \
  --http-tokens required \
  --http-endpoint enabled