Conductor CVE-2026-109190

Exploitation requires an authenticated low-privileged user (CVSS PR:L) who can reach the API Tool Configuration component and control the specUrl argument processed by ListApiToolsTask.start. The limiting factor is that the attacker must already be able to create or modify an API tool definition - this is not an unauthenticated flaw - and the server must be positioned to reach valuable internal/metadata targets for the SSRF to yield meaningful data. No special non-default product mode is cited beyond use of the API Tool feature itself; no user interaction is required (UI:N).

This is a medium-severity, low-urgency issue that does not rise to a top patching priority despite being a remotely reachable server-side request forgery (CWE-918). The input CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L) scores 5.3 and explicitly includes E:P, meaning proof-of-concept exploit maturity, which is consistent with the description's statement that the exploit has been publicly disclosed. Critically, the vector carries PR:L, so exploitation requires an already-authenticated low-privileged account - this materially reduces real-world risk versus an unauthenticated SSRF. All impact metrics are only Low (VC:L/VI:L/VA:L) with no scope change (SC:N), indicating limited data exposure rather than full compromise. No EPSS score, no CISA KEV listing, and no SSVC decision data were provided, so exploitation probability and automatability cannot be quantified from this input; the only exploitation signal is the disclosed POC plus the E:P maturity flag. The sole source is VulDB (CNA-style community reporting) with no independent vendor advisory, so affected-version and fix data are unconfirmed. Net: a legitimate but moderate issue - prioritize behind unauthenticated or high-impact flaws.

An attacker who already holds a low-privileged authenticated account on the Conductor instance creates or edits an API Tool configuration and supplies an attacker-controlled value for the specUrl argument. When ListApiToolsTask.start processes it, the server fetches that URL, letting the attacker pivot requests to internal services or cloud metadata endpoints. A public exploit/POC has been disclosed, lowering the practical barrier to reproduction.