# CVE-2026-92132: Server-side request forgery in Jenkins Gradle Plugin

> Attackers controlling build logs can force Jenkins to connect to malicious URLs, leaking Develocity access keys via Server-Side Request Forgery.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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:** 16 Sep 2026
- **Updated:** 16 Sep 2026
- **Also known as:** GHSA-hcx4-fc58-2r84

## What is CVE-2026-92132?

CVE-2026-92132 is a medium-severity server-side request forgery vulnerability in Jenkins Gradle Plugin, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Jenkins Gradle Plugin 2.19.1252.v15196b_5a_6e10 and earlier requests build scan data from the build scan link detected in the build log, even when a Develocity server URL is configured in the global configuration, allowing attackers able to control the build log to capture the Develocity access key configured in the global configuration by having Jenkins connect to an attacker-specified URL.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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


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

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

## Is CVE-2026-92132 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92132 is a medium-severity server-side request forgery vulnerability in Jenkins Gradle Plugin, published on 16 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-92132 in the wild and no public exploit code.

Affected product: Jenkins Gradle Plugin. 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-92132/ (Markdown: https://insights.sbomify.com/CVE-2026-92132/index.md)
```

## Sources

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

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