dbcve.org
Ec2 FleetApplication · Jenkins

CVE-2026-57295

MEDIUM · 5.4 CVSS v3.1 Published 2026-06-24
Fix available
A fix is available. Upgrade to after 4.2.3.539.v8fedff2a_81c3 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click 8 weeks old

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 · unedited
A cross-site request forgery (CSRF) vulnerability in Jenkins EC2 Fleet Plugin 4.2.3.539.v8fedff2a_81c3 and earlier allows attackers to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing AWS credentials stored in Jenkins.

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 confidence

A CSRF vulnerability in Jenkins EC2 Fleet Plugin versions 4.2.3.539.v8fedff2a_81c3 and earlier allows authenticated users to be tricked into connecting to attacker-specified URLs using attacker-specified credentials IDs, potentially exfiltrating AWS credentials stored in Jenkins.

MitigationUpdate EC2 Fleet Plugin to the latest version that includes CSRF protection fixes, or upgrade Jenkins and the plugin to recent versions with proper CSRF token validation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ec2 FleetApplication
Affected:<= 4.2.3.539.v8fedff2a_81c3

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify EC2 Fleet Plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab. Search for 'EC2 Fleet' in the filter box.
    Affected if The EC2 Fleet Plugin appears in the installed plugins list
  2. Check the installed plugin version
    In the Installed plugins tab, locate the EC2 Fleet Plugin and note the version number in the Version column.
    Affected if Version is 4.2.3.539.v8fedff2a_81c3 or earlier
  3. Confirm AWS credentials exist in Jenkins
    Navigate to Manage Jenkins > Manage Credentials. Review any credentials entries that could be AWS-related (check ID, description, or provider type).
    Affected if AWS credentials are stored in Jenkins and the EC2 Fleet Plugin version is vulnerable

User is affected if EC2 Fleet Plugin version is 4.2.3.539.v8fedff2a_81c3 or earlier and AWS credentials are configured in Jenkins.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 4.2.3.539.v8fedff2a_81c3
Interim mitigation

Update EC2 Fleet Plugin to the latest version that includes CSRF protection fixes, or upgrade Jenkins and the plugin to recent versions with proper CSRF token validation.

Fix this in Ec2 Fleet Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-57295 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-57295 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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