Skip to content
Fencer Intel
medium 6.5

CVE-2016-9430 json

An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31.

published 2016-12-12 9 y ago modified 2026-06-17 4 mo ago also EUVD-2016-10240

cvss
6.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.8%
EPSS 1.8% chance of exploitation in 30 days, percentile 78%
public exploits
0
none known

Summary

An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31. w3m allows remote attackers to cause a denial of service (segmentation fault and crash) via a crafted HTML page.

Patch / fix

  • w3m Debian 14, Debian 13, Debian 12 0.5.3-30

debian advisories DEBIAN-CVE-2016-9430

  • w3m Ubuntu 14.04 LTS 0.5.3-15ubuntu0.1
  • w3m Ubuntu 16.04 LTS 0.5.3-26ubuntu0.1

ubuntu advisories UBUNTU-CVE-2016-9430

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

  • w3m Arch Linux 0.5.3.git20161031-1

arch linux advisories AVG-73

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-9430 updated cvss 4.3

w3m: Segmentation fault with malformed input tag

  • Red Hat Enterprise Linux 5 w3m Red Hat Enterprise Linux 6 w3m, w3m-img
    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

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

CVSS scores

assigned by version score vector
NVD 3.0 6.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P

Classification

Weakness

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.