dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-9195

CRITICAL · 9.3 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 No privileges 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
A cross-site scripting vulnerability in the Query Console of Progress MarkLogic Server before 11.3.6 and 12.0.3 allows a remote attacker who lures an authenticated administrator to a crafted URL to execute arbitrary JavaScript in the administrator's browser session, capture credentials, and perform privileged actions on the administrator's behalf.

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

A reflected cross-site scripting (XSS) vulnerability exists in the Query Console component of Progress MarkLogic Server versions prior to 11.3.6 and 12.0.3. An attacker can craft a malicious URL that, when visited by an authenticated administrator, causes arbitrary JavaScript to execute in the administrator's browser session, enabling credential theft and privileged action execution.

MitigationUpgrade MarkLogic Server to version 11.3.6 or 12.0.3 or later to resolve the XSS vulnerability in the Query Console.

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
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

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

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 Server admin interface (typically port 8001) or use the admin API endpoint to retrieve the server version. Alternatively, check the MarkLogic installation logs or execute 'xdmp:version()' in Query Console if accessible.
    Affected if The installed version is below 11.3.6 or below 12.0.3 (for example, 11.3.5, 12.0.2, or earlier releases).
  2. Confirm administrative access exists
    Verify that there is at least one authenticated administrator account configured in MarkLogic Server. Check the admin users list via the admin interface or admin API.
    Affected if An authenticated administrator user account exists and can log in to the admin interface or Query Console.

You are affected if your MarkLogic Server version is prior to 11.3.6 or prior to 12.0.3, the Query Console component is accessible, and an authenticated administrator account exists to trigger the reflected XSS payload.

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 or 12.0.3 or later to resolve the XSS vulnerability in the Query Console.

Recommended fix High confidence

Upgrade to MarkLogic Server 11.3.6 or 12.0.3 (depending on your major version track)

  1. 1. Identify the current MarkLogic Server version by navigating to the Admin Interface > Status > Version or running 'xdmp:version()' in Query Console.
  2. 2. If running a version before 11.3.6 (10.x or 11.0.0-11.3.5), plan upgrade to version 11.3.6 or later.
  3. 3. If running a version before 12.0.3 (12.0.0-12.0.2), plan upgrade to version 12.0.3 or later.
  4. 4. Backup all database configurations, forests, and security documents before proceeding.
  5. 5. Download the appropriate fixed version (11.3.6 or 12.0.3) from the Progress Customer Portal or official distribution channels.
  6. 6. Follow the standard MarkLogic Server upgrade procedure: stop the server, run the installer for the new version, and restart the server.
  7. 7. After upgrade, verify the Query Console is functional and the version number matches the target fixed release.
  8. 8. As a best practice, clear browser cookies and session data before accessing the upgraded Query Console.
Caveat Standard minor version upgrade - minimal breaking changes expected, but review release notes for any deprecation notices

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9195 — 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-9195 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