Skip to content
Fencer Intel
high 7.5

CVE-2015-1396 json

A Directory Traversal vulnerability exists in the GNU patch before 2.7.4.

published 2019-11-25 6 y ago modified 2026-06-17 4 mo ago also EUVD-2015-1533

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.3%
EPSS 3.3% chance of exploitation in 30 days, percentile 88%
public exploits
0
none known

Summary

A Directory Traversal vulnerability exists in the GNU patch before 2.7.4. A remote attacker can write to arbitrary files via a symlink attack in a patch file. NOTE: this issue exists because of an incomplete fix for CVE-2015-1196.

Patch / fix

  • gnu patch 2.7.4
  • patch Debian 14, Debian 13, Debian 12 2.7.3-1

debian advisories DEBIAN-CVE-2015-1396

  • patch Ubuntu 14.04 LTS 2.7.1-4ubuntu2.3

ubuntu advisories UBUNTU-CVE-2015-1396

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

  • patch SLES for SAP 12, SLES 12, SLED 12 2.7.5-7.1

suse advisories SUSE-SU-2015:1019-1

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-2015-1396 updated cvss 3.6

patch: directory traversal via symlinks (incomplete fix for CVE-2015-1196)

  • Red Hat Enterprise Linux 5 patch Red Hat Enterprise Linux 6 patch Red Hat Enterprise Linux 7 patch
    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

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

CVSS scores

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

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

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.