w3m through 0.5.3 does not properly handle temporary files when the ~/.w3m directory is unwritable, which allows a local attacker to craft a symlink attack to overwrite arbitrary files.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Alpine Linux | — | Upgrade w3m | Aug 22, 2024 | Jan 25, 2018 |
| Debian | — | Upgrade w3m | Jul 30, 2024 | Jan 25, 2018 |
| Freebsd | — | Upgrade w3m-imgUpgrade ja-w3m-imgUpgrade ja-w3mUpgrade w3m | Feb 4, 2018 | Feb 1, 2018 |
| Redhat_linux | — | No solution exists | Jul 9, 2025 | Jan 25, 2018 |
| Suse | — | Upgrade w3m | May 20, 2018 | Jan 24, 2018 |
| Ubuntu | — | Upgrade w3m | Feb 2, 2018 | Jan 24, 2018 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub