NVD / CVE Program· CNA mitre

CVE-2017-17458: In Mercurial before 4.4.1, it is possible that a specially malformed repository can cause Git subrepositories to run arbitrary code in the…

CriticalCVSS 9.8 · v3.0—No exploit Fix available

Noroxi assessment

Priority: Plan (action score 41/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 6.3% (FIRST EPSS); higher than 93.7% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: mercurial (Debian:12) 4.4.1-1; mercurial (Debian:7) 2.2.2-4+deb7u6; mercurial (Debian:8) 3.1.2-2+deb8u5, 3.1.2-2+deb8u6.

Add it to your regular patch cycle. Upgrade to mercurial (Debian:12) 4.4.1-1; mercurial (Debian:7) 2.2.2-4+deb7u6; mercurial (Debian:8) 3.1.2-2+deb8u5, 3.1.2-2+deb8u6 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In Mercurial before 4.4.1, it is possible that a specially malformed repository can cause Git subrepositories to run arbitrary code in the form of a .git/hooks/post-update script checked into the repository. Typical use of Mercurial prevents construction of such repositories, but they can be created programmatically.

Published: Dec 7, 2017
Updated: Jun 16, 2026
EPSS: 6.3% · 93th percentile
CWE: CWE-78

Report tools

JSON

Action score

Plan

Add it to your regular patch cycle.

CVSS: 39 / 40 · 9.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 2 / 30 · 6.3%

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
mercurial	mercurial	cpe:2.3:a:mercurial:mercurial
debian	debian linux	cpe:2.3:o:debian:debian_linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

debian debian linux7.0
debian debian linux8.0
mercurial mercurialbefore 4.4.1

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	mercurial	before 4.4.1-1	4.4.1-1
Debian:7	mercurial	before 2.2.2-4+deb7u6	2.2.2-4+deb7u6
Debian:8	mercurial	before 3.1.2-2+deb8u5	3.1.2-2+deb8u5
Debian:8	mercurial	before 3.1.2-2+deb8u6	3.1.2-2+deb8u6
Debian:9	mercurial	before 4.0-1+deb9u2	4.0-1+deb9u2
openSUSE:Tumbleweed	mercurial	before 5.9.1-2.1	5.9.1-2.1
PyPI	mercurial	before 4.4.1	4.4.1
SUSE:Linux Enterprise Software Development Kit 11 SP4	mercurial	before 2.3.2-0.18.6.1	2.3.2-0.18.6.1
SUSE:Linux Enterprise Software Development Kit 12 SP2	mercurial	before 2.8.2-15.6.1	2.8.2-15.6.1

Same product

mercurial: all records

Other highest-scoring records for the same primary product.

CVE-2014-9390Git before 1.8.5.6, 1.9.x before 1.9.5, 2.0.x before 2.0.5, 2.1.x before 2.1.4, and 2.2.x before 2.2.1 on Windows and OS X; Mercurial…
62This week
CVE-2017-9462In Mercurial before 4.1.3, "hg serve --stdio" allows remote authenticated users to launch the Python debugger, and consequently execute…
42Plan
CVE-2017-1000116Mercurial prior to 4.3 did not adequately sanitize hostnames passed to ssh, leading to possible shell-injection attacks.
41Plan

Published before and after this one in the same product

← EarlierCVE-2016-3105May 9, 2016 · The convert extension in Mercurial before 3.8 might allow context-dependent attackers to execute arbitrary code via a crafted git…
36Monitor
← EarlierCVE-2017-1000115Oct 4, 2017 · Mercurial prior to version 4.3 is vulnerable to a missing symlink check that can malicious repositories to modify files outside the…
31Monitor
Later →CVE-2018-1000132Mar 14, 2018 · Mercurial version 4.5 and earlier contains a Incorrect Access Control (CWE-285) vulnerability in Protocol server that can result in…
37Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
debian:mercurial	4.4.1-1 · Debian:12	Package registry (OSV)
opensuse:mercurial	5.9.1-2.1 · openSUSE:Tumbleweed	Package registry (OSV)
PyPI:mercurial	4.4.1	Package registry (OSV)
suse:mercurial	2.3.2-0.18.6.1 · SUSE:Linux Enterprise Software Development Kit 11 SP4	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-78 · Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

CVSS vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

User input is inserted as text into a shell command. The shell may interpret special characters in the input as part of the command.

The bug in code

The whole CWE-78 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const host = req.body.host;
2exec("ping -c 1 " + host, onResult);

Fixed

1const host = req.body.host;
2if (!/^[a-z0-9.-]{1,253}$/i.test(host)) return res.sendStatus(400);
3execFile("ping", ["-c", "1", host], onResult);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log (1)

Fix✗ → ✓Sep 28, 2026, 10:46 PM UTC

For records you follow, these changes also arrive as notifications. →

References

www.securityfocus.com/bid/102926

Show all references (8 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records