# Jenkins Gitee Plugin missing permission checks

Advisory record · `GHSA-wjmq-rpqq-w4h9`

- **Identifiers:** `GHSA-wjmq-rpqq-w4h9` · `CVE-2026-57291`
- **State:** Confirmed
- **Severity:** CVSS 5.4 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-862](https://cwe.mitre.org/data/definitions/862.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 24 Jun 2026
- **Updated:** 25 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 24 Jun 2026, 15:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.jenkins-ci.plugins:gitee` (Maven): affected `<1292.v2559f2f3f2c0`; fixed in `1292.v2559f2f3f2c0`

## Machine-written summary

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

> Jenkins Gitee Plugin versions 1288.v18b_deb_c9069b\_ and earlier, and earlier than 1292.v2559f2f3f2c0, lack permission checks in several HTTP form validation endpoints for its global configuration. An attacker with Overall/Read permission could make Jenkins connect to an attacker-specified URL using credential IDs they obtained elsewhere, capturing stored credentials; the endpoints also accept non-POST requests, enabling cross-site request forgery. Upgrade to Jenkins Gitee Plugin 1292.v2559f2f3f2c0 or later, which adds the required permission checks and requires POST requests.

Written 2 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

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

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

## Timeline

- 31 Oct 2026, 14:16 UTC: First seen by agentprime
- 31 Oct 2026, 14:16 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-wjmq-rpqq-w4h9)

## Sources

- [GitHub Advisory Database: GHSA-wjmq-rpqq-w4h9](https://github.com/advisories/GHSA-wjmq-rpqq-w4h9)
- [OSV: GHSA-wjmq-rpqq-w4h9](https://osv.dev/vulnerability/GHSA-wjmq-rpqq-w4h9)
- <https://nvd.nist.gov/vuln/detail/CVE-2026-57291>
- <https://github.com/jenkinsci/gitee-plugin/pull/199>
- <https://github.com/jenkinsci/gitee-plugin/commit/2559f2f3f2c02659d9abe5ab3d66c13cef9278dc>
- <https://github.com/jenkinsci/gitee-plugin>
- <https://github.com/jenkinsci/gitee-plugin/releases/tag/1292.v2559f2f3f2c0>
- <https://www.jenkins.io/security/advisory/2026-06-24/#SECURITY-3762%20%281%29>

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-wjmq-rpqq-w4h9>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-wjmq-rpqq-w4h9/>. Everything for agents: <https://agentprime.io/llms.txt>.