Skip to content
Noroxi
NVD / CVE Program· CNA redhat

CVE-2019-3902: A flaw was found in Mercurial before 4.9.

MediumCVSS 5.9 · v3.0—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 23/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: 1.3% (FIRST EPSS); higher than 72.2% 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. Special conditions such as timing or configuration are required.
  • Fixed version: mercurial (Alpine:v3.10) 4.9-r0; mercurial (Alpine:v3.7) 4.5.2-r1; mercurial (Alpine:v3.8) 4.6.1-r1.

Low priority for now. Upgrade to mercurial (Alpine:v3.10) 4.9-r0; mercurial (Alpine:v3.7) 4.5.2-r1; mercurial (Alpine:v3.8) 4.6.1-r1 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

A flaw was found in Mercurial before 4.9. It was possible to use symlinks and subrepositories to defeat Mercurial's path-checking logic and write files outside a repository.

Published
Apr 22, 2019
Updated
Jun 16, 2026
EPSS
1.3% · 72th percentile

Report tools

JSON

Action score

23

Monitor

Low priority for now.

CVSS
23 / 40 · 5.9 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.3%

CNA vs NVD score

NVD
5.9
CNA · redhat
5.1
0.8 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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.

Follow CVE-2019-3902

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
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.

VendorProduct
mercurialmercurial
debiandebian linux
redhatenterprise linux

Versions reported by the vendor

Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.

  • The Mercurial Project mercurial

    • before 4.9affected

Affected versions

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

  • debian debian linux8.0
  • mercurial mercurialbefore 4.9
  • redhat enterprise linux7.0

Package-level exposure

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

EcosystemPackageAffected rangeFix
Alpine:v3.10mercurialbefore 4.9-r04.9-r0
Alpine:v3.7mercurialbefore 4.5.2-r14.5.2-r1
Alpine:v3.8mercurialbefore 4.6.1-r14.6.1-r1
Debian:12mercurialbefore 4.9-14.9-1
Debian:8mercurialbefore 3.1.2-2+deb8u73.1.2-2+deb8u7
Debian:9mercurialbefore 4.0-1+deb9u24.0-1+deb9u2
openSUSE:Leap 15.1mercurialbefore 4.5.2-lp151.6.3.14.5.2-lp151.6.3.1
openSUSE:Leap 15.2mercurialbefore 4.5.2-lp152.7.3.14.5.2-lp152.7.3.1
openSUSE:Tumbleweedmercurialbefore 5.9.1-2.15.9.1-2.1
PyPImercurialbefore 4.94.9
SUSE:Linux Enterprise Module for Python 2 15 SP1mercurialbefore 4.5.2-3.9.444.5.2-3.9.44
SUSE:Linux Enterprise Software Development Kit 12 SP5mercurialbefore 2.8.2-15.18.42.8.2-15.18.4

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-17458In Mercurial before 4.4.1, it is possible that a specially malformed repository can cause Git subrepositories to run arbitrary code in the…
    41Plan

Published before and after this one in the same product

  • ← EarlierCVE-2018-13348Jul 5, 2018 · The mpatch_decode function in mpatch.c in Mercurial before 4.6.1 mishandles certain situations where there should be at least 12 bytes…
    31Monitor
  • ← EarlierCVE-2018-17983Oct 4, 2018 · cext/manifest.c in Mercurial before 4.7.2 has an out-of-bounds read during parsing of a malformed manifest entry.
    37Monitor
  • Later →CVE-2010-4237Oct 29, 2019 · Mercurial before 1.6.4 fails to verify the Common Name field of SSL certificates which allows remote attackers who acquire a certificate…
    23Monitor

Remediation

Which version to upgrade to

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

Product / packageFixed versionSource
alpine:mercurial4.9-r0 · Alpine:v3.10Package registry (OSV)
debian:mercurial4.9-1 · Debian:12Package registry (OSV)
opensuse:mercurial4.5.2-lp151.6.3.1 · openSUSE:Leap 15.1Package registry (OSV)
PyPI:mercurial4.9Package registry (OSV)
suse:mercurial4.5.2-3.9.44 · SUSE:Linux Enterprise Module for Python 2 15 SP1Package 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.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
none
Integrity
high · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
High
Availability impact
None

CVSS vector

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

nvd-primary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

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

Vulnerable

ts
const file = path.join(ROOT, req.query.name);res.sendFile(file);

Fixed

ts
const file = path.resolve(ROOT, req.query.name);if (!file.startsWith(ROOT + path.sep)) {  return res.sendStatus(400);}res.sendFile(file);

References

All records