Skip to content
Fencer Intel
high 7.4

CVE-2016-2087 json

Directory traversal vulnerability in the client in HexChat 2.11.0 allows remote IRC servers to read or modify arbitrary files via a .. (dot…

published 2017-01-18 9 y ago modified 2026-06-17 4 mo ago also EUVD-2016-3192

cvss
7.4
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
9.5%
EPSS 9.5% chance of exploitation in 30 days, percentile 95%
public exploits
1
Exploit-DB

Summary

Directory traversal vulnerability in the client in HexChat 2.11.0 allows remote IRC servers to read or modify arbitrary files via a .. (dot dot) in the server name.

Patch / fix

  • hexchat Debian 13, Debian 12 2.12.4-4

debian advisories DEBIAN-CVE-2016-2087

  • hexchat SLE Workstation Extension 12 SP5 2.12.0-6.5.146

suse advisories SUSE-SU-2020:2872-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-2016-2087 updated

hexchat: Multiple vulnerabilities

  • Red Hat All currently supported Red Hat products
    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

Timeline

  1. First public exploit (EDB-39656)
  2. Published

Exploit prediction

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

Exploits and checks

  • EDB-39656 Hexchat IRC Client 2.11.0 - Directory Traversal local, 2016-04-04
  • packetstormsecurity.com http://packetstormsecurity.com/files/136564/Hexchat-IRC-Client-2.11.0-Directory-Traversal.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 7.4 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/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.