Script security bypass vulnerability in Jenkins Shared Library Version Override Plugin

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.8 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS

• CVE-2024-52554: 0.52% estimated exploitation activity in the next 30 days; percentile 43.92 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Jenkins Shared Library Version Override Plugin 17.v786074c9fce7 and earlier declares folder-scoped library overrides as trusted, so that they're not executed in the Script Security sandbox, allowing attackers with Item/Configure permission on a folder to configure a folder-scoped library override that runs without sandbox protection. This allows attackers with Item/Configure permission on a folder to configure a folder-scoped library override that runs without sandbox protection. Shared Library Version Override Plugin 19.v3ac975738d4a declares folder-scoped library overrides as untrusted, so that they’re executed in the Script Security sandbox.

Published by the source

13 Nov 2024, 21:30 UTC

Last modified by the source

14 Nov 2024, 15:42 UTC

Source last checked

26 Oct 2026, 16:31 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-7845-crfj-phc4

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-52554

Advisory: Script security bypass vulnerability in Jenkins Shared Library Version Override Plugin
IDs: CVE-2024-52554, GHSA-7845-crfj-phc4
Record: https://patchnext.com/advisories/cve-2024-52554 (revision 1, source checked 26 Oct 2026, 16:31 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: io.jenkins.plugins:shared-library-version-override 19.v3a. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven io.jenkins.plugins:shared-library-version-override: affected < 19.v3a; fixed in 19.v3a

## Suggested inspection (read-only)
- Maven io.jenkins.plugins:shared-library-version-override: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on io.jenkins.plugins:shared-library-version-override.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-7845-crfj-phc4 (GitHub-reviewed advisory GHSA-7845-crfj-phc4 lists affected ranges: Maven io.jenkins.plugins:shared-library-version-override >=0 <19.v3a)

Commands are suggestions: review each one before running it.