Jenkins Deployer Framework Plugin does not restrict application path of applications when configuring a deployment

Exploitation

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

CVSS

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

EPSS

• CVE-2022-36889: 1.74% estimated exploitation activity in the next 30 days; percentile 77.72 (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 Deployer Framework Plugin 85.v1d1888e8c021 and earlier does not restrict the application path of the applications when configuring a deployment, allowing attackers with Item/Configure permission to upload arbitrary files from the Jenkins controller file system to the selected service.

Published by the source

28 Jul 2022, 00:00 UTC

Last modified by the source

2 Feb 2023, 05:03 UTC

Source last checked

26 Oct 2026, 16:07 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-j5qq-6rpm-qjgh

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

# Patch Next advisory brief: CVE-2022-36889

Advisory: Jenkins Deployer Framework Plugin does not restrict application path of applications when configuring a deployment
IDs: CVE-2022-36889, GHSA-j5qq-6rpm-qjgh
Record: https://patchnext.com/advisories/cve-2022-36889 (revision 1, source checked 26 Oct 2026, 16:07 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.jenkins-ci.plugins:deployer-framework 86.v7b_a_4a_55b_f3ec. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.jenkins-ci.plugins:deployer-framework: affected <= 85.v1d1888e8c021; fixed in 86.v7b_a_4a_55b_f3ec

## Suggested inspection (read-only)
- Maven org.jenkins-ci.plugins:deployer-framework: 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 org.jenkins-ci.plugins:deployer-framework.
- 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-j5qq-6rpm-qjgh (GitHub-reviewed advisory GHSA-j5qq-6rpm-qjgh lists affected ranges: Maven org.jenkins-ci.plugins:deployer-framework >=0 <=85.v1d1888e8c021)

Commands are suggestions: review each one before running it.