Server-side request forgery in Progress MarkLogic Server Azure deployments
Summary
| CVE | CVE-2026-85951 |
|---|---|
| State | PUBLISHED |
| Assigner | ProgressSoftware |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-10-12 16:17:06 UTC |
| Updated | 2026-10-15 20:17:15 UTC |
| Description | Progress MarkLogic Server 12.x releases before 12.1.0 and 11.x releases before 11.3.7 on Azure contain a server-side request forgery vulnerability that could allow an authenticated attacker to access internal cloud services, potentially resulting in unauthorized access to cloud credentials or tokens. |
Risk And Classification
Primary CVSS: v3.1 8.5 HIGH from [email protected]
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N
EPSS: 0.001900000 probability, percentile 0.080480000 (date 2026-10-15)
Problem Types: CWE-918 | CWE-918 CWE-918: Server-Side Request Forgery (SSRF)
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | [email protected] | Secondary | 8.5 | HIGH | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N |
| 3.1 | CNA | CVSS | 8.5 | HIGH | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N |
CVSS v3.1 Breakdown
Attack Vector
NetworkAttack Complexity
LowPrivileges Required
LowUser Interaction
NoneScope
ChangedConfidentiality
HighIntegrity
LowAvailability
NoneCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Progress Software Corporation | MarkLogic Server | affected 11.0.0 11.3.7 custom | Not specified |
| CNA | Progress Software Corporation | MarkLogic Server | affected 12.0.0 12.1.0 custom | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| community.progress.com/s/article/Marklogic-Critical-Security-Alert-Bulletin-October-... | [email protected] | community.progress.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.