Quick answers
- Is CVE-2026-124507 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-124507 being exploited in the wild.
- How severe is CVE-2026-124507?
- Medium severity, with a CVSS score of 5.3, published 9 November 2026.
- Which products and versions are affected?
- Conductor-Oss Conductor up to 3.32.4, 3.33.0, 3.34.0-rc3, 4.0.0-alpha.1.
- Is there a fix for CVE-2026-124507?
- Yes: fixed in <UNKNOWN>. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-124507 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-124507?
- Check whether you run Conductor-Oss Conductor at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: <UNKNOWN>
Technical details
A server-side request forgery (SSRF) vulnerability exists in the WorkflowSystemTask.start function of PlannerContextFetchTask.java in Conductor's PLANNER_CONTEXT_FETCH task handler. The vulnerability stems from improper validation of the url argument, allowing an attacker to supply malicious URLs. The attack is network-accessible and requires no authentication or special preconditions; an attacker can remotely exploit this to force the Conductor server to make requests on their behalf.
Affected products
- conductor-oss Conductor up to 3.32.4, 3.33.0, 3.34.0-rc3, 4.0.0-alpha.1
Timeline
- 2026-11-09: disclosed