# Incorrect Permission Assignment for Critical Resource in Jenkins Credentials Binding Plugin

Advisory record · `GHSA-gqm2-2gcx-p88w`

- **Identifiers:** `GHSA-gqm2-2gcx-p88w` · `CVE-2022-20616`
- **State:** Confirmed
- **Severity:** CVSS 4.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-732](https://cwe.mitre.org/data/definitions/732.html) · [CWE-862](https://cwe.mitre.org/data/definitions/862.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 13 Jan 2022
- **Updated:** 3 Jul 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 13 Jan 2022, 00:01 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.jenkins-ci.plugins:credentials-binding` (Maven): affected `>=1.25, <1.27.1 || <1.24.1`; fixed in `1.27.1`, `1.24.1`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Jenkins Credentials Binding Plugin versions from 1.25 before 1.27.1 and before 1.24.1 are affected. An attacker with Overall/Read access can exploit a missing permission check in a form validation method to determine whether a credential ID refers to a secret file credential and whether that file is a zip file. Upgrade to version 1.27.1 or 1.24.1.

Written 8 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 4.3 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.0088, the 59th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:13 UTC: First seen by agentprime
- 31 Oct 2026, 15:13 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-gqm2-2gcx-p88w)

## Sources

- [GitHub Advisory Database: GHSA-gqm2-2gcx-p88w](https://github.com/advisories/GHSA-gqm2-2gcx-p88w)
- [OSV: GHSA-gqm2-2gcx-p88w](https://osv.dev/vulnerability/GHSA-gqm2-2gcx-p88w)
- <https://nvd.nist.gov/vuln/detail/CVE-2022-20616>
- <https://github.com/jenkinsci/credentials-binding-plugin/commit/2dd5eda721e52d9a5bf6748405adf965ba517d8a>
- <https://github.com/CVEProject/cvelist/blob/2d78eb36f4d084db7fb35f1535d8d84fdcb7d859/2022/20xxx/CVE-2022-20616.json>
- <https://github.com/jenkinsci/credentials-binding-plugin>
- <https://www.jenkins.io/security/advisory/2022-01-12/#SECURITY-2342>
- <http://www.openwall.com/lists/oss-security/2022/01/12/6>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-gqm2-2gcx-p88w>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-gqm2-2gcx-p88w/>. Everything for agents: <https://agentprime.io/llms.txt>.
