CVE-2026-57294
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 missing permission check in Jenkins EC2 Fleet Plugin 4.2.3.539.v8fedff2a_81c3 and earlier allows attackers with Overall/Read permission 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 confidenceThe EC2 Fleet Plugin lacks permission checks on a feature that allows connection to user-specified URLs using user-specified credential IDs. Attackers with only Overall/Read permission (the lowest privilege) can exploit this to direct Jenkins to connect to malicious URLs and exfiltrate AWS credentials stored in the system.
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<= 4.2.3.539.v8fedff2a_81c3CVSS 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 EC2 Fleet Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'EC2 Fleet' or use the Jenkins script console: Jenkins.instance.pluginManager.plugins.each { if (it.shortName == 'aws-k8s') { println "Found: ${it.displayName} version ${it.version}" } }Affected if The plugin named 'EC2 Fleet' or 'aws-k8s' appears in the installed plugins list
-
Check installed EC2 Fleet Plugin versionIn Manage Jenkins > Manage Plugins > Installed tab, find EC2 Fleet and note the version column, or use the script console: println Jenkins.instance.pluginManager.plugins.find { it.shortName == 'aws-k8s' }?.versionAffected if The version number is 4.2.3.539.v8fedff2a_81c3 or lower
-
Confirm users with Overall/Read permission existNavigate to Manage Jenkins > Manage Users and review user accounts, then check authorization matrix at Manage Jenkins > Configure Global Security to see which users/groups have Overall/Read permissionAffected if Any user account (even a low-privilege one) is granted Overall/Read permission in the authorization settings
-
Identify if EC2 Fleet credentials configuration is accessibleNavigate to Manage Jenkins > Configure Clouds > EC2 Fleet or EC2 Fleet Plus section to see if credential configurations allowing user-specified credential IDs existAffected if EC2 Fleet credential configurations are present and configurable by users with Overall/Read access
A user is affected if the EC2 Fleet Plugin version is 4.2.3.539.v8fedff2a_81c3 or lower AND any untrusted user account has Overall/Read permission in the authorization matrix.
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 EC2 Fleet Plugin to a version beyond 4.2.3.539.v8fedff2a_81c3 which includes the permission check, or restrict Overall/Read permission to trusted users only until patching is feasible.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57294 — 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-57294 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