From a penetration tester’s point of view, Telnet is one of those findings that immediately stands out. Not because it is complex or interesting, but because it is simple and risky. If Telnet is exposed in an environment, it often becomes one of the easiest ways for an attacker to gain access.
Many organisations still rely on Telnet in legacy systems, network devices and internal tools. That alone is risky. Recent vulnerabilities have made the situation much worse.
What is Telnet?
Telnet is an old protocol used to remotely log into systems such as servers, routers or network devices. The problem is that everything it sends, including usernames and passwords, is in plain text. This means anyone with access to the network can read sensitive information easily.
In today’s networks, where attackers actively scan and probe systems, this lack of encryption makes Telnet very unsafe. Even inside a company network, it can be exploited if an attacker gains a foothold elsewhere.
Recent Vulnerabilities
Two recent vulnerabilities make Telnet even more dangerous.
**CVE-2026-24061** allows an attacker to connect to a system and gain root access without needing any credentials. Essentially, an attacker can take full control of a system without logging in.
Another vulnerability, **CVE-2026-32746** , involves a memory issue that can be exploited remotely. Attackers can crash services or even execute their own code. Again, no authentication is required.
Public exploit code is available for both of these vulnerabilities, so attackers do not need advanced skills to use them.
Why This Is a Concern
From a security testing perspective, finding Telnet on a network is a red flag.
If the service is vulnerable, an attacker can connect and gain full access quickly. Once inside, they can move to other systems, access sensitive data or disrupt operations.
For companies, this means that any system running Telnet could potentially be accessed without authorisation, leading to data exposure or operational issues.
What You Should Do
The simplest and safest solution is to stop using Telnet. Modern alternatives like SSH provide encrypted communication and stronger security.
If Telnet cannot be removed immediately because of older systems, it is important to limit access. Make sure the service is patched, restrict who can connect to it and never expose it to the internet.
Retire Telnet Before Attackers Exploit It
Telnet is no longer a safe way to access systems. The protocol is outdated, recent vulnerabilities allow attackers to gain access without passwords and public exploits make it easier for attackers to take advantage of it.
Companies should replace Telnet with secure alternatives like SSH and limit access to any remaining Telnet services to reduce risk.
—
Vulnerabilities like these are exactly what attackers look for. A network penetration test from Secora Consulting will identify the weak points in your infrastructure before someone else does.
Request your pentest today. 👇