# CVE-2018-1000112: mercurial — Fixed in 2.3

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

# CVE-2018-1000112 — mercurial

MEDIUM [Fix: jenkinsci/mercurial-plugin@54b4f82](https://github.com/jenkinsci/mercurial-plugin/commit/54b4f82e80c89d51b12bc64258f6b59e98b0c16a)

CVE-2018-1000112 is a medium-severity (CVSS 5.3) CWE-863 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.

Incorrect Authorization in Jenkins Mercurial Plugin

Also known as[GHSA-f9cx-789c-w2mr](/vulnerability/GHSA-f9cx-789c-w2mr)

Published

Mar 13, 2018

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

## EPSS Exploitation Probability

[via FIRST.org ↗](https://www.first.org/epss/)

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs62th percentile — riskier than 62% of all scored CVEsHighest risk

0.00%0.49%0.97%1.46%0.1%0.1%1.0%1.0%1.0%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from [FIRST.org EPSS](https://www.first.org/epss/).

## How urgent is this, really

## Where this sits among everything scored

## Real-World Exposure

1 pkg affected

☕`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

An improper authorization vulnerability exists in Jenkins Mercurial Plugin version 2.2 and earlier in MercurialStatus.java that allows an attacker with network access to obtain a list of nodes and users.

## Affected Packages

1 total 1 fixed

Ecosystem

Package

Vulnerable range

Fix

☕Maven

`org.jenkins-ci.plugins:mercurial` 

all versions

2.3`org.jenkins-ci.plugins:mercurial:2.3`

## Affected Products

1 product · 1 configurations

Application

`mercurial`jenkins

≤ 2.2

range

## Detection & mitigation playbook

Open-source dependency

1.  ### 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.
    
2.  ### Fix
    
    Update org.jenkins-ci.plugins:mercurial to 2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-1000112 is resolved across your whole dependency graph.
    
3.  ### Workarounds
    
    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
    

## Frequently Asked Questions

An improper authorization vulnerability exists in Jenkins Mercurial Plugin version 2.2 and earlier in MercurialStatus.java that allows an attacker with network access to obtain a list of nodes and users.

O3 Security · Impact-Aware SCA

### Is CVE-2018-1000112 in your dependencies?

Find it across Maven, including transitive dependencies.

[Scan my dependencies](/book-demo) [How O3 SCA works](/impact-aware-sca)