Categories
CVE-2026-57290 medium CVSS 4.3

Cross-Site Request Forgery (CSRF) in org.jenkins-ci.plugins:PrioritySorter (CVE-2026-57290)

Summary

Vulnerability in org.jenkins-ci.plugins:PrioritySorter (CVE-2026-57290). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 936.937.v5581d0b or later.

Original description

The description as published by the source.

Jenkins Priority Sorter Plugin 936.v2c01c6b_84449 and earlier does not require POST requests in an HTTP endpoint that saves the global job priority configuration.

This allows attackers to overwrite the global job priority configuration.

Priority Sorter Plugin 936.937.v5581d0b_2ccb_a_ requires POST requests for the affected HTTP endpoint.

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-57290 has been found in org.jenkins-ci.plugins:PrioritySorter.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade org.jenkins-ci.plugins:PrioritySorter to 936.937.v5581d0b or later.
If unsure, ask your IT team or search "org.jenkins-ci.plugins:PrioritySorter CVE-2026-57290" on the vendor's site.

CVE-2026-57290 (org.jenkins-ci.plugins:PrioritySorter) — CWE-352 / CVSS v3 4.3
Attack vector: remote (network-reachable) / unauthenticated
Patched: 936.937.v5581d0b — 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

CSRF (CWE-352) exists in org.jenkins-ci.plugins:PrioritySorter.

📍 Affected scope

Check the vendor advisory for the affected versions of org.jenkins-ci.plugins:PrioritySorter.

🔥 Severity

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

🔧 How to fix

Update to 936.937.v5581d0b.

🛡️ 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・依存マニフェストで org.jenkins-ci.plugins:PrioritySorter を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch
    Upgrade org.jenkins-ci.plugins:PrioritySorter to 936.937.v5581d0b

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

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

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

Affected packages

maven org.jenkins-ci.plugins:PrioritySorter
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"936.937.v5581d0b"}]}]

References

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