NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

CVE-2024-52551 — pipeline-model-parent

HIGH

CVE-2024-52551 is a high-severity (CVSS 8) Incorrect Default Permissions vulnerability in org.jenkinsci.plugins:pipeline-model-parent. A fix is available for org.jenkinsci.plugins:pipeline-model-parent — see the affected versions and patch details below.

Restarting a run with revoked script approval allowed by Jenkins Pipeline: Declarative Plugin

Also known asGHSA-p2qq-c693-q53w
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-52551.

EPSS Exploitation Probability

via FIRST.org ↗
0.6%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs48th percentile — riskier than 48% of all scored CVEsHighest risk
0.05%0.40%0.74%1.09%0.5%0.6%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
☕org.jenkinsci.plugins:pipeline-model-parent

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Jenkins Pipeline: Declarative Plugin 2.2214.vb_b_34b_2ea_9b_83 and earlier does not check whether the main (Jenkinsfile) script used to restart a build from a specific stage is approved, allowing attackers with Item/Build permission to restart a previous build whose (Jenkinsfile) script is no longer approved. This allows attackers with Item/Build permission to restart a previous build whose (Jenkinsfile) script is no longer approved. Pipeline: Declarative Plugin 2.2218.v56d0cda_37c72 refuses to restart a build whose main (Jenkinsfile) script is unapproved.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.jenkinsci.plugins:pipeline-model-parentall versions2.2218.v56d0cdaorg.jenkinsci.plugins:pipeline-model-parent:2.2218.v56d0cda

Affected Products

1 product · 1 configurations
Application
pipeline\jenkins
≤ 2.2214.vb_b_34b_2ea_9b_83
1 version
_declarative

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkinsci.plugins:pipeline-model-parent, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.jenkinsci.plugins:pipeline-model-parent to 2.2218.v56d0cda or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-52551 is resolved across your whole dependency graph.

  3. Workarounds

    Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This vulnerability is rated as Important due to the risk it poses by allowing attackers with Item/Build permissions to restart a previous build using an unapproved Jenkinsfile script, this could result in unauthorized execution of scripts, compromising the integrity of the build process.

Workaround published by Red Hat
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Source: Red Hat security advisory for CVE-2024-52551 (CC BY 4.0)
ProductFixed inAdvisory
OCP-Tools-4.12-RHEL-8jenkins-0:2.479.3.1740464431-3.el8RHSA-2025:2223
OCP-Tools-4.13-RHEL-8jenkins-0:2.479.3.1740464433-3.el8RHSA-2025:2222
OCP-Tools-4.14-RHEL-8jenkins-0:2.479.3.1740109575-3.el8RHSA-2025:2221
OCP-Tools-4.15-RHEL-8jenkins-0:2.479.3.1740051993-3.el8RHSA-2025:2220
OCP-Tools-4.16-RHEL-9jenkins-0:2.479.3.1739896390-3.el9RHSA-2025:2219
OCP-Tools-4.17-RHEL-9jenkins-0:2.479.3.1739859586-3.el9RHSA-2025:2218

Frequently Asked Questions

Jenkins Pipeline: Declarative Plugin 2.2214.vb_b_34b_2ea_9b_83 and earlier does not check whether the main (Jenkinsfile) script used to restart a build from a specific stage is approved, allowing attackers with Item/Build permission to restart a previous build whose (Jenkinsfile) script is no longer approved. This allows attackers with Item/Build permission to restart a previous build whose (Jenkinsfile) script is no longer approved. Pipeline: Declarative Plugin 2.2218.v56d0cda_37c72 refuses to restart a build whose main (Jenkinsfile) script is unapproved.
O3 Security · Impact-Aware SCA

Is CVE-2024-52551 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2024-52551: pipeline-model-parent — Fix Available