CVE-2026-57292
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA cross-site request forgery (CSRF) vulnerability in Jenkins Gitee Plugin 1288.v18b_deb_c9069b_ and earlier allows attackers to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe Jenkins Gitee Plugin before version 1288.v18b_deb_c9069b_ contains a CSRF vulnerability that allows unauthenticated attackers to trick an authenticated Jenkins user into making the Jenkins server connect to an attacker-controlled URL using attacker-specified credential IDs. This enables the attacker to potentially exfiltrate sensitive credentials or cause the Jenkins server to interact with malicious external services.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Gitee plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or run: jenkins-cli.jar get-plugins (or check $JENKINS_HOME/plugins/ for gitee directory)Affected if The Gitee plugin is listed as installed in Jenkins
-
Check installed Gitee plugin versionIn Jenkins UI: Manage Plugins > Installed > Gitee Plugin > Version column. Or inspect $JENKINS_HOME/plugins/gitee/WEB-INF/manifest.mf for the Implementation-VersionAffected if Version is present but lower than 1288.v18b_deb_c9069b_ (e.g., 1285.vc3f9c5b_2b_9 or earlier)
-
Confirm plugin is enabled and activeIn Manage Plugins > Installed, verify Gitee is Enabled (checkbox checked) and not disabled or marked for disableAffected if Plugin shows as Enabled in the plugin manager UI
-
Check for configured Gitee credentialsNavigate to Jenkins > Manage Jenkins > Manage Credentials > look for any credentials with Gitee-related IDs or in Gitee-associated credential storesAffected if Any credentials (especially username/password, API tokens, or secret texts) are configured for Gitee integration
-
Verify Jenkins global CSRF protection statusNavigate to Manage Jenkins > Global Security > CSRF Protection section, or inspect $JENKINS_HOME/jenkins.model.Jenkins.xml for enableCsrfProtection settingAffected if CSRF protection is disabled or not explicitly enabled (the vulnerability requires an authenticated user session to be exploitable)
A user is affected if the Gitee plugin is installed with a version prior to 1288.v18b_deb_c9069b_, the plugin is enabled, and credentials are configured for Gitee integration, making it possible for an attacker to trick an authenticated user into exposing those credentials via CSRF.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the Jenkins Gitee Plugin to version 1288.v18b_deb_c9069b_ or later once a patched version is released, or disable the plugin if not required. Also ensure Jenkins has CSRF protection enabled globally.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57292 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-57292 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data