Skip to main content

Progress MarkLogic CVE-2026-85969

| EUVDEUVD-2026-97564 HIGH
Out-of-bounds Write (CWE-787)
2026-10-12 ProgressSoftware GHSA-cc5x-mg69-6h54
7.1
CVSS 3.1 · Vendor: ProgressSoftware
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain valid low-privilege MarkLogic credentials
  2. Delivery
    Send crafted language-processing request
  3. Exploit
    Trigger out-of-bounds write in parser
  4. Execution
    Corrupt server memory
  5. Impact
    Cause instability or limited data modification

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, write limits
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires an authenticated session with at least low-level privileges on MarkLogic Server (CVSS PR:L) and the ability to reach the affected language-processing functionality over the network; it is not exploitable by an anonymous/unauthenticated remote attacker. Only MarkLogic Server 12.x before 12.1.0 and 11.x before 11.3.7 are affected, so patched or older-branch-fixed instances are out of scope. The primary limiting factor is the mandatory pre-existing authentication, which constrains the realistic threat to insiders or attackers who have already obtained credentials or compromised an application account; the vendor does not state a non-default configuration requirement, so default deployments running the affected language-processing feature appear exposed to authenticated users.

Impact

This is a genuine but mid-tier priority rather than a drop-everything emergency. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H, base 7.1) shows a network-reachable, low-complexity flaw with no user interaction, but it explicitly requires PR:L - the attacker must already hold valid authenticated low-privilege credentials on the MarkLogic Server. Impact is skewed toward availability (A:H, server instability / crash) with only limited integrity impact (I:L) and no confidentiality loss (C:N), which is consistent with an out-of-bounds write (CWE-787) that corrupts memory but does not clearly yield full code execution or data disclosure. No EPSS score, CISA KEV listing, or public POC was provided in the input, so there is no signal of active or probable near-term exploitation; the realistic threat is an authenticated insider or an attacker who has already compromised an application/service account abusing crafted language-processing input. Signals are internally consistent (no contradiction between the network vector and the description), but the absence of EPSS/KEV/POC data means exploitation likelihood is genuinely unknown rather than confirmed low.

Exploit ScenarioDerived

An attacker possessing valid low-privilege MarkLogic credentials (or control of a compromised application service account) submits specially crafted input to the affected language-processing functionality over the network, triggering an out-of-bounds write. The memory corruption destabilizes or crashes the server (availability impact) and may allow limited unauthorized modification of data. No public exploit code was identified at time of analysis, and because PR:L is required, exploitation is gated behind prior authentication.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 12, 2026

An out-of-bounds write in the language-processing functionality of Progress MarkLogic Server lets an authenticated remote user with only low-level privileges crash or destabilize the server and, more narrowly, modify limited data. Only MarkLogic Server 12.x releases before 12.1.0 and 11.x releases before 11.3.7 are affected; the CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H) confirms availability is the dominant impact while confidentiality is untouched and integrity impact is limited. The mandatory pre-existing authenticated session is the primary limiting factor, so the realistic threat is an insider or an attacker who already holds valid credentials, and no public exploit code and no confirmed active exploitation were identified at time of analysis.

RemediationAI

Vendor-released patch: upgrade to MarkLogic Server 12.1.0 for the 12.x train, or to 11.3.7 for the 11.x train, per the advisory at https://community.progress.com/s/article/Marklogic-Critical-Security-Alert-Bulletin-October-2026; patching removes the vulnerable language-processing code path and is the only complete fix. Until the upgrade can be staged, apply compensating controls aimed at the mandatory authenticated precondition and at reachability: review and trim MarkLogic user accounts so that only identities that genuinely need query access retain it, reducing the population of credentials an attacker could leverage (trade-off: administrative overhead and possible application breakage where shared service accounts are consolidated); restrict network access to MarkLogic's application and query ports with firewall rules or a reverse proxy so that only trusted application tiers and administrator networks can send requests to the language-processing functionality (trade-off: legitimate clients connecting from other segments must be explicitly allow-listed); and monitor server logs for abnormal terminations or repeated crashes of the query processes, which are the most likely observable symptom of an exploitation attempt (trade-off: high-volume environments generate noise and may require tuning). Because exploitation requires an authenticated session, credential hygiene, MFA at the fronting layer, and prompt revocation of stale accounts materially raise the bar while the upgrade is pending. Note that no public exploit code was identified at time of analysis, so emergency out-of-band remediation is not warranted if patching can be scheduled promptly.

Affected VersionsENISA

MarkLogic Server 12.0.0 <12.1.0
MarkLogic Server 11.0.0 <11.3.7

Affected Packages

euvd marklogic_server fix: 11.3.7, 12.1.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause is CWE-787 (out-of-bounds write), a memory-corruption class in which a buffer is written past its allocated bounds, typically corrupting adjacent heap or stack memory and leading to process crashes, unpredictable behavior, or controlled overwrites. In MarkLogic Server the defect sits in language-processing functionality - the code paths that parse and evaluate query languages and related text handling - so a crafted request reaching that feature drives the write. The CPE cpe:2.3:a:progress_software_corporation:marklogic_server identifies the affected product family, and the vendor advisory notes the flaw affects 12.x before 12.1.0 and 11.x before 11.3.7. Consistent with an out-of-bounds write, the assessed impact is availability-heavy (A:H) with only low integrity impact (I:L) and no confidentiality impact (C:N); the scope is unchanged (S:U), meaning the compromise is contained within the MarkLogic Server security authority rather than crossing a trust boundary. The vendor does not describe a non-default configuration prerequisite, so default deployments that expose the language-processing feature to authenticated users are in scope.

Know when Marklogic Server gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (ProgressSoftware) PRIMARY 7.1 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H
vuln.today AI 7.1 HIGH

Network-reachable language processing (AV:N/AC:L) but requires authenticated low-privilege access (PR:L); memory corruption yields high availability loss (A:H) and limited integrity impact (I:L) with no data disclosure (C:N).

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (ProgressSoftware).

CVSS VectorVendor: ProgressSoftware

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
High

Lifecycle Timeline

2
Patch available
Oct 12, 2026 - 18:03 EUVD
CVE Published
Oct 12, 2026 - 16:37 cve.org
HIGH 7.1

DescriptionCVE.org

Progress MarkLogic Server 12.x releases before 12.1.0 and 11.x releases before 11.3.7 contain an out-of-bounds write vulnerability in certain language-processing functionality. A remote authenticated attacker could exploit this vulnerability to cause server instability or limited modification of data.

Executive ViewAI

Why It Matters

Progress MarkLogic Server, a database platform, is affected by a high-severity vulnerability (CVE-2026-85969) that allows an authenticated user with low-level privileges to crash or destabilize the server, primarily impacting availability with limited integrity effects. Because exploitation requires valid credentials, the main risk comes from insiders or attackers who have already compromised an account, making it crucial for leadership to address potential service disruptions and data integrity concerns. No public exploit code or active exploitation has been identified, but the lack of a vendor patch heightens the need for immediate compensating controls.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include enforcing least privilege and strong authentication for all MarkLogic users, restricting network access to trusted sources, monitoring for abnormal server crashes or language-processing requests, maintaining offline backups, and applying application-layer filtering if possible.

Threat Intelligence Overview

EPSS Score
0.2%
Top 86% exploitable
Prevalence
Medium
enterprise NoSQL/XML database, significant but specialized deployment footprint
Social Media
1
Sightings
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
High

Priority Score

36
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +36
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.

CVE-2026-85948 CRITICAL
9.9 Oct 12

Authenticated XQuery injection in Progress MarkLogic Server 11.x before 11.3.7 and 12.x before 12.1.0 allows a remote at

CVE-2026-85947 CRITICAL
9.9 Oct 12

An authenticated privilege-escalation flaw in Progress MarkLogic Server lets an attacker who already holds forest-manage

CVE-2026-7329 CRITICAL
9.9 Aug 05

Privilege escalation in Progress MarkLogic Server before 11.3.6 and 12.0.3 lets an authenticated user holding only a low

CVE-2026-9193 CRITICAL
9.9 Aug 05

Privilege escalation in Progress MarkLogic Server (versions before 11.3.6 and 12.0.3) lets an authenticated user holding

CVE-2026-8709 CRITICAL
9.9 Aug 05

Privilege escalation in Progress MarkLogic Server before 11.3.6 and 12.0.3 allows an authenticated user holding only a l

CVE-2026-9192 CRITICAL
9.8 Aug 05

Authentication bypass in the ODBC App Server of Progress MarkLogic Server (before 11.3.6 and 12.0.3) lets an unauthentic

CVE-2026-9191 CRITICAL
9.6 Oct 12

Insufficient isolation in Progress MarkLogic Server 12.x before 12.1.0 and 11.x before 11.3.7 allows code executed throu

CVE-2026-9195 CRITICAL
9.3 Aug 05

Stored/reflected cross-site scripting in the Query Console of Progress MarkLogic Server (versions before 11.3.6 and 12.0

CVE-2026-9190 CRITICAL
9.1 Aug 05

HTTP request smuggling in Progress MarkLogic Server's HTTP App Server (versions before 11.3.6 and 12.0.3) lets a remote

CVE-2026-7557 CRITICAL
9.1 Aug 05

Authentication bypass in Progress MarkLogic Server (versions before 11.3.6 and 12.0.3) lets an unauthenticated remote at

CVE-2026-7326 HIGH
8.8 Aug 05

Cross-site request forgery in the Progress MarkLogic Server Admin UI allows a remote attacker to perform privileged admi

CVE-2026-9203 HIGH
8.5 Aug 05

Server-side request forgery in Progress MarkLogic Server before 11.3.6 and 12.0.3 enables authenticated low-privileged u

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy