# CVE-2026-55632: GoCD is vulnerable to authorization bypass via pipeline structure API

> Authenticated users can bypass authorization checks to enumerate usernames and roles via the pipeline structure API, facilitating targeted attacks.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-57pf-j652-c3c9

## What is CVE-2026-55632?

CVE-2026-55632 is a medium-severity missing authorization vulnerability in gocd, published on 23 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

GoCD is a continuous deliver server. From 20.2.0 until 26.1.0, the internal pipeline structure API used for autocompletion while editing pipeline, template, environment, and user-preference configuration returns its users-and-roles mode to regular authenticated users without requiring an administrator role. A lower-privileged user can enumerate configured user names and available role names, which can facilitate attacks against those users. The response does not reveal which roles are assigned to each user, and the endpoint cannot modify data. This issue is fixed in version 26.1.0.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-55632?


## How do I fix CVE-2026-55632?

No fix has been published for CVE-2026-55632 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-55632 being exploited?

There is no known exploitation of CVE-2026-55632 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-55632 and fix it if it is affected.

What it is: CVE-2026-55632 is a medium-severity missing authorization vulnerability in gocd, published on 23 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-55632 in the wild and no public exploit code.

Affected product: gocd. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-55632/ (Markdown: https://insights.sbomify.com/CVE-2026-55632/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-55632
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-55632
- OSV: https://osv.dev/vulnerability/CVE-2026-55632

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-55632/
Summaries are generated and may contain mistakes; the official description above is the record.