Quick answers
- Is CVE-2026-52743 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-52743 being exploited in the wild.
- How severe is CVE-2026-52743?
- Medium severity, with a CVSS score of 4.3, published 21 September 2026.
- Which products and versions are affected?
- ThoughtWorks GoCD prior to 26.1.0.
- Is there a fix for CVE-2026-52743?
- A patch was published on 2026-07-06: Fix released in version 26.1.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-52743 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-52743?
- Check whether you run ThoughtWorks GoCD 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.
Technical details
The /jobStatus.json API endpoint fails to validate that a requested server-assigned job ID belongs to the pipeline and stage specified in the API request. An authenticated attacker can enumerate job IDs and retrieve metadata for jobs in unauthorized pipelines through parameter tampering or ID guessing. The vulnerability requires authentication but does not require user interaction; console output, artifacts, commands, variables, and configuration details are not exposed. The issue is fixed in version 26.1.0 by improving validation logic during job status JSON retrieval.
Affected products
- ThoughtWorks GoCD prior to 26.1.0
Timeline
- 2026-09-21: disclosed
- 2026-07-06: patched: Fix released in version 26.1.0