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

CVE-2022-36890 — deployer-framework

MEDIUM

CVE-2022-36890 is a medium-severity (CVSS 4.3) Path Traversal vulnerability in org.jenkins-ci.plugins:deployer-framework. A fix is available for org.jenkins-ci.plugins:deployer-framework — see the affected versions and patch details below.

Jenkins Deployer Framework Plugin vulnerable to Path Traversal

Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs68th percentile — riskier than 68% of all scored CVEsHighest risk
0.16%0.67%1.18%1.69%0.7%1.2%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.jenkins-ci.plugins:deployer-framework

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 Deployer Framework Plugin 85.v1d1888e8c021 and earlier does not restrict the name of files in methods implementing form validation.

This allows attackers with Item/Read permission to check for the existence of an attacker-specified file path on the Jenkins controller file system.

Deployer Framework Plugin 86.v7b_a_4a_55b_f3ec ensures that only files contained inside the expected directory can be accessed.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.jenkins-ci.plugins:deployer-frameworkall versions86.v7b_a_4a_55b_f3ecorg.jenkins-ci.plugins:deployer-framework:86.v7b_a_4a_55b_f3ec

Affected Products

1 product · 1 configurations
Application
deployer frameworkjenkins
≤ 85.v1d1888e8c021
range

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.jenkins-ci.plugins:deployer-framework, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.jenkins-ci.plugins:deployer-framework to 86.v7b_a_4a_55b_f3ec or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-36890 is resolved across your whole dependency graph.

  3. Workarounds

    Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

Jenkins Deployer Framework Plugin 85.v1d1888e8c021 and earlier does not restrict the name of files in methods implementing form validation. This allows attackers with Item/Read permission to check for the existence of an attacker-specified file path on the Jenkins controller file system. Deployer Framework Plugin 86.v7b_a_4a_55b_f3ec ensures that only files contained inside the expected directory can be accessed.
O3 Security · Impact-Aware SCA

Is CVE-2022-36890 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2022-36890: deployer-framework — Fix Available