dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2026-8709

CRITICAL · 9.9 CVSS v3.1 Published 2026-08-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click 14 days old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An improper privilege management vulnerability in the REST API document patch operation of Progress MarkLogic Server before 11.3.6 and 12.0.3 allows an authenticated user with a low-privileged REST role to escalate privileges and execute privileged operations against the Security database.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a privilege escalation vulnerability in Progress MarkLogic Server's REST API document patch operation. An authenticated user with a low-privileged REST role can exploit improper privilege management to escalate their privileges and execute privileged operations against the Security database, potentially gaining full administrative access.

MitigationUpgrade MarkLogic Server to version 11.3.6, 12.0.3, or later to remediate this vulnerability. Additionally, review and restrict REST API role permissions until the upgrade is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine MarkLogic Server version
    Access the MarkLogic Admin Interface or use the admin:server-status() XQuery function to retrieve the installed server version
    Affected if Version is below 11.3.6 or between 12.0.0 and 12.0.2 (inclusive)
  2. Verify REST API is enabled
    Check MarkLogic configuration for REST API server instance existence via Admin Interface or GET /manage/v2/servers REST API endpoint
    Affected if A REST API server instance is running and accessible
  3. Review REST API access logs for Security database operations
    Examine MarkLogic access logs in the Logs directory for POST requests to /v1/documents with patch method targeting the Security database
    Affected if Patch operations on documents in the Security database are logged from low-privileged REST users
  4. Inspect user role assignments
    Query the Security database for users with REST-related roles using admin:users-get-roleids() or review via Admin Interface user management
    Affected if Users with low-privileged REST roles exist and can authenticate to the REST API

Environment is affected if running MarkLogic Server version below 11.3.6 or below 12.0.3 with REST API enabled and low-privileged users able to access document patch operations on the Security database.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade MarkLogic Server to version 11.3.6, 12.0.3, or later to remediate this vulnerability. Additionally, review and restrict REST API role permissions until the upgrade is applied.

Recommended fix High confidence

Upgrade to MarkLogic Server 11.3.6 or later (for 11.x line) or 12.0.3 or later (for 12.x line)

  1. Identify the current MarkLogic Server version by checking the admin interface or running 'xdmp:version()'
  2. Determine which version line (11.x or 12.x) is currently deployed
  3. Plan the upgrade: for 11.x line, upgrade to 11.3.6 or later; for 12.x line, upgrade to 12.0.3 or later
  4. Create a complete backup of all databases, including the Security database, before performing the upgrade
  5. Review Progress MarkLogic upgrade documentation for your specific version path
  6. Perform the upgrade following the official upgrade procedure
  7. After upgrade, verify the new version is running correctly
  8. Confirm the REST API document patch operation now properly enforces privilege boundaries

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8709 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-8709 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data