What is CVE-2026-57290?

CVE-2026-57290 is a medium-severity cross-site request forgery (CSRF) vulnerability in org.jenkins-ci.plugins:PrioritySorter (maven), affecting versions < 936.937.v5581d0b. It is fixed in 936.937.v5581d0b. A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones.

How severe is CVE-2026-57290?

CVE-2026-57290 has a CVSS score of 4.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of org.jenkins-ci.plugins:PrioritySorter are affected by CVE-2026-57290?

org.jenkins-ci.plugins:PrioritySorter (maven) versions < 936.937.v5581d0b is affected.

Is there a fix for CVE-2026-57290?

Yes. CVE-2026-57290 is fixed in 936.937.v5581d0b. Upgrade to this version or later.

Is CVE-2026-57290 exploitable, and should I be worried?

Whether CVE-2026-57290 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-57290 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2026-57290

Q: How severe is CVE-2026-57290?

CVE-2026-57290 has a CVSS score of 4.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of org.jenkins-ci.plugins:PrioritySorter are affected by CVE-2026-57290?

org.jenkins-ci.plugins:PrioritySorter (maven) versions < 936.937.v5581d0b is affected.

Q: Is there a fix for CVE-2026-57290?

Yes. CVE-2026-57290 is fixed in 936.937.v5581d0b. Upgrade to this version or later.

Q: Is CVE-2026-57290 exploitable, and should I be worried?

Whether CVE-2026-57290 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-57290 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-57290?

Upgrade org.jenkins-ci.plugins:PrioritySorter to 936.937.v5581d0b or later.

Summary

Jenkins Priority Sorter Plugin has a CSRF vulnerability

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.

Impact

A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones. Typical impact: state-changing actions performed as the victim without their consent.

CVE-2026-57290 has a CVSS score of 4.3 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (936.937.v5581d0b); upgrading removes the vulnerable code path.

Affected versions

org.jenkins-ci.plugins:PrioritySorter (< 936.937.v5581d0b)

Security releases

org.jenkins-ci.plugins:PrioritySorter → 936.937.v5581d0b (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade org.jenkins-ci.plugins:PrioritySorter to 936.937.v5581d0b or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2026-57290? CVE-2026-57290 is a medium-severity cross-site request forgery (CSRF) vulnerability in org.jenkins-ci.plugins:PrioritySorter (maven), affecting versions < 936.937.v5581d0b. It is fixed in 936.937.v5581d0b. A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones.
How severe is CVE-2026-57290? CVE-2026-57290 has a CVSS score of 4.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of org.jenkins-ci.plugins:PrioritySorter are affected by CVE-2026-57290? org.jenkins-ci.plugins:PrioritySorter (maven) versions < 936.937.v5581d0b is affected.
Is there a fix for CVE-2026-57290? Yes. CVE-2026-57290 is fixed in 936.937.v5581d0b. Upgrade to this version or later.
Is CVE-2026-57290 exploitable, and should I be worried? Whether CVE-2026-57290 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-57290 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-57290? Upgrade org.jenkins-ci.plugins:PrioritySorter to 936.937.v5581d0b or later.