In short: On August 11, 2026, Signal launched Automatic Key Verification (AKV), a feature that silently confirms end-to-end encrypted messages reach only their intended recipient — without in-person safety number comparisons or any user action. AKV closes a narrow but serious attack surface: a compromised Signal directory or malicious insider could substitute an attacker's encryption key for a contact's, enabling server-side interception that appears fully encrypted to both parties.
What Happened
On August 11, 2026, Signal Foundation published the announcement of Automatic Key Verification (AKV), a new background security mechanism now available in the latest Signal releases for Android and iOS. Unlike the existing manual Safety Number comparison — a step realistically taken by only a small fraction of users — AKV runs entirely in the background and requires no action from either participant in a conversation.
AKV is built on Key Transparency, a cryptographic primitive analogous to Certificate Transparency already used by HTTPS certificate authorities worldwide. Independent auditors Cloudflare and Trail of Bits verify the key transparency log in real time, making hidden key substitutions cryptographically detectable. For a practical explanation of the underlying attack class, see our guide on man-in-the-middle attacks.
The Threat AKV Addresses
Signal's end-to-end encryption protects messages in transit: intermediate nodes see only ciphertext. But one subtle threat has always remained: what if Signal's server itself substituted your contact's public key? An attacker with control over the messaging infrastructure, or a malicious insider, could theoretically register a fraudulent key in the directory — decrypting selected conversations invisibly to both parties while the encryption indicator continues to show green.
This is a trusted-directory attack, a variant of man-in-the-middle operating at the authentication layer rather than the transport layer. The previous mitigation was manual safety number verification during an in-person meeting or over a video call — a procedure only a small fraction of users ever perform. AKV automates that verification and scales it across all contacts with zero operational friction. For more on protecting your messaging conversations, read our guide on how to protect your messaging apps.
How Key Transparency Works
Signal's AKV system uses two cryptographic data structures. First, a log tree: an append-only, chronologically ordered ledger of all key registrations and changes. Every entry is cryptographically chained to all previous entries — silent deletion or modification is impossible without breaking the hash chain, making tampering immediately detectable. Second, prefix trees (index books): efficient lookup structures that allow any client to verify whether the key associated with a phone number is globally consistent across all participants.
The auditors — Cloudflare and Trail of Bits — receive no plaintext phone numbers; data is cryptographically obscured using verifiable random functions (VRF). Trail of Bits implemented its auditor client from scratch based on Signal's specification rather than the reference codebase, reducing the risk of shared vulnerabilities. Both auditors operate independently and are not compensated by Signal; Trail of Bits has stated it operates its auditor as a public good.
In practice: when you open a conversation, Signal silently checks your contact's public key against the cryptographic log and auditor signatures. A match means encryption is operating with the correct, registered key. A mismatch would trigger a visible warning, alerting you to a potential key substitution in the directory.
Limitations of AKV
AKV confirms key consistency in the directory — it does not prove the account is controlled by the person you expect. A full account takeover (stolen SIM card, hijacked account credentials) is outside AKV's scope of protection and requires separate mitigation such as registration lock and strong authentication.
Additionally, automatically verifying another user currently requires their phone number. Contacts established only through Signal usernames are not yet covered by full AKV. Outdated phone numbers also block automatic verification. Users preferring manual safety numbers can disable AKV under Privacy → Advanced → Automatic Key Verification.
What This Means for Your Privacy
AKV is a meaningful step toward cryptographically provable privacy: Signal's security model now rests not only on trusting the company's servers but on mathematically verifiable guarantees checked by independent third parties. Journalists, lawyers, activists, and anyone for whom messaging confidentiality is critical gain an additional layer of protection with zero operational friction.
It is worth keeping different security layers distinct. AKV works inside Signal, ensuring encryption key correctness at the directory level. A VPN works at the network layer, outside Signal — hiding from your ISP and network observers the fact of your connections: your IP address and traffic metadata. LiMP VPN complements Signal by concealing even the fact that you are using a secure messenger from your network provider, even when message content is already protected by Signal's end-to-end encryption. These are two tools addressing different threat surfaces.