How severe is GHSA-vrrc-3wwh-frgx?

GHSA-vrrc-3wwh-frgx 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 GHSA-vrrc-3wwh-frgx?

GHSA-vrrc-3wwh-frgx affects the following packages: org.jenkins-ci.plugins:mercurial (Maven), org.jenkins-ci.plugins:mercurial (Maven), org.jenkins-ci.plugins:mercurial (Maven), org.jenkins-ci.plugins:mercurial (Maven). Ecosystems affected: Maven.

How do I fix GHSA-vrrc-3wwh-frgx?

Update org.jenkins-ci.plugins:mercurial to 2.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vrrc-3wwh-frgx is resolved across your whole dependency graph.

How do I detect GHSA-vrrc-3wwh-frgx in my Maven dependencies?

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

How do I mitigate GHSA-vrrc-3wwh-frgx 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 GHSA-vrrc-3wwh-frgx actively exploited in the wild?

No public exploit code has been indexed for GHSA-vrrc-3wwh-frgx 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 GHSA-vrrc-3wwh-frgx?

GHSA-vrrc-3wwh-frgx has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 66th 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 GHSA-vrrc-3wwh-frgx published, and has it been updated?

GHSA-vrrc-3wwh-frgx was published on May 24, 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

MEDIUM severity

Missing Authorization in Jenkins Mercurial PluginGHSA-vrrc-3wwh-frgx

MEDIUMFix: jenkinsci/mercurial-plugin@edd59db

GHSA-vrrc-3wwh-frgx is a medium-severity (CVSS 4.3) vulnerability in org.jenkins-ci.plugins:mercurial. A fix is available for org.jenkins-ci.plugins:mercurial — see the affected versions and patch details below.

Also known asCVE-2020-2306

Published

May 24, 2022

Updated

Feb 16, 2024

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk0.00%

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

4 pkgs affected

☕org.jenkins-ci.plugins:mercurial☕org.jenkins-ci.plugins:mercurial☕org.jenkins-ci.plugins:mercurial☕org.jenkins-ci.plugins:mercurial

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

Mercurial Plugin prior to 2.12, 2.10.1, 2.9.1, and 2.8.1 does not perform a permission check in an HTTP endpoint.

This allows attackers with Overall/Read permission to obtain a list of names of configured Mercurial installations.

Mercurial Plugin 2.12, 2.10.1, 2.9.1, and 2.8.1 performs permission checks when listing configured Mercurial installations.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins:mercurial`	≥ 2.11&&< 2.12	2.12`org.jenkins-ci.plugins:mercurial:2.12`
☕Maven	`org.jenkins-ci.plugins:mercurial`	≥ 2.10&&< 2.10.1	2.10.1`org.jenkins-ci.plugins:mercurial:2.10.1`
☕Maven	`org.jenkins-ci.plugins:mercurial`	≥ 2.9&&< 2.9.1	2.9.1`org.jenkins-ci.plugins:mercurial:2.9.1`
☕Maven	`org.jenkins-ci.plugins:mercurial`	all versions	2.8.1`org.jenkins-ci.plugins:mercurial:2.8.1`

Affected Products

1 product · 1 configurations

Application

mercurialjenkins

≤ 2.11

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:mercurial, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:mercurial to 2.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vrrc-3wwh-frgx 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.

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.1612862361-1.el7`	RHSA-2021:0637
Red Hat OpenShift Container Platform 4.5	`jenkins-2-plugins-0:4.5.1610108899-1.el7`	RHSA-2021:0034
Red Hat OpenShift Container Platform 4.6	`jenkins-2-plugins-0:4.6.1608634578-1.el7`	RHSA-2021:0038

Frequently Asked Questions

Mercurial Plugin prior to 2.12, 2.10.1, 2.9.1, and 2.8.1 does not perform a permission check in an HTTP endpoint. This allows attackers with Overall/Read permission to obtain a list of names of configured Mercurial installations. Mercurial Plugin 2.12, 2.10.1, 2.9.1, and 2.8.1 performs permission checks when listing configured Mercurial installations.

O3 Security · Impact-Aware SCA

Is GHSA-vrrc-3wwh-frgx 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

Weaponization

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

Timeline

Disclosed

May 24, 2022

Last updated

Feb 16, 2024

Identifiers

GHSA-vrrc-3wwh-frgx

References

Advisorynvd.nist.gov · CVE 2020 2306 Webgithub.com · edd59db1eec7e3c8d467372cd8417ae65eeb29dd Webgithub.com · CVE 2020 2306.json Webjenkins.io · 2020 11 04

Related vulnerabilities

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

CVE-2022-43410CVE-2020-2306CVE-2020-2305CVE-2022-30948CVE-2022-30947CVE-2022-30949CVE-2018-1000112

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedFeb 16, 2024

Missing Authorization in Jenkins Mercurial PluginGHSA-vrrc-3wwh-frgx

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

Fixing This On Your OS

Frequently Asked Questions

Is GHSA-vrrc-3wwh-frgx in your dependencies?