PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-85951 Progress Software Corporation CVE debrief

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. An authenticated attacker could exploit this to access internal cloud services, potentially leading to unauthorized access to cloud credentials or tokens. The vulnerability is particularly concerning for defenders responsible for Progress MarkLogic Server instances on Azure, as it could allow attackers to access sensitive cloud resources. To mitigate this vulnerability, defenders should verify exposure, apply vendor remediation, and monitor for suspicious activity.

Vendor
Progress Software Corporation
Product
MarkLogic Server
CVSS
HIGH 8.5
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 on Azure, particularly those using versions 11.x before 11.3.7 and 12.x before 12.1.0, should assess exposure and apply remediation.

Why it matters

CVE-2026-85951 is a server-side request forgery vulnerability in Progress MarkLogic Server on Azure deployments. Defenders should verify exposure, apply vendor remediation, and monitor for suspicious activity to prevent potential unauthorized access to cloud credentials or tokens.

  • Potential unauthorized access to cloud credentials or tokens.
  • Possible exploitation by authenticated attackers to access internal cloud services.
  • Requires verification of Progress MarkLogic Server versions and application of patches.
  • Monitoring for suspicious activity related to cloud credentials or tokens is necessary.

Technical summary

Progress MarkLogic Server 12.x releases before 12.1.0 and 11.x releases before 11.3.7 on Azure are vulnerable to server-side request forgery. An authenticated attacker could exploit this to access internal cloud services, potentially resulting in unauthorized access to cloud credentials or tokens. The vulnerability is caused by inadequate validation of user requests, allowing attackers to manipulate requests and access sensitive cloud resources. To prevent exploitation, defenders should prioritize verifying exposure and applying vendor remediation for Progress MarkLogic Server instances on Azure.

Defensive priority

Defenders should prioritize verifying exposure and applying vendor remediation for Progress MarkLogic Server instances on Azure, particularly for versions 11.x before 11.3.7 and 12.x before 12.1.0.

Recommended defensive actions

  • Verify Progress MarkLogic Server version and apply patches for 11.x and 12.x releases.
  • Restrict access to internal cloud services.
  • Monitor for suspicious activity related to cloud credentials or tokens.
  • Review compensating controls for exposed systems while remediation is scheduled and verified.
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review.
  • 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 in Progress MarkLogic Server. The vendor advisory from Progress Software Corporation is referenced, offering guidance on addressing the issue.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-85951 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-85951

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-85951 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-85951

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental 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.