How severe is CVE-2020-2261?

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

Which packages are affected by CVE-2020-2261?

CVE-2020-2261 affects the following packages: io.jenkins.plugins:perfecto (Maven). Ecosystems affected: Maven.

How do I fix CVE-2020-2261?

Update io.jenkins.plugins:perfecto to 1.18 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-2261 is resolved across your whole dependency graph.

How do I detect CVE-2020-2261 in my Maven dependencies?

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

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

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is CVE-2020-2261 actively exploited in the wild?

No public exploit code has been indexed for CVE-2020-2261 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-2020-2261?

CVE-2020-2261 has an EPSS (Exploit Prediction Scoring System) score of 1.4%, placing it in the 72th 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.

What type of vulnerability is CVE-2020-2261?

CVE-2020-2261 is classified as OS Command Injection (CWE-78). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2020-2261 published, and has it been updated?

CVE-2020-2261 was published on September 16, 2020 and was last updated on October 24, 2026. 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-2020-2261 — perfecto

HIGH

CVE-2020-2261 is a high-severity (CVSS 8.8) OS Command Injection vulnerability in io.jenkins.plugins:perfecto. A fix is available for io.jenkins.plugins:perfecto — see the affected versions and patch details below.

OS command execution vulnerability in Perfecto Plugin

Also known asGHSA-jq84-6fmm-6qv6

Published

Sep 16, 2020

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs72th percentile — riskier than 72% 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

☕io.jenkins.plugins:perfecto

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

Perfecto Plugin allows specifying Perfecto Connect Path and Perfecto Connect File Name in job configurations.

This command is executed on the Jenkins controller in Perfecto Plugin 1.17 and earlier, allowing attackers with Job/Configure permission to run arbitrary commands on the Jenkins controller.

Perfecto Plugin 1.18 executes the specified commands on the agent the build is running on.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`io.jenkins.plugins:perfecto`	all versions	1.18`io.jenkins.plugins:perfecto:1.18`

Affected Products

1 product · 1 configurations

Application

perfectojenkins

≤ 1.17

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.jenkins.plugins:perfecto, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.jenkins.plugins:perfecto to 1.18 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-2261 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

Perfecto Plugin allows specifying Perfecto Connect Path and Perfecto Connect File Name in job configurations. This command is executed on the Jenkins controller in Perfecto Plugin 1.17 and earlier, allowing attackers with Job/Configure permission to run arbitrary commands on the Jenkins controller. Perfecto Plugin 1.18 executes the specified commands on the agent the build is running on.

O3 Security · Impact-Aware SCA

Is CVE-2020-2261 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

8.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

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

CWE Classification

CWE-78OS Command Injection

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Sep 16, 2020

Last updated

Oct 24, 2026

Identifiers

CVE-2020-2261

GHSA-jq84-6fmm-6qv6

References

Advisoryopenwall.com Advisoryjenkins.io · 2020 09 16 Advisorynvd.nist.gov · CVE 2020 2261 Packagegithub.com · perfecto plugin

Related vulnerabilities

Also affects perfecto

This CVE is high severity — higher than any of the other 1 CVE affecting perfecto (highest there: moderate).

CVE-2020-2260

Same weakness: CWE-78

This CVE is high severity, in line with the other 7 CVEs with CWE-78.

CVE-2026-119282CVE-2026-61438CVE-2026-116576GHSA-f9j4-qggq-h239CVE-2026-116676CVE-2026-113723CVE-2026-115586Browse all CWE-78

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2020-2261 — perfecto

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2020-2261 in your dependencies?