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-85961 Overview
CVE-2026-85961 affects Progress MarkLogic Server deployments on Microsoft Azure. The flaw causes the server to write security-sensitive authentication information into diagnostic logs under certain configurations. An attacker who gains access to those logs can harvest credentials and reach protected cloud resources without authorization. The issue is tracked as a sensitive information exposure through log files [CWE-532] and affects MarkLogic Server 12.x releases before 12.1.0 and 11.x releases before 11.3.7.
Critical Impact
Authentication material recorded in Azure diagnostic logs can grant attackers unauthorized access to protected cloud resources tied to MarkLogic Server deployments.
Affected Products
- Progress MarkLogic Server 12.x releases before 12.1.0 on Azure
- Progress MarkLogic Server 11.x releases before 11.3.7 on Azure
- Azure deployments configured to emit diagnostic logs containing authentication data
Discovery Timeline
- 2026-10-12 - CVE-2026-85961 published to the National Vulnerability Database (NVD)
- 2026-10-15 - Record last modified in the NVD database
Technical Details for CVE-2026-85961
Vulnerability Analysis
The vulnerability stems from MarkLogic Server emitting security-sensitive authentication information into diagnostic log streams on Azure deployments. The exposure requires no authentication and is reachable over the network when an attacker can access the generated logs. Because the logged data includes authentication material tied to cloud identity, a single read of the affected logs can translate into broader cloud access.
The weakness is categorized as Insertion of Sensitive Information into Log File [CWE-532]. Logging frameworks are generally outside the application trust boundary. Operators, platform services, and third-party log forwarders often have broad read permissions on diagnostic sinks, which widens the pool of actors who can observe the leaked data.
Impact is limited to confidentiality. The CVSS vector reports no impact to integrity or availability, which aligns with an information disclosure class defect rather than code execution or tampering.
Root Cause
MarkLogic Server, when deployed to Azure under specific configurations, fails to redact or suppress authentication tokens and related secrets before writing diagnostic entries. These entries are forwarded to Azure diagnostic log destinations such as storage accounts, Log Analytics workspaces, or Event Hubs. Any identity with read access to those destinations can retrieve the plaintext material.
Attack Vector
Exploitation requires access to the diagnostic logs produced by an affected MarkLogic Server instance. An attacker with reader privileges on the Azure logging sink, a compromised log forwarder, or lateral access through a shared observability pipeline can parse log entries, extract the authentication information, and reuse it against protected cloud resources. The vulnerability does not require user interaction and does not require prior authentication to the MarkLogic Server itself.
No public proof-of-concept exploit is available. The EPSS probability for this CVE is approximately 0.401% as of 2026-10-16.
Detection Methods for CVE-2026-85961
Indicators of Compromise
- Diagnostic log entries from MarkLogic Server containing authentication tokens, bearer values, connection strings, or credential fields in plaintext
- Unexpected read activity against Azure Log Analytics workspaces, storage accounts, or Event Hubs that receive MarkLogic diagnostic output
- Use of MarkLogic-associated cloud identities from source IPs or principals not previously observed
Detection Strategies
- Scan historical MarkLogic diagnostic logs for patterns matching credential formats, OAuth tokens, and Azure SAS tokens
- Correlate reads from logging sinks with subsequent authentication events against the exposed cloud resources
- Alert on anomalous access to protected Azure resources from identities previously used by MarkLogic workloads
Monitoring Recommendations
- Enable Azure diagnostic settings auditing on all storage accounts and workspaces that receive MarkLogic log data
- Monitor Entra ID sign-in logs for the service principals and managed identities associated with MarkLogic deployments
- Flag downloads of MarkLogic log blobs by non-operator identities and investigate out-of-band access patterns
How to Mitigate CVE-2026-85961
Immediate Actions Required
- Upgrade MarkLogic Server 12.x to release 12.1.0 or later and 11.x to release 11.3.7 or later
- Rotate every credential, token, API key, and secret used by affected MarkLogic Azure deployments
- Review and restrict read permissions on all diagnostic log destinations receiving MarkLogic output
- Purge historical log data that contains leaked authentication material where retention policy allows
Patch Information
Progress has released fixed versions in the MarkLogic Server 12.1.0 and 11.3.7 updates. Refer to the Progress MarkLogic Security Bulletin for vendor guidance and download instructions.
Workarounds
- Disable or reconfigure diagnostic logging settings known to emit authentication data until the upgrade is applied
- Apply strict role-based access control to Azure log sinks, limiting access to a minimal set of operator identities
- Route MarkLogic logs through a sanitization pipeline that strips credential patterns before storage
# Example: restrict reader access on an Azure Log Analytics workspace
az role assignment list \
--scope "/subscriptions/<sub-id>/resourceGroups/<rg>/providers/Microsoft.OperationalInsights/workspaces/<workspace>" \
--query "[?roleDefinitionName=='Log Analytics Reader']"
# Remove unnecessary reader assignments
az role assignment delete \
--assignee <principal-id> \
--role "Log Analytics Reader" \
--scope "/subscriptions/<sub-id>/resourceGroups/<rg>/providers/Microsoft.OperationalInsights/workspaces/<workspace>"
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

