AWS credential capture via forged validation requests
Published Jun 24, 2026 · Updated Jun 24, 2026
CSRF in Jenkins EC2 Fleet Plugin 4.2.3.539.v8fedff2a_81c3 and earlier allows remote authenticated users to capture AWS credentials. Cloud-configuration validation endpoints accept non-POST requests and connect to attacker-selected URLs using supplied Jenkins credential IDs. Exploitation requires a credential ID obtained separately and an authenticated Jenkins context with Overall/Read access; the outbound connection exposes the stored AWS credential.
Summary
What happened
CSRF in Jenkins EC2 Fleet Plugin 4.2.3.539.v8fedff2a_81c3 and earlier allows remote authenticated users to capture AWS credentials. Cloud-configuration validation endpoints accept non-POST requests and connect to attacker-selected URLs using supplied Jenkins credential IDs. Exploitation requires a credential ID obtained separately and an authenticated Jenkins context with Overall/Read access; the outbound connection exposes the stored AWS credential.
The record
- CVE
- CVE-2026-57295
- Published
- Jun 24, 2026
- Updated
- Jun 24, 2026
- Vendor
- Jenkins Project
- Product
- EC2 Fleet Plugin
- Classifications
- CWE-352, T1555
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 24, 2026CVE publishedPublication date reported by the CVE source.
- Jun 24, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=4.2.3.539.v8fedff2a_81c3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo