Description
GoCD is a continuous deliver server. Prior to 26.1.0, the internal GoCD UI /jobStatus.json API does not validate that a requested server-assigned job ID belongs to the pipeline and stage named in the request. An authenticated user can guess job IDs and retrieve status for jobs in pipelines the user cannot otherwise view, including job names, state, progress timestamps, assigned agent IP addresses and UUIDs, and associated stages and pipelines. The response does not expose console output, artifacts, commands, variables, or configuration. This issue is fixed in version 26.1.0.
Published: 2026-09-21
Score: 4.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Information Disclosure via Authorization Bypass
Action: Patch
AI Analysis

Impact

The GoCD continuous delivery server exposes a job status API endpoint, /jobStatus.json, that does not confirm that the job ID requested belongs to the pipeline and stage specified. As a result, any authenticated user can enumerate job IDs and retrieve status details for jobs in pipelines that they are not authorized to view. The response reveals job names, state, progress timestamps, agent IP addresses, UUIDs, and references to associated stages and pipelines. While console output, artifacts and configuration data are not exposed, the disclosed metadata still constitutes an information disclosure via an authorization bypass.

Affected Systems

The flaw affects all installations of GoCD earlier than version 26.1.0. Any deployment of GoCD that has not been upgraded to 26.1.0 or later is potentially vulnerable. This includes both on‑premises and cloud‑based instances that are still running a pre‑26.1.0 release.

Risk and Exploitability

With a CVSS score of 4.3, the vulnerability is evaluated as moderate severity. No EPSS score is reported, and the vulnerability is not listed in CISA's KEV catalog, suggesting that it has not yet been observed in the wild or is not actively exploited. However, the vulnerability is trivial for an authenticated user because it merely requires guessing job identifiers; enumeration can be automated. As a result, the potential for widespread information leakage is present if an internal attacker or a rogue user gains access to user credentials. Organizations with relaxed pipeline permissions or who allow broad authenticated access to job status are especially at risk.

Generated by OpenCVE AI on September 21, 2026 at 15:37 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to GoCD 26.1.0 or later to apply the official fix.
  • Restrict access to the /jobStatus.json endpoint by configuring your reverse proxy or firewall to allow only users with explicit pipeline view permissions.
  • Perform regular security audits of access controls and monitor job status API usage to detect unauthorized enumeration attempts.

Generated by OpenCVE AI on September 21, 2026 at 15:37 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sat, 26 Sep 2026 18:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Mon, 21 Sep 2026 19:45:00 +0000

Type Values Removed Values Added
First Time appeared Gocd
Gocd gocd
Vendors & Products Gocd
Gocd gocd

Mon, 21 Sep 2026 14:45:00 +0000

Type Values Removed Values Added
Description GoCD is a continuous deliver server. Prior to 26.1.0, the internal GoCD UI /jobStatus.json API does not validate that a requested server-assigned job ID belongs to the pipeline and stage named in the request. An authenticated user can guess job IDs and retrieve status for jobs in pipelines the user cannot otherwise view, including job names, state, progress timestamps, assigned agent IP addresses and UUIDs, and associated stages and pipelines. The response does not expose console output, artifacts, commands, variables, or configuration. This issue is fixed in version 26.1.0.
Title GoCD before 26.1.0 is vulnerable to authorization bypass via job status API
Weaknesses CWE-639
CWE-863
References
Metrics cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-09-25T19:23:52.915Z

Reserved: 2026-06-08T14:00:43.573Z

Link: CVE-2026-52743

cve-icon Vulnrichment

Updated: 2026-09-25T19:23:48.591Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-09-21T15:17:28.950

Modified: 2026-09-25T20:17:07.593

Link: CVE-2026-52743

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-21T19:23:33Z

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key

  • CWE-863

    Incorrect Authorization