PatchSiren cyber security CVE debrief
CVE-2026-85948 Progress Software Corporation CVE debrief
A critical vulnerability exists in Progress MarkLogic Server versions 11.x before 11.3.7 and 12.x before 12.1.0. An XQuery injection flaw in a deprecated Management API package path allows remote attackers with manage-user-level privileges to gain persistent unauthorized administrative control. Defenders should assess exposure, prioritize remediation, and verify affected versions.
- Vendor
- Progress Software Corporation
- Product
- MarkLogic Server
- CVSS
- CRITICAL 9.9
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-10-12
- Original CVE updated
- 2026-10-12
- Advisory published
- 2026-10-12
- Advisory updated
- 2026-10-12
Who should care
Defenders responsible for Progress MarkLogic Server instances, especially those with manage-user-level privileges, should assess exposure and prioritize remediation. This includes operators managing affected versions, platform administrators, vulnerability management teams, and security teams responsible for verifying affected versions and implementing compensating controls.
Why it matters
CVE-2026-85948 allows remote attackers with manage-user-level privileges to gain persistent unauthorized administrative control in Progress MarkLogic Server versions 11.x before 11.3.7 and 12.x before 12.1.0. Defenders should assess exposure, prioritize remediation, and verify affected versions.
- Potential unauthorized administrative control
- Possible elevation of privileges
- Required verification of affected versions
- Necessity for timely remediation
Technical summary
Progress MarkLogic Server 11.x before 11.3.7 and 12.x before 12.1.0 contain an XQuery injection flaw in a deprecated Management API package path. A remote attacker with manage-user-level privileges could exploit this flaw to obtain persistent unauthorized administrative control. The vulnerability allows attackers to inject malicious XQuery code, potentially leading to unauthorized administrative control. Defenders should assess exposure, prioritize remediation, and verify affected versions to mitigate potential impacts.
Defensive priority
High
Recommended defensive actions
- Assess exposure of MarkLogic Server instances, especially versions 11.x before 11.3.7 and 12.x before 12.1.0
- Prioritize remediation of affected versions
- Verify affected versions and inventory of MarkLogic Server instances
- Implement compensating controls, such as restricting access to the Management API
- Review 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
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The CVE record and source item provide details on the vulnerability, affected versions, and potential impact. However, additional information on exploitation, victims, or specific business impacts is not available.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-85948 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-85948
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-85948 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-85948
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Improper privilege management in Progress MarkLogic Server Management API
Unverified legacy reference
URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/85xxx/CVE-2026-85948.json
cve_program_cvelist_v5
-
Source reference
Unverified legacy reference
URL: https://community.progress.com/s/article/Marklogic-Critical-Security-Alert-Bulletin-October-2026
Supplemental source - vendor-advisory
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.