How severe is CVE-2020-2136?

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

Which packages are affected by CVE-2020-2136?

CVE-2020-2136 affects the following packages: org.jenkins-ci.plugins:git (Maven). Ecosystems affected: Maven.

How do I fix CVE-2020-2136?

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

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

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

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

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

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

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

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

CVE-2020-2136 is classified as Cross-site Scripting (XSS) (CWE-79). 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-2136 published, and has it been updated?

CVE-2020-2136 was published on March 9, 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-2136 — git

MEDIUMFix: jenkinsci/git-plugin@f581998

CVE-2020-2136 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in org.jenkins-ci.plugins:git. A fix is available for org.jenkins-ci.plugins:git — see the affected versions and patch details below.

Improper Neutralization of Input During Web Page Generation in Jenkins Git Plugin

Also known asGHSA-6c7r-6p5m-cp82

Published

Mar 9, 2020

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs58th percentile — riskier than 58% 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:git

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 Git Plugin 4.2.0 and earlier does not escape the error message for the repository URL for Microsoft TFS field form validation, resulting in a stored cross-site scripting vulnerability.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins:git`	all versions	4.2.1`org.jenkins-ci.plugins:git:4.2.1`

Affected Products

1 product · 1 configurations

Application

gitjenkins

≤ 4.2.0

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:git, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:git to 4.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-2136 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
Red Hat OpenShift Container Platform 3.11	`jenkins-2-plugins-0:3.11.1591354111-1.el7`	RHSA-2020:2478
Red Hat OpenShift Container Platform 4.3	`jenkins-2-plugins-0:4.3.1597915133-1.el7`	RHSA-2020:3616
Red Hat OpenShift Container Platform 4.4	`jenkins-2-plugins-0:4.4.1592817009-1.el7`	RHSA-2020:2737
Red Hat OpenShift Container Platform 4.5	`openshift4/ose-aws-machine-controllers:v4.5.0-202007012112.p0`	RHBA-2020:2409

Frequently Asked Questions

Jenkins Git Plugin 4.2.0 and earlier does not escape the error message for the repository URL for Microsoft TFS field form validation, resulting in a stored cross-site scripting vulnerability.

O3 Security · Impact-Aware SCA

Is CVE-2020-2136 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.4/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

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

CWE Classification

CWE-79Cross-site Scripting (XSS)

Weaponization

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

Timeline

Disclosed

Mar 9, 2020

Last updated

Oct 24, 2026

Identifiers

CVE-2020-2136

GHSA-6c7r-6p5m-cp82

References

Advisoryopenwall.com Advisoryjenkins.io · 2020 03 09 Advisorynvd.nist.gov · CVE 2020 2136 Webgithub.com · f581998be38cfed8e080c672c4b7caa8b4a45979

Related vulnerabilities

This CVE is medium severity; 7 of 8 other CVEs affecting git are rated as high or higher (top: high).

CVE-2022-38663CVE-2022-36884CVE-2022-36882CVE-2022-36883CVE-2021-21684CVE-2022-30947CVE-2022-30949CVE-2017-1000092

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026