External risk intelligence

MarkLogic Server HTTP Request Smuggling Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-9190

The vulnerability exists in an HTTP App Server commonly deployed to handle web traffic. As a server designed to process HTTP requests, often positioned behind or acting as part of an edge infrastructure, it is frequently exposed to network traffic, making it a likely target for external reachability in typical web application deployments.

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical security vulnerability has been identified in Progress MarkLogic Server's HTTP App Server, which could allow unauthenticated attackers to bypass security controls, hijack user sessions, or steal credentials. This issue arises from how the server handles specific HTTP request headers, potentially leading to security breaches if not addressed.

  • Attackers could bypass security checks.
  • It enables session hijacking and credential theft.
  • Confirm relevance and assess potential exposure.

Attack Path

How an attacker could exploit the issue

A remote attacker can exploit this vulnerability by sending specially crafted HTTP requests that trick a reverse proxy and the MarkLogic Server into processing them incorrectly. This misinterpretation can allow the attacker to bypass security measures, potentially taking over a user's session or stealing credentials.

  • Requires network access.
  • Triggered by malformed HTTP requests.
  • Risk of unauthorized access and data theft.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, a crafted HTTP request can cause a reverse proxy and MarkLogic Server to misinterpret request boundaries due to differing handling of Content-Length and Transfer-Encoding headers. This could allow an attacker to bypass authentication and authorization controls, hijack user sessions, or steal credentials.

  • Authentication and session data at risk.
  • Different request interpretation by proxy.
  • Unauthorized access and credential theft.

Operational Fix

Recommended remediation, mitigation, and detection steps

The Progress MarkLogic Server HTTP App Server is likely managed by platform or infrastructure teams responsible for core application services, with application owners needing to confirm specific deployments and business criticality. The first step involves identifying all instances of the affected server, assessing their reachability and business impact, and then coordinating with vendor management for the appropriate fix.

  • Platform and application teams own the issue.
  • Verify external reachability and business impact.
  • Coordinate with vendor for remediation.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Progress MarkLogic Server?

Progress MarkLogic Server is a multi-model database platform designed to store, manage, and query complex data. Its built-in HTTP App Server component allows it to function as a web server, enabling direct communication with applications and handling incoming web traffic.

What does CWE-444 mean for CVE-2026-9190?

CWE-444 refers to HTTP Request Smuggling. This weakness occurs when a server and a front-end proxy disagree on where one HTTP request ends and the next begins. In CVE-2026-9190, this disagreement allows attackers to hide malicious requests inside legitimate ones, effectively bypassing security controls.

How is this vulnerability triggered?

An attacker triggers this by sending a crafted HTTP request containing both Content-Length and Transfer-Encoding headers. The bug does not occur with standard, well-formed requests. It specifically relies on the confusion created when the MarkLogic Server and a reverse proxy interpret these conflicting headers differently.

Is my instance at risk according to Halo Surface Signal?

Halo Surface Signal flags this as likely to be exposed because MarkLogic Server is frequently deployed to handle web traffic. Because the HTTP App Server often sits at the edge of infrastructure, instances accessible from the internet are at a higher risk of being reached by external threats compared to internal-only services.

Do I need to patch my MarkLogic Server?

Yes, you should begin by identifying all instances of MarkLogic Server in your environment. Evaluate which systems are reachable from the network and coordinate with your vendor management team to apply the necessary updates to reach the secure, patched versions mentioned in the official security bulletin.

References