Description
Progress MarkLogic Server 12.x releases before 12.1.0 and 11.x releases before 11.3.7 assign overly permissive operating-system permissions to certain log files, which could allow a local user to read or alter log data. The corrected default permissions apply to newly created and rotated logs; existing logs retain their current permissions until remediated.
Published: 2026-10-12
Score: 7.1 High
EPSS: < 1% Very Low
KEV: No
Impact: Log data confidentiality and integrity compromise
Action: Upgrade Required
AI Analysis

Impact

The vulnerability lies in incorrect file permissions on log files in older versions of Progress MarkLogic Server. Operating‑system level permissions are set too broadly, enabling any local user to read or change log data. This compromises confidentiality and integrity of logs, allowing an attacker to observe system activity or inject misleading entries.

Affected Systems

Affected versions are all 12.x releases earlier than 12.1.0 and all 11.x releases earlier than 11.3.7 of Progress Software Corporation's MarkLogic Server.

Risk and Exploitability

The CVSS score of 7.1 places this vulnerability in the medium‑to‑high risk category. Since it requires local user privileges, the threat is limited to the local environment. However, logs often contain sensitive diagnostics, so the impact could be significant. Because the EPSS score is unavailable, the likelihood is unknown, but the problem has already been addressed in newer releases. The vulnerability can be exploited by an attacker who gains local access to the server, reading or modifying existing log files. Applying an update addresses the issue for new logs; existing logs keep their original permissions until manually fixed.

Generated by OpenCVE AI on October 12, 2026 at 19:56 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Progress MarkLogic Server to version 12.1.0 or later, or 11.3.7 or later, to apply corrected default permissions for new and rotated logs.
  • Manually reset permissions on any existing log files to restrict access to authorized users only.
  • Modify the file system ACLs or use the chmod command to restrict the log directory and all existing log files to privileged users only, preventing further over‑permissive permissions.

Generated by OpenCVE AI on October 12, 2026 at 19:56 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 14 Oct 2026 11:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Tue, 13 Oct 2026 07:30:00 +0000

Type Values Removed Values Added
First Time appeared Progress Software Corporation
Progress Software Corporation marklogic Server
Vendors & Products Progress Software Corporation
Progress Software Corporation marklogic Server

Mon, 12 Oct 2026 17:00:00 +0000

Type Values Removed Values Added
Description Progress MarkLogic Server 12.x releases before 12.1.0 and 11.x releases before 11.3.7 assign overly permissive operating-system permissions to certain log files, which could allow a local user to read or alter log data. The corrected default permissions apply to newly created and rotated logs; existing logs retain their current permissions until remediated.
Title Incorrect log file permissions in Progress MarkLogic Server
Weaknesses CWE-732
References
Metrics cvssV3_1

{'score': 7.1, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N'}


Subscriptions

Progress Software Corporation Marklogic Server
cve-icon MITRE

Status: PUBLISHED

Assigner: ProgressSoftware

Published:

Updated: 2026-10-14T10:51:06.341Z

Reserved: 2026-09-04T18:43:16.554Z

Link: CVE-2026-85971

cve-icon Vulnrichment

Updated: 2026-10-14T10:41:40.591Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-10-12T17:17:37.750

Modified: 2026-10-15T16:27:17.070

Link: CVE-2026-85971

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-13T07:15:15Z

Weaknesses
  • CWE-732

    Incorrect Permission Assignment for Critical Resource