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-85959 Overview
CVE-2026-85959 affects Progress MarkLogic Server versions 12.x before 12.1.0 and 11.x before 11.3.7. The server does not consistently record successful authentication events in audit logs. This gap limits a customer's ability to detect and investigate unauthorized access or credential misuse. The weakness is classified under CWE-778 (Insufficient Logging). An attacker who authenticates with valid or stolen credentials may leave no reliable audit trail, undermining incident response and forensic workflows. The flaw is reachable over the network with no privileges or user interaction required.
Critical Impact
Successful authentication events may be omitted from audit logs, allowing credential misuse and unauthorized access to proceed undetected across affected MarkLogic Server deployments.
Affected Products
- Progress MarkLogic Server 12.x releases before 12.1.0
- Progress MarkLogic Server 11.x releases before 11.3.7
- Deployments relying on MarkLogic audit logs for authentication monitoring
Discovery Timeline
- 2026-10-12 - CVE-2026-85959 published to the National Vulnerability Database
- 2026-10-15 - Last updated in NVD database
Technical Details for CVE-2026-85959
Vulnerability Analysis
MarkLogic Server generates audit records for security-relevant events, including authentication outcomes. In the affected releases, the server does not consistently emit audit log entries for successful authentication. The missing telemetry leaves defenders without a dependable record of when a user or service account logged in, from where, and under which identity.
Although the vulnerability does not grant code execution or data modification by itself, it reduces defenders' visibility into legitimate-looking access. An attacker using phished, brute-forced, or leaked credentials can log in and query the database while leaving minimal forensic evidence. Correlating lateral movement across downstream systems becomes considerably harder when the authoritative source of authentication activity is incomplete.
Root Cause
The root cause is insufficient logging ([CWE-778]). The MarkLogic audit subsystem does not uniformly invoke the audit emitter on all successful authentication paths. Certain authentication flows bypass or fail to trigger the event write, leaving gaps relative to the expected audit policy configured by administrators.
Attack Vector
Exploitation requires only network reachability to the MarkLogic Server authentication interface. An attacker with valid credentials, obtained through any means, authenticates to MarkLogic and performs actions. Because the authentication event may not be recorded, downstream SIEM correlation, user behavior analytics, and compliance reporting lose fidelity. No special privilege, user interaction, or local access is required.
No public exploit code is required to abuse this condition; the deficiency is observable during normal authentication activity. See the Progress MarkLogic Security Alert Bulletin for vendor technical details.
Detection Methods for CVE-2026-85959
Indicators of Compromise
- Gaps between application-level query activity and corresponding authentication entries in MarkLogic audit logs.
- Session or query records attributed to users with no preceding successful login event.
- Downstream data access from service accounts without a matching MarkLogic authentication record within the same window.
Detection Strategies
- Reconcile MarkLogic query and session telemetry against authentication events to surface sessions lacking a corresponding login record.
- Forward MarkLogic audit logs, application logs, and network authentication telemetry to a centralized data lake for cross-source correlation.
- Monitor edge devices (load balancers, reverse proxies, firewalls) for authenticated connections to MarkLogic ports and compare against server-side audit entries.
Monitoring Recommendations
- Alert on any MarkLogic session activity that cannot be tied to a logged authentication event.
- Track MarkLogic Server version inventory and flag hosts running releases earlier than 12.1.0 or 11.3.7.
- Baseline normal authentication volumes per account and investigate deviations in downstream query activity even when login records appear absent.
How to Mitigate CVE-2026-85959
Immediate Actions Required
- Upgrade MarkLogic Server 12.x deployments to 12.1.0 or later and 11.x deployments to 11.3.7 or later.
- Review existing audit log coverage and treat historical authentication records from affected versions as incomplete during investigations.
- Rotate credentials for privileged MarkLogic accounts if compromise is suspected and audit evidence is inconclusive.
Patch Information
Progress has addressed the issue in MarkLogic Server 12.1.0 and 11.3.7. Refer to the Progress MarkLogic Security Alert Bulletin for the full list of fixed versions and upgrade guidance.
Workarounds
- Restrict network reachability to MarkLogic authentication endpoints using firewall rules and allowlists until the patch is applied.
- Enforce multi-factor authentication at upstream identity providers and reverse proxies to raise the cost of credential misuse.
- Collect authentication telemetry from network and identity layers (reverse proxy, IdP, VPN) to compensate for the audit gap on the MarkLogic server.
# Verify installed MarkLogic Server version on Linux hosts
/opt/MarkLogic/bin/MarkLogic -v
# Confirm the version meets the fixed release threshold
# Expected: 12.1.0 or later, or 11.3.7 or later
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

