CVE-2026-57291
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 · uneditedMissing 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.
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 · high confidenceThe Jenkins Gitee Plugin lacks permission checks, allowing any user with Overall/Read permission to trigger the Jenkins server to connect to attacker-specified URLs using credentials IDs obtained through another method. This creates an SSRF-like vulnerability where authenticated low-privilege users can make the Jenkins server make arbitrary HTTP requests to internal or 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 installedAccess Jenkins script console at /script or check the plugin directory ($JENKINS_HOME/plugins) for gitee* files. In script console run: Jenkins.instance.pluginManager.plugins.find{it.shortName=='gitee'}Affected if The Gitee plugin is present in the Jenkins instance
-
Check installed Gitee Plugin versionIn Jenkins script console run: Jenkins.instance.pluginManager.plugins.find{it.shortName=='gitee'}?.version. Compare this version number against 1288.v18b_deb_c9069b_Affected if Version is lower than 1288.v18b_deb_c9069b_ (e.g., 1285.vf5b_3d5a_3a_b_2, 1283.v5b_3d5a_3a_b_1, etc.)
-
Verify Gitee credentials are configuredNavigate to Manage Jenkins > Manage Credentials, or check the Gitee plugin configuration at /configure or under the Gitee section. Look for any stored credentials associated with Gitee API access.Affected if Any Gitee credentials (username/password, token, or SSH key) are stored in Jenkins and associated with the Gitee plugin
-
Confirm user access levelCheck if any user account with Overall/Read permission (the default permission for authenticated users) exists in Jenkins. This can be verified in Manage Jenkins > Manage Users or via LDAP/AD integration settings.Affected if Any user account with Overall/Read permission exists in the Jenkins instance (this is the default state)
-
Check Gitee API endpoint configurationReview the Gitee plugin configuration for any configured API URLs or webhook endpoints. In script console run: Jenkins.instance.getDescriptorByName('com.gitee.jenkins.GiteeLink').apiUrlAffected if A Gitee server URL is configured in the plugin settings, indicating the plugin is actively used
The environment is affected if the Gitee plugin is installed with a version lower than 1288.v18b_deb_c9069b_ AND has Gitee credentials or API endpoints configured, allowing any authenticated user with basic read access to potentially trigger arbitrary HTTP requests.
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 dataUpgrade the Jenkins Gitee Plugin to version 1288.v18b_deb_c9069b_ or later, which includes proper permission checks. Review and rotate any credentials that may have been exposed.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.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,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57291 — 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-57291 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