Jenkins Gitee Plugin has a cross-site request forgery vulnerability

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

EPSS

• CVE-2026-57292: 0.14% estimated exploitation activity in the next 30 days; percentile 3.06 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Jenkins Gitee Plugin 1288.v18bdebc9069b and earlier does not perform permission checks in several HTTP endpoints implementing form validation for its global configuration. This allows attackers with Overall/Read permission to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins. Additionally, these HTTP endpoints do not require POST requests, resulting in a cross-site request forgery (CSRF) vulnerability. Gitee Plugin 1292.v2559f2f3f2c0 requires the appropriate permissions in the affected HTTP endpoints, and requires POST requests.

Published by the source

24 Jun 2026, 15:31 UTC

Last modified by the source

25 Sep 2026, 19:04 UTC

Source last checked

26 Oct 2026, 16:56 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-w794-rwp2-jc9m

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-57292

Advisory: Jenkins Gitee Plugin has a cross-site request forgery vulnerability
IDs: CVE-2026-57292, GHSA-w794-rwp2-jc9m
Record: https://patchnext.com/advisories/cve-2026-57292 (revision 1, source checked 26 Oct 2026, 16:56 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.jenkins-ci.plugins:gitee 1292.v2559f2f3f2c0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.jenkins-ci.plugins:gitee: affected < 1292.v2559f2f3f2c0; fixed in 1292.v2559f2f3f2c0

## Suggested inspection (read-only)
- Maven org.jenkins-ci.plugins:gitee: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.jenkins-ci.plugins:gitee.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-w794-rwp2-jc9m (GitHub-reviewed advisory GHSA-w794-rwp2-jc9m lists affected ranges: Maven org.jenkins-ci.plugins:gitee >=0 <1292.v2559f2f3f2c0)

Commands are suggestions: review each one before running it.