Skip to main content
Vulnerability Database/CVE-2026-109190

CVE-2026-109190: Conductor-OSS SSRF Vulnerability

CVE-2026-109190 is a server-side request forgery flaw in conductor-oss conductor 3.31.2 affecting the ListApiToolsTask component. Attackers can exploit this remotely to manipulate server requests. This article covers technical details, impact assessment, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-109190 Overview

CVE-2026-109190 is a server-side request forgery (SSRF) vulnerability in Conductor OSS version 3.31.2. The flaw resides in the ListApiToolsTask.start function within ListApiToolsTask.java, part of the API Tool Configuration component. An attacker can manipulate the specUrl argument to force the server to issue arbitrary outbound requests. The attack is remotely exploitable and requires low-level privileges. Public disclosure of the exploit technique has occurred, increasing the risk of opportunistic abuse against exposed Conductor deployments.

Critical Impact

Authenticated remote attackers can coerce the Conductor backend into sending HTTP requests to attacker-chosen destinations, enabling internal network reconnaissance and interaction with internal services.

Affected Products

  • conductor-oss Conductor 3.31.2
  • Component: API Tool Configuration (ListApiToolsTask.java)
  • Function: ListApiToolsTask.start

Discovery Timeline

  • 2026-10-13 - CVE-2026-109190 published to the National Vulnerability Database
  • 2026-10-13 - Last updated in NVD database

Technical Details for CVE-2026-109190

Vulnerability Analysis

The vulnerability is classified as Server-Side Request Forgery [CWE-918]. The affected code path accepts a user-supplied specUrl parameter and uses it to initiate a server-side HTTP request without sufficient validation of the target destination. Because the Conductor server performs the fetch on behalf of the caller, an attacker can direct requests toward internal hosts, metadata endpoints, or non-public services that are otherwise unreachable from the internet. The vulnerability permits low-impact disclosure, modification, and availability effects within the application scope, as reflected by the CVSS 4.0 vector supplied by the publisher.

Root Cause

The root cause is missing or inadequate validation of the specUrl argument before it is dereferenced by ListApiToolsTask.start. The function does not restrict schemes, hostnames, or IP ranges, nor does it enforce an allowlist of acceptable upstream API specification sources. Any user with the ability to submit a task definition that triggers this code path can control the destination of the outbound request.

Attack Vector

Exploitation requires network access to the Conductor API and authenticated access with low privileges. The attacker submits a crafted task or configuration whose specUrl points to an internal resource such as http://127.0.0.1, link-local metadata endpoints like http://169.254.169.254/latest/meta-data/, or internal service URLs. The Conductor server then issues the request and may return response data or side-channel observations to the attacker. No user interaction is required. Public technical details are referenced in the VulDB entry for CVE-2026-109190 and the associated VulDB vulnerability record #416898.

Detection Methods for CVE-2026-109190

Indicators of Compromise

  • Outbound HTTP requests from the Conductor server process to internal IP ranges (RFC1918), loopback addresses, or cloud metadata services such as 169.254.169.254.
  • Task definitions or workflow submissions containing a specUrl value pointing to non-public hosts, raw IP addresses, or non-HTTP schemes.
  • Unexpected error entries in Conductor logs referencing ListApiToolsTask with unusual URL targets.

Detection Strategies

  • Inspect Conductor application logs for invocations of ListApiToolsTask.start and correlate the specUrl argument against an allowlist of expected API specification hosts.
  • Deploy egress monitoring on the Conductor host to flag outbound connections that deviate from the baseline of permitted upstream endpoints.
  • Review authenticated API traffic to Conductor for repeated task submissions that vary only in the specUrl field, which is characteristic of SSRF probing.

Monitoring Recommendations

  • Forward Conductor application and reverse-proxy logs to a central analytics platform for retention and query.
  • Alert on any request originating from the Conductor service account that targets cloud instance metadata IPs or internal management interfaces.
  • Baseline normal task-submission patterns per user and flag anomalous spikes from low-privilege accounts.

How to Mitigate CVE-2026-109190

Immediate Actions Required

  • Restrict network egress from Conductor hosts to only the destinations required for legitimate API specification retrieval.
  • Audit existing Conductor accounts and remove task-definition privileges from users who do not require them.
  • Place Conductor behind an authenticated reverse proxy and block direct exposure of its API to the internet.

Patch Information

At the time of publication, no fixed version has been identified in the NVD record for CVE-2026-109190. Monitor the conductor-oss project and the VulDB advisory for updated patch information and apply upgrades as soon as they are released.

Workarounds

  • Implement an allowlist of permitted hostnames for the specUrl parameter at a proxy or web application firewall tier.
  • Block Conductor outbound access to loopback (127.0.0.0/8), link-local (169.254.0.0/16), and internal (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) ranges unless explicitly required.
  • Require code review of any task configuration that supplies external URLs before it is promoted to production.
bash
# Example egress restriction using iptables on the Conductor host
iptables -A OUTPUT -m owner --uid-owner conductor -d 127.0.0.0/8 -j REJECT
iptables -A OUTPUT -m owner --uid-owner conductor -d 169.254.0.0/16 -j REJECT
iptables -A OUTPUT -m owner --uid-owner conductor -d 10.0.0.0/8 -j REJECT
iptables -A OUTPUT -m owner --uid-owner conductor -d 172.16.0.0/12 -j REJECT
iptables -A OUTPUT -m owner --uid-owner conductor -d 192.168.0.0/16 -j REJECT

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.