Skip to main content
VulnerabilityPublished Updated

CVE-2026-9190: Progress Software MarkLogic Server · HTTP Request/Response Smuggling

Affects Progress Software MarkLogic ServerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.1 Critical : upgrade to 12.0.3 or 11.3.6 as a priority.

Data as of 3 Nov 2026, 22:58 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 12.0.3, 11.3.6
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.

What to do

Upgrade Progress Software MarkLogic Server to 12.0.3 or 11.3.6.

Affected software

ProductAffectedFixed in
Progress Software CorporationMarkLogic ServerAffected
  • >=12.0.0 <12.0.3
Fixed in
  • 12.0.3
Progress Software CorporationMarkLogic ServerAffected
  • >=11.0.0 <11.3.6
Fixed in
  • 11.3.6

AI-suggested

Until then, consider deploying additional network-level protections such as strict HTTP header validation or reverse proxy configurations that mitigate HTTP request smuggling risks.

Description

CVE-2026-9190 is an HTTP request smuggling vulnerability in the HTTP App Server component of Progress MarkLogic Server versions 11.0.0 and 12.0.0. This flaw allows a remote attacker to bypass authentication and authorization controls, hijack user sessions, or capture credentials by exploiting inconsistent interpretation of HTTP request boundaries between a reverse proxy and the server when both Content-Length and Transfer-Encoding headers are present in a crafted request.

References

Community reviews

Loading reviews…