# CVE-2026-85961: Progress MarkLogic Server sensitive information disclosure in diagnostic logs

Source: https://junglewise.ai/threats/cve-2026-85961-on-azure-deployments-progress-marklogic-server-12-x-releases  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-12. Updated: 2026-10-16  
License: CC BY 4.0 with a link back

CVE-2026-85961 · Severity: high · CVSS 7.5 · Published 2026-10-12

MarkLogic Server, a database platform commonly deployed on cloud infrastructure, may record authentication credentials and other sensitive security information in diagnostic logs under certain configurations. An attacker with access to these logs could extract credentials and gain unauthorized access to protected databases and cloud resources.

Technologies: [Progress Marklogic Server](https://junglewise.ai/threats/technologies/marklogic-server). Vendors: [Progress](https://junglewise.ai/threats/vendors/progress).

## Quick answers

**Is CVE-2026-85961 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-85961 being exploited in the wild.

**How severe is CVE-2026-85961?** High severity, with a CVSS score of 7.5, published 12 October 2026.

**Which products and versions are affected?** Progress Marklogic Server 11.x before 11.3.7, 12.x before 12.1.0.

**Is there a fix for CVE-2026-85961?** Yes: fixed in MarkLogic Server 11.3.7, 12.1.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-85961 attacked?** It is attacked over the network, in a hosted service.

**Am I affected by CVE-2026-85961?** Check whether you run Progress Marklogic Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in MarkLogic Server 11.3.7, 12.1.0

## Technical details

The vulnerability involves improper logging of authentication credentials in diagnostic logs on Azure deployments. An attacker with access to diagnostic logs (via cloud storage misconfiguration or compromised credentials) can extract authentication material and use it to gain unauthorized database access. The issue affects MarkLogic Server versions 12.x before 12.1.0 and 11.x before 11.3.7.

## Affected products

- Progress MarkLogic Server 11.x before 11.3.7, 12.x before 12.1.0

## Timeline

- 2026-10-12: disclosed

## References

- [https://community.progress.com/s/article/Marklogic-Critical-Security-Alert-Bulletin-October-2026](https://community.progress.com/s/article/Marklogic-Critical-Security-Alert-Bulletin-October-2026)

## Related threats

- [Progress MarkLogic Server HTTP response splitting in Query Console](https://junglewise.ai/threats/cve-2026-85976-progress-marklogic-server-12-x-releases-before-12-1-0-and-11-x)
- [Progress MarkLogic Server cleartext S3 transport default](https://junglewise.ai/threats/cve-2026-85975-progress-marklogic-server-12-x-releases-before-12-1-0-and-11-x)
- [Progress MarkLogic Server TLS hostname validation bypass](https://junglewise.ai/threats/cve-2026-85974-progress-marklogic-server-12-x-releases-before-12-1-0-and-11-x)
- [Progress MarkLogic Server cleartext cluster-management communications](https://junglewise.ai/threats/cve-2026-85973-progress-marklogic-server-12-x-releases-before-12-1-0-may-use)
- [Progress MarkLogic Server Kerberos authentication verification bypass](https://junglewise.ai/threats/cve-2026-85972-progress-marklogic-server-12-x-releases-before-12-1-0-and-11-x)