Loading vulnerability…
CVE-2005-0469 is a client-side buffer overflow in various BSD-based Telnet clients. The flaw is in the slc_add_reply function, which handles LINEMODE Set Local Character (SLC) suboption replies. The vulnerable code fails to properly validate bounds when processing a reply containing a large number of SLC commands, allowing a malicious Telnet server, or an attacker in a man-in-the-middle position able to modify server responses, to overflow a client-side buffer. The issue is triggered during Telnet option negotiation when the client processes crafted LINEMODE SLC reply data from the remote side. The vulnerability is closely analogous to later server-side Telnet LINEMODE/SLC overflows, but in this case the memory corruption occurs in the client.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A historical Telnet client-side bounds-checking flaw similar to CVE-2026-32746, caused by a missing bounds check in slc_add_reply.
An older client-side vulnerability referenced as analogous to CVE-2026-32746.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.