CVE-2026-9191 Progress Software Corporation CVE debrief

Who should care

Defenders responsible for MarkLogic Server instances, especially those with REST and XDBC evaluation paths exposed, should assess exposure and prioritize patching. This includes operators managing affected product deployments, platform administrators, vulnerability management teams, and security teams responsible for reviewing and implementing defensive measures.

Why it matters

CVE-2026-9191 allows attackers to execute user-supplied code, potentially leading to unauthorized actions or session compromise in Progress MarkLogic Server instances. Defenders should prioritize verifying exposure and applying patches.

• Potential unauthorized actions or session compromise via user-supplied code execution.
• Possible elevation of privileges or access to sensitive data.
• Required verification of exposure and patching of affected systems.
• Potential disruption of critical business operations if exploited.

Technical summary

Progress MarkLogic Server 12.x releases before 12.1.0 and 11.x releases before 11.3.7 do not sufficiently isolate user-supplied code executed through certain REST and XDBC evaluation paths from HTTP request, response, and session state. This could allow an attacker to perform unauthorized actions or compromise an authenticated session. The vulnerability can be exploited through REST and XDBC evaluation paths, potentially leading to unauthorized actions or session compromise. Defenders should prioritize verifying exposure of MarkLogic Server instances, especially those with REST and XDBC evaluation paths exposed, and apply vendor-provided patches as soon as possible.

Defensive priority

Defenders should prioritize verifying exposure of MarkLogic Server instances, especially those with REST and XDBC evaluation paths exposed, and apply vendor-provided patches as soon as possible.

Recommended defensive actions

• Verify exposure of MarkLogic Server instances, especially those with REST and XDBC evaluation paths exposed.
• Apply vendor-provided patches as soon as possible.
• Review and update inventory to ensure accurate tracking of affected systems.
• Monitor for suspicious activity related to MarkLogic Server instances.
• Perform vulnerability scanning to identify potentially affected systems.
• Implement compensating controls for exposed systems while remediation is scheduled and verified.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The CVE record and source item provide details on the vulnerability, affected versions, and potential impacts. However, there is limited information on exploitation, victims, or specific defensive consequences.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.