Skip to content
Fencer Intel
critical 9.1

CVE-2018-1000132 json

Mercurial Incorrect Access Control vulnerability

published 8y ago modified 4mo ago also GHSA-4mr4-7vjv-9hm6 , PYSEC-2018-87 , EUVD-2018-0094

cvss
9.1
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.7%
EPSS 2.7% chance of exploitation in 30 days, percentile 85%
public exploits
0
none known

Summary

Mercurial version 4.5 and earlier contains a Incorrect Access Control (CWE-285) vulnerability in Protocol server that can result in Unauthorized data access. This attack appear to be exploitable via network connectivity. This vulnerability appears to have been fixed in 4.5.1.

Patch / fix

  • pypi mercurial 4.5.1
  • mercurial mercurial 4.5.1
  • mercurial Debian 14, Debian 13, Debian 12 4.5.2-1

debian advisories DEBIAN-CVE-2018-1000132

  • mercurial Ubuntu 14.04 LTS 2.8.2-1ubuntu1.4
  • mercurial Ubuntu 16.04 LTS 3.7.3-1ubuntu1.1

ubuntu advisories UBUNTU-CVE-2018-1000132

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • mercurial RHEL 7 2.6.2-10.el7
  • mercurial-hgk RHEL 7 2.6.2-10.el7
  • emacs-mercurial RHEL 7 2.6.2-10.el7
  • emacs-mercurial-el RHEL 7 2.6.2-10.el7

red hat advisories RHSA-2019:2276

  • mercurial SLE Software Development Kit 12 SP3 2.8.2-15.10.1

suse advisories SUSE-SU-2018:0933-1

  • mercurial openSUSE Tumbleweed 5.9.1-2.1

opensuse advisories openSUSE-SU-2024:10586-1

  • mercurial Alpine 3.7, Alpine 3.6, Alpine 3.5 4.5.2-r0

alpine advisories ALPINE-CVE-2018-1000132

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2018-1000132 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-1000132 updated cvss 6.5

mercurial: HTTP server permissions bypass

  • Red Hat Enterprise Linux 6 mercurial, mercurial-hgk, emacs-mercurial, emacs-mercurial-el
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux Client Optional (v. 7) mercurial 2.6.2-10.el7, mercurial-hgk 2.6.2-10.el7, emacs-mercurial 2.6.2-10.el7, emacs-mercurial-el 2.6.2-10.el7 Red Hat Enterprise Linux ComputeNode Optional (v. 7) mercurial 2.6.2-10.el7, mercurial-hgk 2.6.2-10.el7, emacs-mercurial 2.6.2-10.el7, emacs-mercurial-el 2.6.2-10.el7 Red Hat Enterprise Linux Server (v. 7) mercurial 2.6.2-10.el7 Red Hat Enterprise Linux Server Optional (v. 7) mercurial-hgk 2.6.2-10.el7, emacs-mercurial 2.6.2-10.el7, emacs-mercurial-el 2.6.2-10.el7 Red Hat Enterprise Linux Workstation (v. 7) mercurial 2.6.2-10.el7 Red Hat Enterprise Linux Workstation Optional (v. 7) mercurial-hgk 2.6.2-10.el7, emacs-mercurial 2.6.2-10.el7, emacs-mercurial-el 2.6.2-10.el7
    fixed: vendor fix RHSA-2019:2276
  • Red Hat Enterprise Linux 8 mercurial, mercurial-chg, mercurial-hgk
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.67% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 9.1 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
NVD 2.0 6.4 AV:N/AC:L/Au:N/C:P/I:P/A:N
GitHub 3.0 9.1 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
pypi mercurial
<4.5.1
4.5.1

Classification

Weakness
  • CWE-732 Incorrect Permission Assignment for Critical Resource

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.