CVE-2026-57298
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 Contrast Continuous Application Security Plugin 3.11 and earlier allows attackers to have Jenkins connect to an attacker-specified URL using an attacker-specified username, API key, and service key.
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 confidenceCSRF vulnerability in Jenkins Contrast Continuous Application Security Plugin version 3.11 and earlier allows attackers to trick Jenkins into making outbound connections to attacker-controlled URLs using attacker-supplied credentials (username, API key, and service key). This enables credential theft, data exfiltration, or further compromise of the Jenkins infrastructure.
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 Contrast plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, search for 'Contrast Continuous Application Security' or 'Contrast' in the plugin listAffected if the plugin appears in the installed plugins list
-
Check installed plugin versionIn the installed plugins list, locate the Contrast plugin and note the version number displayed in the Version columnAffected if the version is 3.11 or earlier (e.g., 3.11, 3.10, 3.9, etc.)
-
Determine if plugin is configured with credentialsNavigate to Jenkins > Manage Jenkins > Configure System > Contrast Continuous Application Security section, or check Jenkins credentials configured for the Contrast pluginAffected if the plugin has credentials (username, API key, service key) configured or stored in Jenkins
-
Check Jenkins global CSRF protectionGo to Jenkins > Manage Jenkins > Global Security > CSRF Protection setting. Verify whether the default Jenkins Crumb or compatible crumb issuer is enabledAffected if CSRF protection is disabled or uses an insecure configuration
You are affected if the Contrast Continuous Application Security Plugin is installed at version 3.11 or earlier and has credentials configured; ensure CSRF protection is enabled to partially mitigate the risk.
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 Contrast Continuous Application Security Plugin to a version newer than 3.11 which includes proper CSRF protection. Ensure Jenkins global CSRF protection is enabled in Jenkins global security settings.
- 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-57298 — 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-57298 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