VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

mercurial: vulnerability history, versions and safety

mercurial is a package in the Debian ecosystem. Vulert records 35 vulnerabilities for it across 1 release, from Jun 2008 to Mar 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
35 vulnerabilities recorded U35
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all mercurial vulnerabilities

Vulert verdict on mercurial i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 27 Mar 2025. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 35 vulnerabilities on record across 16 years, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 35 over 16 years · 0 in the last year i
  • Latest disclosure 27 Mar 2025 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for mercurial, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
5.6.1-4 U3 Yes Details →

Newest 1 of 1 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2008 4
  • 2015 2
  • 2016 8
  • 2017 6
  • 2018 9
  • 2019 3
  • 2025 3

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 35 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for mercurial

The 5 most severe of 35 vulnerabilities recorded for this package

Search all 35 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Arbitrary Code Execution Vulnerability in Mercurial - CVE-2017-17458 9.8 critical 4.4.1-1 07 Dec 2017
Critical Integer Handling Vulnerability in Mercurial: CVE-2018-13347 9.8 critical 4.6.1-1 06 Jul 2018
Out-of-Bounds Read Vulnerability in Mercurial 9.1 critical 4.7.2-1 04 Oct 2018
Remote Code Execution Vulnerability in Mercurial via Debugger Exposure 8.8 high 4.3.1-1 06 Jun 2017
Remote Code Execution Vulnerability in Mercurial - CVE-2016-3069 8.8 high 3.7.3-1 13 Apr 2016

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About mercurial

Is mercurial safe to use?

Vulert records 35 vulnerabilities for mercurial in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 35 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does mercurial have?

35 vulnerabilities are recorded for mercurial in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 35 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new mercurial vulnerabilities disclosed?

0 vulnerabilities were recorded for mercurial in the last 12 months, and the oldest entry in this database dates to 30 Jun 2008. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of mercurial are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor mercurial for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the mercurial version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.