How severe is CVE-2020-2117?

CVE-2020-2117 has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2020-2117?

CVE-2020-2117 affects the following packages: org.jenkins-ci.plugins:pipeline-githubnotify-step (Maven). Ecosystems affected: Maven.

How do I fix CVE-2020-2117?

Update org.jenkins-ci.plugins:pipeline-githubnotify-step to 1.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-2117 is resolved across your whole dependency graph.

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

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

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

Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

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

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

CVE-2020-2117 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 53th 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-2117?

CVE-2020-2117 is classified as Incorrect Default Permissions (CWE-276). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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

CVE-2020-2117 was published on February 12, 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

MEDIUM severity

CVE-2020-2117 — pipeline-githubnotify-step

MEDIUM

CVE-2020-2117 is a medium-severity (CVSS 4.3) Incorrect Default Permissions vulnerability in org.jenkins-ci.plugins:pipeline-githubnotify-step. A fix is available for org.jenkins-ci.plugins:pipeline-githubnotify-step — see the affected versions and patch details below.

Missing permission checks in Pipeline GitHub Notify Step Plugin allows capturing credentials

Also known asGHSA-x7rc-5mjg-5pvr

Published

Feb 12, 2020

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs53th percentile — riskier than 53% 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:pipeline-githubnotify-step

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

A missing permission check in Jenkins Pipeline GitHub Notify Step Plugin 1.0.4 and earlier allows attackers with Overall/Read permission to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins:pipeline-githubnotify-step`	all versions	1.0.5`org.jenkins-ci.plugins:pipeline-githubnotify-step:1.0.5`

Affected Products

1 product · 1 configurations

Application

pipeline github notify stepjenkins

≤ 1.0.4

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:pipeline-githubnotify-step, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:pipeline-githubnotify-step to 1.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-2117 is resolved across your whole dependency graph.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2020-2117 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

4.3/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Raw vector

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

CWE Classification

CWE-276Incorrect Default Permissions

Weaponization

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

Timeline

Disclosed

Feb 12, 2020

Last updated

Oct 24, 2026

Identifiers

CVE-2020-2117

GHSA-x7rc-5mjg-5pvr

References

Advisoryopenwall.com Advisoryjenkins.io · 2020 02 12 Advisorynvd.nist.gov · CVE 2020 2117 Webjenkins.io · 2020 02 12 Packagegithub.com · pipeline githubnotify step plugin

Related vulnerabilities

Also affects pipeline-githubnotify-step

This CVE is medium severity; 1 of 1 other CVE affecting pipeline-githubnotify-step is rated as high or higher (top: high).

CVE-2020-2116

Same weakness: CWE-276

This CVE is medium severity; 7 of 7 other CVEs with CWE-276 are rated as high or higher (top: critical).

GHSA-763v-5pjm-fx36CVE-2026-77364CVE-2026-53657CVE-2026-52766CVE-2026-48790CVE-2026-48722CVE-2026-53856Browse all CWE-276

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2020-2117 — pipeline-githubnotify-step

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-2117 in your dependencies?