Categories
CVE-2026-57294 medium CVSS 5.4

Vulnerability in com.amazon.jenkins.fleet:ec2-fleet (CVE-2026-57294)

Summary

Vulnerability in com.amazon.jenkins.fleet:ec2-fleet (CVE-2026-57294). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 4.2.3.540.va or later.

Original description

The description as published by the source.

Jenkins EC2 Fleet Plugin 4.2.3.539.v8fedff2a_81c3 and earlier does not perform permission checks in several HTTP endpoints used to validate cloud configurations.

This 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.

Additionally, these HTTP endpoints do not require POST requests, resulting in a cross-site request forgery (CSRF) vulnerability.

EC2 Fleet Plugin 4.2.3.540.va_6eedb_7b_c112 requires Overall/Administer permission and POST requests to perform these form validation actions.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-57294 has been found in com.amazon.jenkins.fleet:ec2-fleet.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: upgrade com.amazon.jenkins.fleet:ec2-fleet to 4.2.3.540.va or later.
If unsure, ask your IT team or search "com.amazon.jenkins.fleet:ec2-fleet CVE-2026-57294" on the vendor's site.

CVE-2026-57294 (com.amazon.jenkins.fleet:ec2-fleet) — CWE-862 / CVSS v3 5.4
Attack vector: remote (network-reachable) / no user interaction
Patched: 4.2.3.540.va — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-862) exists in com.amazon.jenkins.fleet:ec2-fleet.

📍 Affected scope

Check the vendor advisory for the affected versions of com.amazon.jenkins.fleet:ec2-fleet.

🔥 Severity

Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 4.2.3.540.va.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで com.amazon.jenkins.fleet:ec2-fleet を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch
    Upgrade com.amazon.jenkins.fleet:ec2-fleet to 4.2.3.540.va

    ステージング環境で 4.2.3.540.va に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven com.amazon.jenkins.fleet:ec2-fleet
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.2.3.540.va"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details