# CVE-2026-57291: Jenkins Gitee Plugin missing permission checks

> Attackers with read access can bypass authorization to connect to arbitrary URLs using stolen credentials, requiring a plugin upgrade.

- **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:** Yes
- **Published:** 24 Jun 2026
- **Updated:** 24 Jun 2026
- **Also known as:** GHSA-wjmq-rpqq-w4h9

## What is CVE-2026-57291?

CVE-2026-57291 is a medium-severity missing authorization vulnerability in Jenkins Gitee Plugin, published on 24 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Missing permission checks in Jenkins Gitee Plugin 1288.v18b_deb_c9069b_ and earlier allow attackers with Overall/Read permission to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method.

Weakness: CWE-862 (Missing Authorization)

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

2 open source packages ship an affected version, including org.jenkins-ci.plugins:gitee.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:gitee` | Maven | All versions | 1292.v2559f2f3f2c0 |
| `org.jenkins-ci.plugins:gitee` | Maven | All versions | 1292.v2559f2f3f2c0 |

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

Upgrade org.jenkins-ci.plugins:gitee to 1292.v2559f2f3f2c0 or later.

## Is CVE-2026-57291 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-57291 is a medium-severity missing authorization vulnerability in Jenkins Gitee Plugin, published on 24 Jun 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-57291 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:gitee (Maven): affected all versions; fixed in 1292.v2559f2f3f2c0
- org.jenkins-ci.plugins:gitee (Maven): affected all versions; fixed in 1292.v2559f2f3f2c0

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-57291/ (Markdown: https://insights.sbomify.com/CVE-2026-57291/index.md)
```

## Sources

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

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