How severe is CVE-2022-36894?

CVE-2022-36894 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-36894?

CVE-2022-36894 affects the following packages: org.jenkins-ci.plugins:clif-performance-testing (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-36894?

Update org.jenkins-ci.plugins:clif-performance-testing to 71.v0741865e206f or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-36894 is resolved across your whole dependency graph.

How do I detect CVE-2022-36894 in my Maven dependencies?

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

How do I mitigate CVE-2022-36894 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2022-36894 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-36894 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2022-36894?

CVE-2022-36894 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 56th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2022-36894 published, and has it been updated?

CVE-2022-36894 was published on July 28, 2022 and was last updated on February 16, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2022-36894 — clif-performance-testing

HIGHFix: jenkinsci/clif-performance-testing-plugin@0741865

CVE-2022-36894 is a high-severity (CVSS 8.8) vulnerability in org.jenkins-ci.plugins:clif-performance-testing. A fix is available for org.jenkins-ci.plugins:clif-performance-testing — see the affected versions and patch details below.

Arbitrary file write vulnerability in Jenkins CLIF Performance Testing plugin

Published

Jul 28, 2022

Updated

Feb 16, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs56th percentile — riskier than 56% of all scored CVEsHighest risk

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:clif-performance-testing

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

An arbitrary file write vulnerability in Jenkins CLIF Performance Testing Plugin 64.vc0d66de1dfb_f and earlier allows attackers with Overall/Read permission to create or replace arbitrary files on the Jenkins controller file system with attacker-specified content.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins:clif-performance-testing`	all versions	71.v0741865e206f`org.jenkins-ci.plugins:clif-performance-testing:71.v0741865e206f`

Affected Products

1 product · 1 configurations

Application

clif performance testingjenkins

≤ 64.vc0d66de1dfb_f

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:clif-performance-testing, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:clif-performance-testing to 71.v0741865e206f or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-36894 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2022-36894 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works