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-85971 Overview
Progress MarkLogic Server assigns overly permissive operating-system permissions to certain log files. The flaw affects MarkLogic Server 12.x releases before 12.1.0 and 11.x releases before 11.3.7. A local user with access to the host can read sensitive log data or alter log contents, undermining confidentiality and integrity controls.
The weakness is tracked under CWE-732: Incorrect Permission Assignment for Critical Resource. Progress disclosed the issue in its October 2026 security bulletin.
Critical Impact
Local users on MarkLogic hosts can read or tamper with log files, exposing operational data and enabling tampering that could obscure attacker activity.
Affected Products
- Progress MarkLogic Server 12.x releases before 12.1.0
- Progress MarkLogic Server 11.x releases before 11.3.7
- Existing log files created before the patch (permissions are not retroactively corrected)
Discovery Timeline
- 2026-10-12 - CVE-2026-85971 published to NVD
- 2026-10-15 - Last updated in NVD database
Technical Details for CVE-2026-85971
Vulnerability Analysis
MarkLogic Server writes operational and audit information to log files on the underlying operating system. In affected versions, the server creates these files with permissions that extend read and write access beyond the intended service accounts. Any local user with shell or filesystem access to the MarkLogic host can therefore interact with the logs.
The practical impact is twofold. First, logs often contain query fragments, URIs, user identifiers, and other operational metadata that should remain restricted to administrators. Second, write access enables a local actor to delete or modify records that would otherwise support incident response and audit trails.
According to the Progress MarkLogic Security Bulletin, the corrected default permissions apply only to newly created and rotated log files. Logs created before patching retain their original permissions and require manual remediation.
Root Cause
The root cause is an insecure permission assignment during log file creation. MarkLogic Server did not restrict chmod or equivalent OS-level permission settings to the service account owning the database process. This maps to [CWE-732], where a critical resource is made available to actors outside its intended trust boundary.
Attack Vector
Exploitation requires local access and low privileges on the MarkLogic host. No user interaction is needed. An unprivileged local account can enumerate the MarkLogic log directory, read sensitive entries, and selectively overwrite or truncate files to disrupt forensic review. The vulnerability does not provide a direct path to code execution but materially weakens detection and response capability on the affected server.
The vulnerability is described in prose only; no public proof-of-concept is required because exploitation reduces to standard filesystem operations against misconfigured files.
Detection Methods for CVE-2026-85971
Indicators of Compromise
- Log files under the MarkLogic data directory with world-readable or group-writable permission bits set
- Unexpected gaps, truncations, or timestamp anomalies in ErrorLog.txt, AccessLog.txt, or audit logs
- Access to MarkLogic log paths by user accounts other than the configured MarkLogic service user
Detection Strategies
- Audit filesystem permissions on all MarkLogic log directories and compare against the service account's expected ownership and mode
- Enable OS-level file integrity monitoring on MarkLogic log paths to flag writes by non-service accounts
- Correlate authentication and shell session telemetry with filesystem access events targeting MarkLogic log directories
Monitoring Recommendations
- Forward MarkLogic audit logs to a centralized log store immediately after rotation to limit tamper windows
- Alert on chmod, chown, or deletion operations against MarkLogic log files executed by non-MarkLogic users
- Review local user and group membership on MarkLogic hosts to ensure only administrators and the service account can reach the log directory
How to Mitigate CVE-2026-85971
Immediate Actions Required
- Upgrade MarkLogic Server to version 12.1.0 or later on the 12.x branch, or 11.3.7 or later on the 11.x branch
- After patching, manually correct permissions on pre-existing log files because the fix only applies to newly created and rotated logs
- Restrict interactive and SSH access on MarkLogic hosts to administrators only
Patch Information
Progress published fixed releases referenced in the Progress MarkLogic Security Bulletin. Apply 12.1.0 for the 12.x branch or 11.3.7 for the 11.x branch. Confirm that log rotation runs after upgrade so newly rotated files inherit the corrected default permissions.
Workarounds
- Manually tighten permissions on the MarkLogic log directory so that only the MarkLogic service account and administrators have read or write access
- Move log storage onto a filesystem or mount point with restrictive default ACLs until patching is complete
- Enforce least privilege for local accounts on MarkLogic hosts and remove shell access for users without an operational need
# Example: restrict MarkLogic log directory permissions on Linux
# Replace /var/opt/MarkLogic/Logs with your deployment path
sudo chown -R daemon:daemon /var/opt/MarkLogic/Logs
sudo chmod 750 /var/opt/MarkLogic/Logs
sudo find /var/opt/MarkLogic/Logs -type f -exec chmod 640 {} \;
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

