MarkLogic Server: Insufficient Logging
CVE-2026-85959 is a high-severity insufficient logging vulnerability in MarkLogic Server from Progress Software, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 11.3.7, 12.1.0 as the first without the flaw, so updating MarkLogic Server to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.4% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update MarkLogic Server to 11.3.7 or 12.1.0, whichever matches your release line, or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Progress Software | MarkLogic Server | 11.0.0 up to, but not including, 11.3.7; 12.0.0 up to, but not including, 12.1.0 | 11.3.7, 12.1.0 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N. Scored by CNA (progress.com).
Official description
Progress MarkLogic Server 12.x releases before 12.1.0 and 11.x releases before 11.3.7 do not consistently record successful authentication events in audit logs, which could limit customers' ability to detect and investigate unauthorized access or credential misuse.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Insufficient Logging
When a security-critical event occurs, the product either does not record the event or omits important details about the event when logging it.
How developers prevent this class of flaw
- Use a centralized logging mechanism that supports multiple levels of detail.
- Ensure that all security-related successes and failures can be logged. When storing data in the cloud (e.g., AWS S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to enable and capture detailed logging information.
- Be sure to set the level of logging appropriately in a production environment. Sufficient data should be logged to enable system administrators to detect attacks, diagnose errors, and recover from attacks. At the same time, logging too much data (CWE-779) can cause the same problems, including unexpected costs when using a cloud environment.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Other references
Other vulnerabilities in MarkLogic Server
- 7.5 High severity
- 7.4 High severity
- 7.4 High severity
- 7.4 High severity
- 7.1 High severity
- 7.1 High severity
Recent Insufficient Logging vulnerabilities
- 8.2 High severity
- 2.7 Low severity
Broadcom VMWare ESX Insufficient Logging Exploited
- 8.2 High severity
- 7.5 High severity
- 10.0 Critical severity
- 7.5 High severity
Spotted an error? Tell us.