Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2018-13348

mercurial: Improper length check in mpatch.c

Overview

Published
6 Jul 2018
Modified
17 Jun 2026
High CVE
1 Registry packages
3 OS packages
4 Linux distributions
Yes Fix available

Description

The mpatch_decode function in mpatch.c in Mercurial before 4.6.1 mishandles certain situations where there should be at least 12 bytes remaining after the current position in the patch data, but actually are not, aka OVE-20180430-0001.

Source: OX vulnerability database

Severity

7.5 · HIGH

CVSS 3.0 base score, scored by NVD.

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

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

Weakness: CWE-20

Affected packages · 1

Packages affected by CVE-2018-13348
EcosystemPackageVulnerableFixed in
PyPI mercurial <4.6.1 4.6.1

Open a package to see all its vulnerabilities.

Operating systems · 9 fixes

debian 5 releases · 1 package

fixed 5
mercurial
debian fixes for CVE-2018-13348
ReleasePackageFixed in
11 mercurial 4.6.1-1
12 mercurial 4.6.1-1
13 mercurial 4.6.1-1
14 mercurial 4.6.1-1
9 mercurial 4.0-1+deb9u2

echo 1 release · 1 package

fixed 1
mercurial
echo fixes for CVE-2018-13348
ReleasePackageFixed in
mercurial 4.6.1-1

openSUSE 1 release · 1 package

fixed 1
mercurial
openSUSE fixes for CVE-2018-13348
ReleasePackageFixed inAdvisory
Tumbleweed mercurial +2 5.9.1-2.1 openSUSE-SU-2024:10586-1

ubuntu 2 releases · 1 package

fixed 2
mercurial
ubuntu fixes for CVE-2018-13348
ReleasePackageFixed in
18.04 mercurial 4.5.3-1ubuntu2.1
18.04-ESM mercurial 4.5.3-1ubuntu2.1

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.