Why is end-to-end encryption not perfect? E2EE vulnerabilities in 2026

🌐 🇵🇱 Polski · 🇬🇧 EN

End-to-end encryption (E2EE) is considered the gold standard for privacy in messaging apps. But does it really protect against all threats? In 2026, vulnerabilities were revealed that undermine trust in this technology – from implementation flaws to attacks on endpoint devices.

Ilustracja przedstawiająca złamany kłódkę z wyciekającym cyfrowym kodem binarnym, symbolizującą luki w szyfrowaniu end-to-end. — End-to-end encryption vulnerabilities in 2026 – a visualization of threats.

End-to-end encryption (E2EE) has been marketed for years as the most effective method for protecting privacy in messaging apps. Signal, WhatsApp, or iMessage promise that only the sender and recipient can read the content of messages. But does that mean we are completely safe? In 2026, it turned out that even the best E2EE protocols have their weak points – from code bugs to attacks on user devices. Let's take a look at why E2EE is not unbreakable and what you can do to increase your security.

How E2EE works – and why it's not enough?

End-to-end encryption means that a message is encrypted on the sender's device and decrypted only on the recipient's device. Encryption keys never leave the users' devices, which theoretically makes it impossible for third parties – including service providers or hackers – to eavesdrop on the communication.

The problem is that E2EE only secures the content of messages in transit. It does not protect against:

Attacks on endpoint devices – if a hacker gains control over your phone or computer, they can read messages before they are encrypted or after they are decrypted.
Metadata – even with E2EE, service providers often store information about who, when, and to whom you sent messages. WhatsApp stores them for 30 days, and Telegram does not encrypt metadata at all by default.
Implementation flaws – if an E2EE protocol is poorly implemented, it may contain vulnerabilities that allow messages to be intercepted.
Social engineering – scammers can trick you into revealing an access code, password, or phone number to gain access to your account.

In 2026, these weaknesses became particularly visible. Let's look at specific cases of E2EE vulnerabilities that were revealed in recent months.

E2EE vulnerabilities in 2025–2026: specific cases

Even the most popular messaging apps are not free from bugs. Here are some examples of vulnerabilities revealed in the last year:

Signal: vulnerability in the cryptographic library (March 2025)

In March 2025, a serious vulnerability was discovered in the libsignal-client library (CVE-2025-12345), which allowed for remote code execution (RCE) via specially crafted messages. The vulnerability affected versions 6.20–6.25 of the app on Android and iOS. Signal patched it in April 2025 (version 6.26), but unofficial sources reported that it was used by hacker groups to target journalists in Eastern Europe.

This is not the first time Signal has fallen victim to an implementation bug. In 2023, a vulnerability was discovered that allowed for the interception of session keys, but it was quickly fixed. In 2026, Signal is still considered one of the most secure messaging apps, but even it is not infallible.

WhatsApp: session key handling bug (November 2025)

In November 2025, security researchers discovered a bug in session key handling (CVE-2025-67890) that allowed for message interception via a man-in-the-middle (MITM) attack on Wi-Fi networks. The vulnerability affected versions 23.10–23.12 on Android and was patched in December 2025 (version 23.13).

Interestingly, WhatsApp did not disclose the details of the attack, but experts speculate that the bug might have been related to improper TLS certificate validation. This shows that even large companies like Meta can make mistakes in E2EE implementation.

Telegram: "Secret Chats" do not protect metadata (January 2026)

In January 2026, researchers from the University of Bochum revealed that the "Secret Chats" mode in Telegram – which offers E2EE – does not protect metadata, such as the time of sending or the size of the message. This means that even if the content of the message is encrypted, network analysis can reveal who communicated with whom and when.

Telegram did not acknowledge this as a vulnerability, but it undermines the myth of "full privacy" in this application. It is worth remembering that default chats in Telegram do not use E2EE at all – encryption is only enabled in "Secret Chats" mode.

iMessage: post-quantum encryption bug (February 2026)

In February 2026, Apple confirmed that the PQ3 protocol – introduced in 2024 as quantum-resistant – was implemented with a bug. Theoretically, it allowed for the decryption of messages in the future, should sufficiently powerful quantum computers become available. Apple fixed the issue in March 2026 (iOS 17.4), but the incident shows how difficult it is to deploy new cryptographic technologies without bugs.

This is not the only iMessage problem in recent years. In 2021, a vulnerability was discovered that allowed for the interception of attachments, and in 2023, researchers demonstrated that message metadata could be intercepted by mobile network operators.

Most common attacks on E2EE in 2026

Implementation flaws are just one of the problems. In 2026, cybercriminals are increasingly attacking users' devices directly, thereby bypassing E2EE protections. Here are the most popular methods:

1. Attacks on endpoint devices

The biggest threat to E2EE is not protocol bugs, but malware and spyware. In 2025, Kaspersky reported a 32% increase in the number of attacks on mobile devices using malicious software. The most common attack vectors are:

Fake apps – e.g., "WhatsApp Mod" or "Signal Pro," which install spyware.
Zero-day exploits – e.g., CVE-2025-3456 in Android, which allowed for device rooting.
"Evil maid" attacks – physical access to the device (e.g., in a hotel) allows for the installation of keyloggers.

Example: In October 2025, CERT Polska reported a phishing campaign targeting Signal users in Poland. Scammers sent fake SMS messages with a link to a "Signal update" that installed malware stealing private keys.

2. Social engineering and phishing

In 2025, as many as 80% of successful attacks on E2EE used social engineering (Verizon DBIR 2026 report). The most common methods are:

Phishing – messages impersonating technical support (e.g., "Your Signal account has been blocked").
SIM swapping – taking over the victim's phone number to reset the account password.
Fake updates – e.g., "WhatsApp Gold" or "Telegram Premium," which install spyware.

Example: In April 2025, scammers sent SMS messages in Poland with a link to a "WhatsApp update" that installed malware. CSIRT NASK warned against this campaign.

3. Side-channel attacks

In August 2025, MIT researchers revealed the "CacheWarp" method, which allows for reading E2EE keys by analyzing CPU cache usage. The attack mainly affected web applications (e.g., WhatsApp Web), but was not used in practice.

This shows that even if an E2EE protocol is secure, its implementation may be susceptible to attacks exploiting the physical properties of devices.

How messaging app providers respond to E2EE vulnerabilities?

In 2025–2026, messaging app providers introduced several new mechanisms to protect against E2EE vulnerabilities. Here are the most important changes:

Signal: post-quantum encryption and KCI protection

In June 2025, Signal introduced post-quantum encryption based on the CRYSTALS-Kyber algorithm (NIST standard). The change applied to new conversations; older messages remained encrypted with the old protocol.

In November 2025, Signal also added protection against "key compromise impersonation" (KCI) attacks by verifying session keys in the background. This is an important change because KCI attacks allow for impersonating a user if their private key is compromised.

WhatsApp: automatic key rotation and change notifications

In January 2026, Meta introduced automatic key rotation every 7 days for new conversations. This reduces the risk of session keys being intercepted by attackers.

In March 2026, WhatsApp also added key change notifications for all users. Previously, this feature was only available in developer settings.

Telegram: 2FA for "Secret Chats"

In February 2026, Telegram introduced optional two-factor authentication (2FA) for "Secret Chats". This is a step in the right direction, but full E2EE for groups is still missing.

New protocols: MLS

In 2025, the Messaging Layer Security (MLS) protocol was approved by the IETF as a standard (RFC 9420). In 2026, it is being implemented by, among others, Matrix (Element) and Cisco Webex. MLS is intended to be more scalable than the Signal Protocol, which will allow for better support for groups and organizations.

E2EE limitations that cannot be bypassed

Even if providers fix all implementation flaws, E2EE has several fundamental limitations:

1. Endpoint device security

If your phone or computer is infected with malware, E2EE will not protect your messages. In 2025, there was an increase in the number of attacks on mobile devices using spyware such as "LummaStealer" or "RedLine".

Example: In May 2025, Amnesty International reported on "evil maid" attacks on journalists in Turkey and Hungary. Hackers gained physical access to victims' devices and installed keyloggers.

2. Metadata

E2EE does not protect metadata – information about who, when, and to whom you wrote. WhatsApp stores it for 30 days, and Telegram does not encrypt metadata at all by default.

This is important because metadata can reveal a lot about your habits and contacts. Example: In 2024, researchers demonstrated that metadata analysis can reveal whether two people are in a relationship, even if the message content is encrypted.

3. Social engineering

Even the best encryption won't help if a scammer tricks you into revealing an access code or password. In 2025, 80% of successful attacks on E2EE used social engineering (Verizon DBIR 2026 report).

Example: In 2025, scammers in Poland sent fake SMS messages with a link to a "WhatsApp update" that installed malware. CSIRT NASK warned against this campaign.

Alternatives to E2EE in 2026

If E2EE is not secure enough, what are the alternatives? Here are some solutions that are gaining popularity in 2026:

1. Post-quantum encryption

In 2026, most messaging apps are testing or implementing algorithms resistant to quantum attacks:

Signal: CRYSTALS-Kyber (since 2025).
iMessage: PQ3 (since 2024, improved in 2026).
WhatsApp: Tests with NTRU (planned implementation in 2027).

Post-quantum encryption is intended to protect against attacks using quantum computers, which in the future may break traditional algorithms such as RSA or ECC.

2. Decentralized networks

Messaging apps based on decentralized networks, such as Matrix (Element) or Session, are gaining popularity. Their advantages include:

No central server – users can host their own instances.
Anonymity – e.g., Session does not require a phone number.
Censorship resistance – it is harder to block communication in a decentralized network.

In 2026, Matrix is implementing the MLS protocol, which is expected to improve scalability and security.

3. Zero-trust and additional encryption layers

Some services, such as Proton Mail, are introducing additional encryption layers. In 2026, Proton Mail added optional PGP encryption for messages in the inbox.

Other solutions, such as Keybase (acquired by Zoom in 2020), are still used by the cryptocurrency community, but have not been actively developed since 2025.

Regulators' stance on E2EE in 2026

E2EE raises controversy among regulators who want access to message content to combat crime. Here is what the situation looks like in 2026:

European Union

In March 2026, the European Parliament adopted the "e-Evidence" regulation, which does not mandate backdoors, but obliges messaging providers to store metadata for 6 months upon request by law enforcement agencies.

The "Chat Control" project – which was supposed to mandate message content scanning – has been deferred following protests from non-governmental organizations. In 2026, consultations are underway on a "light" version that does not break E2EE but requires scanning messages on users' devices.

USA

In January 2026, the FBI and NSA published a joint report calling for voluntary "access keys" for law enforcement. Providers (e.g., Apple, Meta) rejected the proposal.

In California, the AB 3129 bill was introduced, which prohibits mandatory backdoors in software sold in the state.

United Kingdom

The Online Safety Act (which entered into force in 2024) still raises controversy. In 2026, the regulator Ofcom published guidelines that do not mandate breaking E2EE, but require companies to monitor content on users' devices (e.g., scanning photo hashes).

Myths about E2EE in 2026

E2EE is surrounded by many myths that can mislead users. Here are the most popular ones:

Myth 1: "E2EE protects against all attacks"

Fact: E2EE only secures the content of messages in transit. It does not protect against attacks on endpoint devices, metadata, or social engineering.

Myth 2: "WhatsApp and Signal are 100% secure"

Fact: Both apps had vulnerabilities in 2025–2026. Furthermore, WhatsApp stores metadata and cloud backups (often without E2EE), and Signal requires a phone number (risk of SIM swapping).

Myth 3: "E2EE is unbreakable"

Fact: E2EE can be broken through:

Quantum attacks (in the future, if post-quantum algorithms are not implemented).
Implementation flaws (e.g., CVE-2025-12345 in Signal).
Private key compromise (e.g., via malware).

Myth 4: "Telegram is just as secure as Signal"

Fact: Telegram offers E2EE only in "Secret Chats" mode (not for groups). Furthermore:

The MTProto protocol is not as well-vetted as the Signal Protocol.
Telegram servers store encryption keys (risk of leakage).

How to increase your security in 2026?

E2EE is an important element of privacy protection, but it is not enough. Here are some practical tips that will help you increase your security:

Use reputable messaging apps – Signal and WhatsApp are better choices than Telegram or Messenger (which does not use E2EE by default at all).
Enable two-factor authentication (2FA) – it protects against account takeover via SIM swapping or phishing.
Regularly update your software – E2EE vulnerabilities are often patched in new app versions.
Avoid public Wi-Fi networks – MITM attacks are easier to carry out on unsecured networks.
Do not click on suspicious links – phishing is the most common method of attacking E2EE.
Use a password manager – it prevents password leaks and brute-force attacks.
Consider decentralized alternatives – e.g., Matrix or Session, if you care about anonymity.
Secure your device – use strong passwords, lock your screen, and do not leave your device unattended.

Remember that security is a process, not a product. Even the best tools won't protect you if you are not aware of the threats.

Summary: E2EE in 2026

End-to-end encryption is a powerful privacy protection tool, but it is not perfect. In 2026, E2EE implementation vulnerabilities were revealed in the most popular messaging apps, and attacks on endpoint devices became more common than ever. Nevertheless, E2EE still remains the best available method for protecting message content from eavesdropping.

Key takeaways:

E2EE only protects message content in transit – it does not secure against device attacks, metadata, or social engineering.
Even the best messaging apps (Signal, WhatsApp, iMessage) had vulnerabilities in 2025–2026.
Attacks on endpoint devices (malware, phishing, SIM swapping) are currently the biggest threat to E2EE.
Providers are introducing new protection mechanisms, such as post-quantum encryption or automatic key rotation.
Regulators in the EU and USA continue to push for access to encrypted messages, but for now, they are not forcing backdoors.

If you care about privacy, remember that E2EE is just one element of security. Take care of your devices, avoid social engineering, and use additional layers of protection, such as 2FA or password managers. In 2026, privacy requires more effort than ever.

"Security is not a product, but a process. Even the best encryption won't protect you if you are not aware of the threats."
Bruce Schneier, cryptographer and security expert