Conductor (<= 3.32.5) - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/products/conductor--3.32.5/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioTue, 13 Oct 2026 14:36:50 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgSSRF Vulnerability in Conductor A2AServicehttps://feed.craftedsignal.io/briefs/2026-10-conductor-ssrf/Tue, 13 Oct 2026 14:36:50 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-10-conductor-ssrf/An SSRF vulnerability in the Conductor-OSS A2AService allows remote attackers to manipulate the agentUrl parameter to force unauthorized internal requests.The Conductor-OSS workflow orchestration platform contains a Server-Side Request Forgery (SSRF) vulnerability in the A2AService component. Specifically, the getAgentCard function within 'ai/src/main/java/org/conductoross/conductor/ai/a2a/A2AService.java' fails to properly sanitize the 'agentUrl' argument. A remote, unauthenticated attacker can supply a malicious URL to this parameter, causing the Conductor server to make unauthorized requests to arbitrary internal or external targets. This vulnerability may be used to probe internal network services, access metadata services in cloud environments, or potentially bypass internal firewall controls. The flaw is present in all versions of Conductor up to and including 3.32.5.

Impact

Successful exploitation allows an attacker to perform internal reconnaissance, potentially access sensitive cloud metadata services, or interact with services inside the network perimeter that are not otherwise accessible. This could lead to information disclosure or serve as a pivot point for further internal network exploitation.

Recommendation

  1. Upgrade to a version of Conductor-OSS that patches CVE-2026-109403.
  2. Implement strict allow-listing for outbound requests originating from the Conductor-OSS application server.
  3. Monitor web access logs for anomalous requests to the A2AService component, particularly those containing suspicious internal IP addresses or private URI schemes in the agentUrl parameter.
  4. Ensure the Conductor process is running with the least privilege necessary, particularly concerning network egress capabilities.
]]>highadvisory