# CVE-2026-52740: GoCD is vulnerable to pipeline template view API authorization bypass

> An authenticated user can bypass view permissions to read pipeline template configurations by using nonstandard HTTP method capitalization.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA: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:** 21 Sep 2026
- **Updated:** 21 Sep 2026
- **Also known as:** GHSA-9jfm-4f6v-79wh

## What is CVE-2026-52740?

CVE-2026-52740 is a medium-severity missing authorization vulnerability in gocd, published on 21 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 18.7.0 until 26.1.0, the Get Template Config API compares HTTP method names case-sensitively when selecting authorization filters. A lower-privileged authenticated user can send a request with nonstandard HTTP method capitalization to retrieve a pipeline template by name without the required view permission and read its configuration. API operations that modify data are not affected, secure variables remain encrypted, and deployments whose reverse proxy rejects non-uppercase HTTP methods are not affected. This issue is fixed in version 26.1.0.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-52740 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-52740 is a medium-severity missing authorization vulnerability in gocd, published on 21 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-52740 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-52740/ (Markdown: https://insights.sbomify.com/CVE-2026-52740/index.md)
```

## Sources

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

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