Skip to content
Applications

CVE-2026-9193

9.9
Critical
EPSS 0.31%Patch availableAug 6, 2026

Authenticated low-privileged Hadoop role can escalate to privileged ops on MarkLogic Security DB.

common questions

Is CVE-2026-9193 being exploited?

Not confirmed. CVE-2026-9193 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.31% probability of exploitation in the next 30 days.

How severe is CVE-2026-9193?

CVE-2026-9193 is rated Critical with a CVSS score of 9.9. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-9193?

Yes. A fix has been recorded for CVE-2026-9193. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-9193 affect?

CVE-2026-9193 affects Progress MarkLogic Server (Hadoop integration) versions before 11.3.6, Progress MarkLogic Server versions before 12.0.3. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-9193?

Upgrade to 11.3.6 or 12.0.3, restrict Hadoop roles and audit accesses.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Progress MarkLogic Server (Hadoop integration) versions before 11.3.6Progress MarkLogic Server versions before 12.0.3
impact

Authenticated low-priv Hadoop user can escalate privileges to perform privileged operations on the Security DB, alter security config, create admin accounts, or access protected data.

action required

Immediate action required

affected versions
Progress Software Corporation MarkLogic Server
  • affected>= 11.0.0 and < 11.3.6
  • affected>= 12.0.0 and < 12.0.3

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free