W3m is a text-based web browser with a narrowly scoped but notable deployment footprint in terminal and embedded environments, where its handling of web content parsing presents an attack surface. Disclosed vulnerabilities center on improper input validation and format-string issues that reflect the challenges of safely processing untrusted HTML and network data in a lightweight browser codebase. Current exploitation activity and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by W3m over time
Signals from CVEs in this vendor scope (5 CVEs).
5 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2001-0700HIGH Buffer overflow in w3m 0.2.1 and earlier allows a remote attacker to execute arbitrary code via a long base64 encoded MIME header. | Sep 20, 2001 | 7.5 | 34 | NO | YES |
CVE-2006-6772HIGH Format string vulnerability in the inputAnswer function in file.c in w3m before 0.5.2, when run with the dump or backend option, allows remote attackers to execute arbitrary code v | Dec 27, 2006 | 9.3 | 24 | NO | NO |
CVE-2010-2074MEDIUM istream.c in w3m 0.5.2 and possibly other versions, when ssl_verify_server is enabled, does not properly handle a '\0' character in a domain name in the (1) subject's Common Name o | Jun 16, 2010 | 6.8 | 23 | NO | NO |
CVE-2002-1348MEDIUM w3m before 0.3.2.2 does not properly escape HTML tags in the ALT attribute of an IMG tag, which could allow remote attackers to access files or cookies. | Feb 19, 2003 | 5.0 | 15 | NO | NO |
CVE-2002-1335MEDIUM Cross-site scripting (XSS) vulnerability in w3m 0.3.2 does not escape an HTML tag in a frame, which allows remote attackers to insert arbitrary web script or HTML and access files | Dec 11, 2002 | 4.3 | 14 | NO | NO |
Signals from CVEs in this vendor scope (5 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by W3m.
Media articles that mention a CVE ID that affects a product developed by W3m — matched by CVE ID, not by vendor name.