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

CVE-2020-2166 — pipeline-aws

HIGH

CVE-2020-2166 is a high-severity (CVSS 8.8) Improper Input Validation vulnerability in de.taimos:pipeline-aws. A fix is available for de.taimos:pipeline-aws — see the affected versions and patch details below.

RCE vulnerability in Jenkins Pipeline: AWS Steps Plugin

Also known asGHSA-w598-25hm-jqx3
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 1, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.0%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs81th percentile — riskier than 81% of all scored CVEsHighest risk
0.15%0.95%1.74%2.53%0.7%2.0%May 26Aug 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
☕de.taimos:pipeline-aws

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

Pipeline: AWS Steps Plugin 1.40 and earlier does not configure its YAML parser to prevent the instantiation of arbitrary types. This results in a remote code execution (RCE) vulnerability exploitable by users able to provide YAML input files to Pipeline: AWS Steps Plugin’s build steps.

Pipeline: AWS Steps Plugin 1.41 configures its YAML parser to only instantiate safe types.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavende.taimos:pipeline-awsall versions1.41de.taimos:pipeline-aws:1.41

Affected Products

1 product · 1 configurations
Application
pipeline\jenkins
≤ 1.40
1 version
_aws_steps

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update de.taimos:pipeline-aws to 1.41 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-2166 is resolved across your whole dependency graph.

  3. 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

Pipeline: AWS Steps Plugin 1.40 and earlier does not configure its YAML parser to prevent the instantiation of arbitrary types. This results in a remote code execution (RCE) vulnerability exploitable by users able to provide YAML input files to Pipeline: AWS Steps Plugin’s build steps. Pipeline: AWS Steps Plugin 1.41 configures its YAML parser to only instantiate safe types.
O3 Security · Impact-Aware SCA

Is CVE-2020-2166 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2020-2166: pipeline-aws RCE — Fixed in 1.41